Vista API changes?

[B_Level]

Does anyone know/heard of any changes to the Windows API in Vista that would directly affect game development. I know about all the DirectX 10 stuff but that doesn't seem to be to much of an issue. I had heard that they were totally rewriting Windows from the ground up. Basically, I'm wondering if all my old source code will compile fine!

[Xiotex]

It depends - if you are moving to Visual studio.net 2005 then in theory the string functions are now deprecated in favour of more 'secure' versions and where you can save game data has become more secure.

[Phil Steinmeyer]

The one issue I've noticed in testing a couple of my games against a Vista R.C. 1 system is that there are some issues if you use the 'standard' sound calls (i.e. WinMM/WaveOut, rather than DirectSound).

In one case, using FMOD, I had defaulted the game to use Win_MM, but, at least on my one Vista tester machine, that results in laggy sound. I will probably switch to DSound for that.

In another case, using my own home-rolled system with WaveOutWave, I found that adding a call to waveOutGetPosition within my sound buffer refill thread resolved an issue where the sound buffers were not refilling fast enough, resulting in scratchy sound. I think I have another thread in this forum discussing this latter case a bit further.

[James C. Smith]

It depends - if you are moving to Visual studio.net 2005 then in theory the string functions are now deprecated in favour of more 'secure' versions and where you can save game data has become more secure.

Or you could continue to use the compiler you use now and chances are your game will run fine in Vista.

One of the things that makes Windows popular is its ability to run programs that were designed to run in Windows.

[Odin]

We've also had some fun issues with the program not coming properly back online in full-screen after a wakeup. Anyone encountered that?

Allan