I tested this on OS X 10.6.7 using the steam version.
I created a new winxp bottle, then installed steam.
You need to manually install .net 2.0 and visual c++ 2005 runtimes.
When you launch the game it will try and install these runtimes
again from the games own installation packages, just cancel out of
them.
The two problems I have found running the game are. Trying to set
audio settings crashes it, this was reported in an earlier thread on
this forum.
Setting the resolution ends up in quirky results. I have a MBP
1440x900 res, when I run the game it thinks the native resolution is
1440x878. If I set it to fullscreen it does so fine, however upon
relaunching the game you get a black bar down the bottom and then a
white bar above that with the rest of the game drawn above the white
bar.
If I leave the game running at 1440x878 I get the Finder menu bar at
the top.
Hi there,
...Ding!... back-story -- I have a ticket/bug hoisted against my 11,2 iMac with HD5670 video,
with regards the 'fight' between fullscreen and the OSX menubar ; many apps are doing it on my
setup, the predominate scenario being the 22pixel blackbar at the bottom of screen in fullscreen
mode/resolution. Howsoever, during me testing here, with Borderlands, I did indeed recreate what
you describe here several times - 22pixel blackbar at bottom, 22pixel whitebar at top, and just
once I had -both- of these bars at the bottom of the screen, white atop black, with the top
44pixels of the game viewport rendering cut off...
...problem is, none of the CW devs can recreate the issue, and so there's a bit of a search on
to find some app that -can- reliably recreate the issue ; perhaps this may be it... could you
post back the full specs of your MBP please?...ie; model, video chipset/ram etc etc ; such would
help record where this is happening on what hardware makeup....
...that said, I'm suspicious something else is at play, my first best-guess candidate being the
rollin updates to OS X itself. The iMac here was one of the first Mid-2010 'new' models, and was
shipped with 10.6.3 -- now current @ 10.6.7 ; that period contains more than a few OS updates and
upgrades. If one of these junctures is participle to this issue, my reckoning puts it good @ 10.6.5
- 10.6.6 would've rolled in somewhere on the cusp of CXG-9.2 -> 10.0 .. it all seems a bit too
coincidental for mine, perhaps something snuck in under the back door here =)....
The only way to really ascertain such, in my mind, is to wipe things clean, reinstall the OS, and
take a firmer hold of the software updater and recreate the history on both the OS and CXG version
increments to see if one can find the coincidence of events that manifests the issue -- take & hold
@ 10.6.4 + pass from CXG-9.0 -> CXG current ; rub out CXG ; take OS to 10.6.5 & hold + CXG pass ;
ditto ; ditto ditto; wash, rinse, repeat <grin> ,,, little doubt it'd be easier to know if there
was something one could manually do to remedy any possible glitche in the update/upgrade processes,
but I have -no- idea where that could happen wrt OSX - I don't know it that well...yet ..
Thank you very much for reporting this detail -- such can be invaluable when chasing the elusive B)
Cheers!
