Install instructions:
Express install the game
- Run regedit and create key Direct3D --> String:
OffscreenRenderingMode = pbuffer (without string you get a
black screen)
Run the game!
The following comments are owned by whoever posted them. We are not responsible for them in any way.
Back to Threads Reply to Thread
Install instructions:
Express install the game
Run the game!
I tried it and can confirm that it works on my MacBook Pro with OS X 10.6.3 and CrossOver Games 9.0.
To specify paulthetall's rather sketchy description:
I was shocked to find my USB joystick to work in that game. That is so far unprecedented in CrossOver for Mac for me.
Anyway, the game shows some problems, like a serious delay in the menus. Most of the time, when the menu screen switches, the graphics don't get updated right away. This can result in serious confusion when pressing keys, for instance.
I tried it as well and can confirm that it works on my MacBook Pro 13" 2010 with OS X 10.6.7 and CrossOver Games 10.1.0.
In 10.1.0 I only did these three steps:
First I had some issues with the display size, but in 1.0.13 you can select 1152 x 720, 16:10 which works well ICM WITH "Wine T&L 32-bit" driver in Falcon4. 1280x800 didn't work quite good for me I had mouse problems.
I didn't do anything else. Works like a charm however (!) the menu could be slow, BUT if you hit a key or move the mouse around it speeds up the menu browsing.
I would almost say: gold!
Hi,
What release of this title do you refer to?...ie; CD/DVD. digital download, other?
Cheers!
I can ge it to install fine but its when i get to the main menu it stuffs up. When i start it without clicking anywhere, it looks fine and sounds work. But as soon i click anywhere on the main menu, the whole page messes up. It goes patchy and i can see parts of my desktop background. I can still click on the buttons but i cant see what im doing. I've also installed the 1.0.13 patch but nothing and have tried what Paulthetall said but nothing changed. Any ideas?
Hi,
...which version of crossover? What OS are you using?
What video card/chip does your machine have? What sort
or machine is it? It's nearly impossible to advise without
these facts - please tell us more =)
Cheers!
Artist Formally Known as Dot on 2011-11-15 06:39
oops, forgot.
Im have version 10.1.2
Im using a Macbook Pro lion 10.7.1
Processor 2.3 GHz Intel Core i5
Memory 4 GB 1333 MHz DDR3
Graphics Intel HD Graphics 3000 384 MB
owenbalfe wrote:
oops, forgot.
Im have version 10.1.2
Im using a Macbook Pro lion 10.7.1
Processor 2.3 GHz Intel Core i5
Memory 4 GB 1333 MHz DDR3
Graphics Intel HD Graphics 3000 384 MB
...ugh...<grin>.. as I've just replied to another post of yours, your
biggest hurdle here is always going to be the HD3000 GPU & drivers. If
this version of the intel HDxxxx GPU displays the same bad behaviors as
past revisions of the intel igp chipsets, I can tell you now there is
no single answer/resolve to problems you will encounter. Some apps/games
will run OK on it, others won't run at all, and the things that -do- run
may need a different bottle setup/tweak to work -- the actual workaround,
if any, tends to be app/game specific...
....there are a number of things you can try, as follows...
*..try enabling 'emulate a virtual desktop' in the Wine Configuration GUI
for the bottle in question. You can get to this via Crossover (Games) menu
-> Configure -> Manage Bottles -> highlight the bottle you want to work
on -> Control Panel -> launch the Wine Configuration item. Click on the
Graphics tab in the GUI that pops up - you will see the setting & checkbox
for what I speak of. Note that the default 'desktop size' is set at 800x600
-- you may set this to some other value (often 1024x768 is more appropriate)
but start at the default setting, because it's going to use less videoram...
..also note the Direct3D 'vertex' and 'pixel' shader switches there ; sometimes
altering these settings also can have a bearing on how things behave...
*...I'm not exactly sure how aware the wine core is about the HD3000 chipset,
and I should also point out that 384mb of videoram is not a lot to play with.
Worse case scenario is certain registry settings aren't enabled, and/or the
amount of videoram you have is being misdetected. To guard against this happening,
it's best to define the Direct3D registry entries. To do this, cut&paste the
following code into a plaintext editor ...
REGEDIT4
[HKEY_CURRENT_USER\Software\Wine\Direct3D]
"DirectDrawRenderer"="gdi"
"OffscreenRenderingMode"="fbo"
"RenderTargetLockMode"="auto"
"UseGLSL"="enable"
"VideoMemorySize"="384"
...then save the file and name it direct3d.reg or such. Now.. Crossover (games)
menu -> Programs -> Run Command ...select the bottle being worked on, and in the
'Command:' stringbox type regedit and click on Run. The windows registry editor
will appear, use the 'Registry' -> 'Import Registry file' menu item, navigate to
and select the 'direct3d.reg' file created above, then click 'Open'. You can now
close the registry editor..
...that much, just sets up the bottle registry in some sort of default state from
which you can work with..ie; change some of the registry values of the keys above.
You can read about these keys (and others) and the various settings available (and
what they do) over at winehq...see;
http://wiki.winehq.org/UsefulRegistryKeys
...the truly tiresome and arduous part, is determining what (if any) key values
(or combinations or key values/wine configuration settings) are actually required,
and this may well vary from app to app, and the only real way to fathom it out
is by good old trial and error. You can perhaps search about for references to
the HD3000 in winehq/wineskin ... such may lend a clue as to which keys values
need changing and to what for this graphics chipset ,,(with -any- app/game, and
see if the same works for -your- situation)...
Hope this helps...
Cheers!
The menu now works but when i start a mission or even click preview in the graphics settings a message pops up saying "Failed to setup rendering context. Press OK to Quit". Any idea what that means?
Thanks
...note, for future reference, if you edit your posts, like
you have done here, and substantially change the content of
what you have written (or ask another question), such edit(s)
never get an email notification sent out, and so myself and others
never know of any changes...ie; last time you posted it had
started working ; now that I get here hours later and only because
I wanted to reference what I typed here for someone else, do
I see you've edited your last post and have another problem...
... as I say above, you have to change the various key values,
one at a time, trying the alternative values as you go, and noting
any changes in behavior. Which one have you tried so far? Have you
tried the registry key changes mentioned in the first post here?
(I think that error message can link to offscreenrendermode
settings), but if it's not that then it could be an opengl failure
...and if it is that, there's probably no way around it...
... in any event, I don't own one of these chipsets, nor the game,
and all I can do is point you at things to try, and hope you do that
and report back what does any doesn't work. If you haven't already
tried installing directx into the bottle, try it...
Cheers!
Nope, cant get it to work. Installing DirectX into the bottle just causes it to crash on startup. And cant get it to work when changing the strings.
Thanks for your help though.
...it may be the intro movie crashing ...see;
http://appdb.winehq.org/objectManager.php?sClass=version&iId=14840
...try adding the --nomovie switch and see if it helps... else,
you would need to gather a debuglog so I can see what's going wrong.
The game should run on the hardware (it's an old game, so doesn't
require much) but being an older game means it uses the older directx
api and that can cause troubles...
Cheers!
How do i do that? I dont really know much about this stuff.
Thanks
http://www.codeweavers.com/support/wiki/mac/mactutorial/submittechsupportlog
...you use the same route to locate and run the program with the extra
-nomovie switch. Have you selected the video renderer option mentioned
by the poster above? (3rd posting) If it still doesn't work after
exhausting all options, blow the bottle away, and start with a fesh
bottle, a fresh install of the game (just the game), and apply the
registry key used earlier. Then create a debuglog as described above,
and just put +trace,+loaddll in the 'Other' stringbox and create the
log file (run the program, try to do whatever you do to crash it)...
...once you have the logfile, upload it to a public repo somewhere
(rapidshare, pastebin, google) and post the download URL back here ;
then I can have a look at what's going on...
Cheers!
CrossOver Forums: the place to discuss running Windows applications on Mac and Linux