ZDoom

Thanks for the input. Comparing the two, other than the file names involved, I can see no obvious difference between the two.

However, prompted by your question, I went through the 16 projects in the solution and built them one by one. It's not any of the wadsrc projects that give the error, its the one called zdoom.

[edit] And I've just looked through all the properties for that project and I don't see anything that leaps out to me as being responsible. [/edit]

Well, just for info, (and a mmmmonster bump) I just formatted my HD, reinstalled Windows, reinstalled Visual C++ and all the other bits and pieces required to compile (G)Zdoom and... despite having a completely new and freshly set up environment, this "problem" persists when compiling GZdoom.

And to finally close this one off for anyone who is interested...

I, foolishly it would seem, thought that my Windows update setting ("You receive updates for Windows and other products from Microsoft update") included updates to directx. Apparently not.

I installed Media Player Classic on my newly formatted machine a couple of days ago and it told me that my directx end user run time files were out of date. So, I went to the MS directx site and downloaded their web updater. It updated both the runtime files and the SDK.

Doing this seems to have fixed the problem. I have compiled a few versions of GZdoom now and not got the temp environment message. Updating directx the only thing that I have changed since last seeing the message so I guess that must be it.

I've tried following the exact instructions on the wiki to get it compiled and got the exact same error when starting any level in the game.
It only crashed when starting any level, so it worked until then.

I've tried everything to get it running, even uninstalled my Jun2010 DXSDK and installing the older Feb2010 DXSDK, but that didn't change it.
I then tried messing with the lib and include loading order as described earlier in this thread. That didn't help much resolving this either.

However, the thing that did the trick was uing NASM 2.00 instead of NASM 2.10
So, maybe the compilation instructions in the wiki needs to be updated to rather read that you must use 2.00 and not the "above" bit, because it seems the above might count for up to a certain version above the 2.00 version.

The one thing I'd like to know is if Im running (compiling) zDoom 2.5.0 (latest official), do I still have to use the Feb2010 DXSDK, or may I install the latest Jun2010 DXSDK?
It that still an issue?

Oh, and I can confirm that upgrading the project to VS2010 worked just fine.
I'm using VS2010 Ultimate on Win7 64bit.
The Windows SDK I compiled against was 7.0A

That's a fixed problem (2.5 is old). The latest DX SDK works but its missing ddraw.lib so you'll have to copy that over. A tip to anyone that needs it the DX installers can be opened in 7z so you can get it without having to install it.

When will there be a new stable release that I can download from the zDoom site to replace 2.5?

Nobody knows, but the current ZDoom revision is quite stable. There has been a flurry of bug fixes in the last few week, half the bug forum has been cleaned out already. I think a new official version might happen in the coming month.

That said, I do encourage you to compile the head revision right now. [wiki=Version_history#Next_version]It's a lot nicer than 2.5.0 already[/wiki].

Great!
I'm downloading the head version now.
Which version of FMOD is required for the head version?

See [wiki]FMOD Ex[/wiki].