Has the sound ever been fixed so that it works correctly with Audigy cards? At the moment (using 1.05), acceleration has to be set to basic for the sound effects to play.
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Indeed. I am using an Audigy card myself (Audigy II in fact), and sound plays just fine.
Jan Peter
Jan Peter
Audigy (not Audigy II) card.
Via motherboard with latest 4in1 drivers
Windows ME.
When using full or standard hardware acceleration, sound effects for units moving, etc play once, than never play again until the program is restarted. All sound effects work fine on basic acceleration.
However, I have other programs that work better with full acceleration, and it is annoying having to go in and change it every time I want to plau a different game.
Via motherboard with latest 4in1 drivers
Windows ME.
When using full or standard hardware acceleration, sound effects for units moving, etc play once, than never play again until the program is restarted. All sound effects work fine on basic acceleration.
However, I have other programs that work better with full acceleration, and it is annoying having to go in and change it every time I want to plau a different game.
VIA drivers have been know to be very buggy. You may want to investigate changing to default windows drivers.
Yes, that is true.
The Audigy (one) card comes with VxD drivers only. The Audigy II comes with both VxD and WDM drivers.
When I install the VIA drivers AND the Audigy VxD drivers, then I get the same problem. Sound effects play only once, then never again.
When I either ditch the VIA drivers completely, or install the Audigy WDM drivers, then sound plays as it should.
There is an incompatiblity between the sound implementation in Paradox games (EU2 has the same problems), the Creative VxD based sound drivers for the Audigy cards and the VIA 4in1 drivers on VIA based hardware.
The simplest way of resolving the problem (and getting rid of a whole bunch of other problems at the same time) is to completely remove any and all traces of the VIA 4in1 drivers, and to never install them again. Your graphics performance decreases slightly, but you gain a lot in system stability. All VIA drivers are bugged.
Jan Peter
The Audigy (one) card comes with VxD drivers only. The Audigy II comes with both VxD and WDM drivers.
When I install the VIA drivers AND the Audigy VxD drivers, then I get the same problem. Sound effects play only once, then never again.
When I either ditch the VIA drivers completely, or install the Audigy WDM drivers, then sound plays as it should.
There is an incompatiblity between the sound implementation in Paradox games (EU2 has the same problems), the Creative VxD based sound drivers for the Audigy cards and the VIA 4in1 drivers on VIA based hardware.
The simplest way of resolving the problem (and getting rid of a whole bunch of other problems at the same time) is to completely remove any and all traces of the VIA 4in1 drivers, and to never install them again. Your graphics performance decreases slightly, but you gain a lot in system stability. All VIA drivers are bugged.
Jan Peter
When you run the default installer (through autorun), then it automatically will install the WDM drivers for you.
The only way to get the VxD drivers with the Audigy II, is to run the driver selector program afterwards. In your case, you probably don't want to do that
Mind you, in the long run you will be better off by uininstalling those darned VIA 4in1 drivers, and stick with the default Microsoft IDE and AGP drivers. It will save you lot's of trouble.
Jan Peter
The only way to get the VxD drivers with the Audigy II, is to run the driver selector program afterwards. In your case, you probably don't want to do that
Mind you, in the long run you will be better off by uininstalling those darned VIA 4in1 drivers, and stick with the default Microsoft IDE and AGP drivers. It will save you lot's of trouble.
Jan Peter
What is a WDM driver and a VxD driver exactly? How are they different? Do they both perform the same with digital or anaolog speakers?
VxD based drivers are the traditional driver technique for Windows 9.x based OS'es, and have their roots in the aging Windows 3.x platforms. WDM (Windows Driver Model) is the driver technique for Win2K and higher.
Both techniques are fundamentally different, and thus not interchangable. The main difference, basically, is that VxD based drivers have to do everything with respect to manimulating the supported hardware. In the WDM model, the Windows kernel itself handles a lot of common functions between different hardware vendors, and only the low level hardware drivers need to be supplied by the vendor (hence the name miniport drivers)
With the introduction of Windows 98 SE (which more or less coincided with Win2K), Microsoft wanted to stimulate driver development for the latter platform. Because, to that point, driver development for Windows NT had lagged behind that of the Windows 9.x platforms. So, they added the Win2K driver engine to the Windows 98 SE kernel, so driver developers could concentrate on developing WDM based drivers, which are then installable on both Windows 98 SE (and ME) and Win2K.
As for supported features, that is basically dependant on the vendors in question. I would assume that the level of supported features is roughly the same, whether you use the VxD or the WDM based driver.
Jan Peter
Both techniques are fundamentally different, and thus not interchangable. The main difference, basically, is that VxD based drivers have to do everything with respect to manimulating the supported hardware. In the WDM model, the Windows kernel itself handles a lot of common functions between different hardware vendors, and only the low level hardware drivers need to be supplied by the vendor (hence the name miniport drivers)
With the introduction of Windows 98 SE (which more or less coincided with Win2K), Microsoft wanted to stimulate driver development for the latter platform. Because, to that point, driver development for Windows NT had lagged behind that of the Windows 9.x platforms. So, they added the Win2K driver engine to the Windows 98 SE kernel, so driver developers could concentrate on developing WDM based drivers, which are then installable on both Windows 98 SE (and ME) and Win2K.
As for supported features, that is basically dependant on the vendors in question. I would assume that the level of supported features is roughly the same, whether you use the VxD or the WDM based driver.
Jan Peter