Blood Bowl Forum

Well, I installed the game from the CD that I got... it installs ok, but it doesn't work. This program is now available from Steam, I had thought about downloading it from them, I wish there was a way to do that without buy another copy.

Hi,

Well...maybe it -can- run from CD, but you haven't told us what platform/OS you are using,
what videocard/drivers you are using, what version of crossover...what the error message
(if any) are....etc etc...however...

There's a discussion regarding getting this to run under wine ...see;

http://appdb.winehq.org/objectManager.php?sClass=version&iId=17179&iTestingId=42454

It looks like there's a reasonable amount of non-trivial work to do to get this title
running - by the looks of it, you'll need at least .NET 2.0 installed, possibly directx
runtime, maybe one of another of the visual C++ runtime packages...and a number of registry
tweaks ...hope this helps...

Cheers!

I have a Nac Pro OS X Leopard, with 12 gb Ram, a ATI Radeon HD 4870 512MB Video Card.

After following the above link and poking around a few other places, I’m finally running Blood Bowl v1.1.3.3 under CrossOver Games v8.1.4. Here’s the short of what I did:

1. I installed the game under Windows by using Boot Camp. I authenticated the game. I updated it to v1.1.3.3 by running autorun.exe, which is what the desktop shortcut points to. I later copied this clean install over my install within CrossOver.
2. Next, I created a WinXP bottle within CrossOver.
3. I installed “Microsoft .Net Framework 2.0” into that bottle.
4. I installed “Microsoft DirectX Runtime - Modern” into that bottle as well. This may be provided by the game, but I manually added it anyway.
5. I then installed the game into this bottle. The install repeatedly hung during its “Test Firewall” phase, which is after it copies all the files and after it asks to authenticate the serial number. (Incidentally, this happened on three separate installs.) To remedy, I forced the installer to complete by using the corresponding CrossOver Games button.
6. I copied my Windows install over my bottle’s install. The two target directories are C:\Program Files\Cyanide\Blood Bowl and the corresponding Blood Bowl directory under My Documents.
7. At the above link, nab suggested the following registry changes:
   "DirectDrawRenderer"="OpenGL"
   "Multisampling"="disabled"
   "OffscreenRenderingMode"="fbo"
   "PixelShaderMode"="enabled"
   "UseGLSL"="enabled"
   I changed all minus the multisampling, which I couldn’t find after searching the bottle’s registry.
8. Some people reported a problem with the refresh rate setting that’s specified in their config.xml. This is located in \My Documents\Blood Bowl, but I didn’t have this problem so I let it be.
9. Because the start menu and desktop shortcuts point to Blood Bowl’s autorun.exe, and because autorun.exe repeatedly fails (it’s basically a splash screen and auto-patcher), I created a shortcut to C:\Program Files\Cyanide\Blood Bowl\bb.exe, which is the game’s actual executing file. This means I’ll have to manually patch the game once new content arrives.

And that’s it. So far I’ve played one single-player match and one of the tutorials. With my iMac 2.8Ghz, I can slide the graphics up toward an acceptable quality.

One caveat is that the game must authenticate with a server before you can run it. This is the activation code that’s located in the manual. You must enter the player key after the activation code registers. Blood Bowl’s authentication server will only allow three authentications, so you’ll either need to contact them when exceeding this three install limit or use the deactivation shortcut that’s within Start Menu > Programs > Cyanide > Blood Bowl. I'll submit screenshots for approval. Best of luck to you all.

(Oh, and all of this was from the DVD version, Dark Elves Edition.)

I thought that I opened my big mouth too soon because, after posting the above, Blood Bowl crashed during half time of my first tournament. Afterwards, I rebooted the bottle, played an uninterrupted single-player one-off match, and then I started a campaign in which I've played four complete games without interruption. If I were smarter, or of if I actually knew how to troubleshoot things Wine-related, I could better describe this aberration.

Hi,

To debug the crossover/wine process, see the following;

http://www.codeweavers.com/support/wiki/submittechsupportlog

In this case, if you grab such a log, you can gzip it and upload
it to a free public repo (like rapidshare or the like) and post the
URL back here so people can download it and have a look.

...or...

To debug the mainstream wine process (not crossover/wine) see;

http://www.winehq.org/site/docs/wineusr-guide/x543#AEN545

In this case, if you grab such a log, you can gzip it and upload
it to the WineHQ AppDB entry for this title ;

http://appdb.winehq.org/objectManager.php?sClass=version&iId=18255

Hope this helps...oh, and the debug channels available for mainstream
wine are the same in the crossover/wine case, just so you know ;)

Cheers!

That's good info, Don.

The game has run flawlessly since its first hiccup. I'll read the links and follow protocol. I want to learn to decipher this stuff, so hopefully some kind soul will let me follow along when I post a crash log.

Best,
Russell

Artist Formally Known as Dot wrote:

Hi,

To debug the crossover/wine process, see the following;

http://www.codeweavers.com/support/wiki/submittechsupportlog

In this case, if you grab such a log, you can gzip it and upload
it to a free public repo (like rapidshare or the like) and post the

URL back here so people can download it and have a look.

...or...

To debug the mainstream wine process (not crossover/wine) see;

http://www.winehq.org/site/docs/wineusr-guide/x543#AEN545

In this case, if you grab such a log, you can gzip it and upload
it to the WineHQ AppDB entry for this title ;

http://appdb.winehq.org/objectManager.php?sClass=version&iId=18255

Hope this helps...oh, and the debug channels available for
mainstream
wine are the same in the crossover/wine case, just so you know ;)

Cheers!

I've gotten Blood Bowl's autorun.exe to (somewhat) work by following Don's advice in this thread. He says, "Some online registration schemes use ieframe to hoist the registration GUI."

I installed IE 8.0 and all of its dependencies from within regular Crossover. Autorun.exe now runs, but it grumbles about an unhandled exception and it doesn't correctly display the splash-screen. I can now successfully autopatch Blood Bowl (which I guess isn't that big of an accomplishment), and since the game already runs well under CrossOver Games, I'm a tall, happy man.