Compile Proplem

#1 Point your include path to dx9sdk/include and your lib path to dx9sdk/lib and also make sure they are on top of the list of directories, else the visual C libs will be used and those are like dx5 i think

#2 I had same prob after getting The SDK December update, uninstalling and installing the octo er version fixes the problem.

#3 Think I'm still using the older version too.

#4 Problem sorted just needed to make sure the lib files where copied from the vc++6 extras/lib folder to the libary folder in the SDK compile successful. Just need to switch to realease now instead of debug mode

#5 FYI the December update will NOT work with VC6. Use the October one, or get .NET.

#6 This probably marks the beginning of the end for VC6 support across the board - I'd make upgrading to .net a pretty high priority, as I imagine a lot of things in the next few months are going to drop VC6 support...

#7 Doesn't the .NET SDK require Windows 2000, 2003 or XP though?

#8 I'm not sure I follow. .NET applications may require those vintages of application. Torque, however, is not a .NET application. If you compile it with VC7 it may require the 70 runtime, but as far as I know that runtime will work on 98.

VC.NET may not run on 98, but if you're doing all of your development on 98... well... you may have bigger problems to deal with... :)

#9 Like many people here, I'm on a limited budget, and the cost of switching from TGE to TSE seems to be increasing.

With TGE, you can get away with using Win98 and a free compiler, or download a precompiled version. With TSE it sounds as if you now need to purchase VC7 or above, which in turn requires XP (which I would have no other reason for using), on top of the additional TSE license fee.

#10 Naturally, all that money goes directly to line our pockets... ;)

As far as I know, the only reason you can't use a free compiler with TSE out of the box is because we're not maintaining the makefiles for it right now. The reason we're not doing that is because we're working on other, more important tasks, like getting Milestone 2 done. If somebody wants to contribute a working makefile, I'll happily check it in.

We also have precompiled versions available, vis a vis the various demos we've released.

The cost of TSE is not any higher now than it was when we initially released it. If anything, it's cheaper because you're gonna spend less time dealing with brokenness. There are certain costs of business when you're a game developer - artists have to pay for Max or Maya, scanners and pencils and paints. Coders have compilers and text editors. Some things you can get for free, some you can't. If you can spare $150 or $250 to get TSE, surely you can manage $75 to get a copy of VS.net. :) (Or if you can't... you could spend the time and learn how to work GCC well enough to compile it for free. ;)

Count yourself lucky, artists have to _really_ shell out for the higher end tools...

#11 Do these comments by various people mean that support for vc6 will definatelly be droped shortly, i could do with an answer as my future spending decisions may have to feflect this.

#12 If you have a choice, get VC7. You shouldn't have one, though - Microsoft doesn't sell VC6 anymore...

#13 Its not like GG is dropping "support" for VC6, its basically that microsoft is releasing incompatible SDK's which TSE relies on.

Bitch to microsoft guys, not GG.

And get .net :)

It produces smaller executables anyway.

#14 Even the Microsoft site say they will no longer support VC6.

#15 The only reason why i had made a comment on VC6 is because i already purchased it 2 years ago, if VC7 is the way to go are you talking about the C++ version of .NET or the C# version.

#16 I got the linker error "cannot find d3d9.dll" message yesterday. It turned out that the version of D3D SDK I was using, dated Dec-04, stuck the "d3d9.dll" file in the "lib/x86" directory, not just the "lib" directory. I added the "x86"" path to the top of the list of Library paths in VC++.NET 2003 and it compiled just fine.

#17 The C++ version. Torque is not a .net application, and is not likely to become one in the near future.

#18 Thats not all that is dropping. MS no longer look at Win 2k as a supported platform starting with this release of the SDK!

I guess you can't expect someone to support old versions of software indefinitely. Though win2k is only 5 years old, I guess thats a lifetime in operating system software terms.