Indigo Prophecy Forum

This is a community forum and not official technical support. — If you need official support: Contact Us

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

Installation works, starting up the game doesn't

I've installed this game via steam download. When I double-click it in ym steam games list, the steam window "launching game" comes up and closes after 2 seconds. Nothing more happens.

On another PC it just works. The difference between both PCs is: onboard sound/ati-video vs. creative x-fi/ nvidia card. On the PC with the creative x-fi soundcard and the nvidia it works out of the box.

The weird thing is, if I run the program in a terminal, I don't even get an error message - the game just doesn't start up.

I already installed the redistributables of visual studio - nothing changed.

Crossover Games 8.1.4 - Kubuntu 9.10.

Any thoughts?

You have 2 different PCs running Crossover Games 8.1.4 and Kbuntu 9.10. and one works right out of the box and one doesn't?

In this thread, it appears someone was potentially having an audio problem on Linux as well:

http://www.codeweavers.com/compatibility/browse/name/?app_id=4174;forum=1;msg=70664

I'm not sure if they might be related.

abeta wrote:

You have 2 different PCs running Crossover Games 8.1.4 and Kbuntu
9.10. and one works right out of the box and one doesn't?

That's exactly how it is. One PC is works as a media-pc. Both PCs run Kubuntu 9.10 and Crossover Games 8.1.4. PulseAudio runs on both systems - but I don't know much about the linux sound system.

abeta wrote:

In this thread, it appears someone was potentially having an audio
problem on Linux as well:

http://www.codeweavers.com/compatibility/browse/name/?app_id=4174;forum=1;msg=70664

I'm not sure if they might be related.

Thanks, I'll try and report.

Did you emulate a virtual desktop?

I haven't played with Linux in a long time but I was wondering if there was a way to just disable the sound outright as a quick test.

update:

I tried:

  • emulating a virtual desktop
  • disabling the soundcard in BIOS (as I get it, this does NOT disable pulseaudio, but the driver for the soundcard)
  • several steam launch options in different variations (-dxlevel XX, -nosound, -autoconfig)

Nothing worked so far.

Blah, I hate stuff like this :).

I don't know, might be worth trying the suggestions on pulseaudio. I don't know enough about Linux to be of much help though. Hopefully someone else has some ideas.

overd0se wrote:

update:

I tried:

  • emulating a virtual desktop
  • disabling the soundcard in BIOS (as I get it, this does NOT
    disable pulseaudio, but the driver for the soundcard)
  • several steam launch options in different variations (-dxlevel XX,
    -nosound, -autoconfig)

Nothing worked so far.

Hi,

Let me get this right...you have 2 machines, both running the same version
of Ubuntu, both installed with the same version of crossover games, and yet
the same game when installed on both computers, only works on one of them and
not the other?...(this looks the case, but I like to confirm ;)

If that's so...and if it were pulseaudio being the culprit, then the only thing
I could think that would cause that is different pulseaudio configuration ..or
dramatically different performance being displayed by the soundcards involved,
and or the relative performance of each machine. That is to say, pulseaudio
is a sound server (software daemon process)...it's not a driver as such...and
as you've found out, even disabling the BIOS option doesn't stop the pulseaudio
process from starting/running...
...if you want to remove pulseaudio from a Ubuntu
system, the best place to look for clue on that, is over on the Ubuntu forums. If
you search for "how to remove disable pulseaudio" on those forums, you'll get hits
explaining how to do it (the procedure differs depending on your Ubuntu release)...

That said, this doesn't appear to be a pulseaudio issue to me at first glance - I
think I'd be more suspicious it's the Ati video chipset/drivers doing this..could
you include more detail in this regard please?...ie; both graphics card models,
how much ram they have onboard, which driver/version of same you're using with
each card...stuff like that...

...I think I'd be guessing without those details...but if I wanted to madly guess,
I'd imagine moving the nvidia card/drivers from the current box into the box that
currently runs the Ati card would be a fairly conclusive test case...

...you could likely also see this in the winedebug +d3d channel if you're into
diffing log files against each other to discover when/what/why things are different
between the two setups...

Post back your video hardware/driver details first, then it'll be easier to understand..

Cheers!

Quick question since I'm not by any stretch a Linux person :).

It's a daemon right? If you disable or stop the daemon doesn't that prevent it from loading into Linux? Or does it still load and is just not active only than listening to see if it needs to be loaded?

PS - Not to distract from Don's theory of it not being a pulseaudio problem. I'd believe him before believing me :).

@abeta -- what you say (about daemons) ia typically correct behavior, however
some daemons are worse than others. For example, although you might disable/stop
the daemon from running, there maybe other configurata/system settings that rely
on the daemon running -- so in effect, something like the following can happen ;
if you disable/stop the daemon, you effectively disable/stop all sound replay, due
to the fact there's no automagic way to fallback to the alsa driver layer - or,
some other configuration tells the application layer to expect a sound daemon to
be running and to use that (even if it's not running), so at best the application(s)
may start but have no sound, or at worse the application(s) may not start because of
of a sound initialization error (due to the fact the daemon isn't running).

If it just stops the application from running then it might not be too bad as a quick test, but if it prevents the system from coming up maybe not so good of an idea :).

Artist Formally Known as Dot wrote:

Let me get this right...you have 2 machines, both running the same
version
of Ubuntu, both installed with the same version of crossover games,
and yet
the same game when installed on both computers, only works on one of
them and
not the other?...(this looks the case, but I like to confirm ;)

That's exactly how it is.

I now installed an nvidia card for testing. Result: game doesn't start. But maybe there's light at the end of the tunnel, it produced output in the console:

user@user-desktop:~$ /home/user/Desktop/Indigo+Prophecy.desktop
<unknown program name>(2572)/ ClientApp::doIt: Creating ClientApp
test: 448: Illegal number:
test: 448: Illegal number:
test: 448: Illegal number:
user@user-desktop:~$

It doesn't seem to be the ati driver...

I also tried removing PulseAudio using a Ubuntu Tutorial - no effect. I'll try a different tutorial soon (there are different ones out there for 9.10).

My Hardware details:
PC giving me prophecy:
01:00.0 VGA compatible controller: nVidia Corporation G80 [GeForce 8800 GTS] (rev a2)
nvidia driver version 185.18.36
04:02.0 Multimedia audio controller: Creative Labs SB X-Fi
Pulseaudio& OS driver
(Kernel: 2.6.31-17)

PC refusing to launch the game:
01:00.0 VGA compatible controller: nVidia Corporation G72 [GeForce 7300 SE/7200 GS] (rev a1)
nvidia driver version 185.18.36
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
Pulseaudio & OS driver
(2.6.31-17)

Thanks for your support!

overd0se wrote:

Artist Formally Known as Dot wrote:

Let me get this right...you have 2 machines, both running the same
version
of Ubuntu, both installed with the same version of crossover
games,
and yet
the same game when installed on both computers, only works on one
of
them and
not the other?...(this looks the case, but I like to confirm ;)

That's exactly how it is.

I now installed an nvidia card for testing. Result: game doesn't
start. But maybe there's light at the end of the tunnel, it produced
output in the console:

user@user-desktop:~$ /home/user/Desktop/Indigo+Prophecy.desktop
<unknown program name>(2572)/ ClientApp::doIt: Creating ClientApp
test: 448: Illegal number:
test: 448: Illegal number:
test: 448: Illegal number:
user@user-desktop:~$

It doesn't seem to be the ati driver...

I also tried removing PulseAudio using a Ubuntu Tutorial - no
effect. I'll try a different tutorial soon (there are different ones
out there for 9.10).

My Hardware details:
PC giving me prophecy:
01:00.0 VGA compatible controller: nVidia Corporation G80 [GeForce
8800 GTS] (rev a2)
nvidia driver version 185.18.36
04:02.0 Multimedia audio controller: Creative Labs SB X-Fi
Pulseaudio& OS driver
(Kernel: 2.6.31-17)

PC refusing to launch the game:
01:00.0 VGA compatible controller: nVidia Corporation G72 [GeForce
7300 SE/7200 GS] (rev a1)
nvidia driver version 185.18.36
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)

Pulseaudio & OS driver
(2.6.31-17)

Thanks for your support!

Hi,

Okay...I see you've removed the Ati videocard from the equation...
that's one step closer to an equal playing field, however be aware
that a geforce7 chipset isn't as capable as a geforce 8 (number of
hardware shader pipes iirc)..so be aware you can't directly compare
results between the two....

...I know I'm asking you to remove screws and swap soundcard as a 'sure
test'....but...if I was there facing this problem, it's certainly a
something I'd try before I went futzing further with software looking for
the cause...ie; disable the onboard intel-hda audio in BIOS and try the
SB X-Fi and see if it changes anything (as matter of course, I'd try the
gf8 card in the same box as well ;)....but that's up to you, ok?...

The only thing that immediately springs to mind, is that many intel-hda
chipset/codec combinations have a have a tendency to initialize as a
sound device with a default sampling/playback rate of 48KHz -- many programs
(including native linux ones) simply refuse outright if they see this and
were looking for 44.1KHz instead. The intel-hda chipset is of course capable
of this, it just defaultly doesn't get set up that way - SB Live!/Audigy(2)/X-Fi
etc cards don't have this difficulty (multiple PCM playback channels, one of
which always reports 44.1KHz if memory serves)...

I'm not sure if it applies here, but there was a recent posting from our illustrious
Cupcake Ninja that -may- be related here...see;

http://www.codeweavers.com/compatibility/browse/name/?app_id=6160;tips=1

[bottom of that page]

FYI, I've seen that fix work on a couple of other title besides L4D2..

If you wish to generate some debug logs (one from each machine) and hoist them
to a public repo (ie; rapidshare.com or similar) and post a link back here,
I can grab them and have a look for anything obvious -- how to do that, see;

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

possibly the most useful channels will be --debugmsg=+seh,+trace,+dsound,+dsalsa

There's a complete list of debug channels you can look at over on WineHQ ;

http://wiki.winehq.org/DebugChannels?action=show&redirect=WINEDEBUG

Keep me posted with your progress...

Cheers!

1 to 13 of 13

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi01LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzA4NjEzODE4LCJjc3JmX3Rva2VuIjoiNE13a3c0cENiSHZ6S3NzcCIsImdkcHIiOjB9