• Advertisement
Sign in to follow this  

going from Direct X 8.1 - Direct X 9.0c -- Direct Input Problem

This topic is 4660 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hey Guys & Gals, I've been working on a little side project off and on, and when i got back to it this time around, i decided to bump it up to directx 9.0 from 8.1. After fixing all changes, i finally got it compiling again. However, im having a problem with direct input that is not allowing me to generate debug info! :/ in the file im using DirectInput8Create(), i have included dinput.h, which seems to work fine, no compile errors, BUT, when it comes to linking the damn thing.. i get one of two errors if i use dinput8.lib, i get this error dinput8.lib(dilib2.obj) : fatal error LNK1103: debugging information corrupt; recompile module - ive reinstalled the directx sdk a couple times, and it doesn't go away, next step is to red/l the sdk i guess if i use dinput.lib, it doesn't even find the function soooo... hmph :( if i uncheck the generate debug info box it compiles fine, but i cant debug any help would be greatly appreciated

Share this post


Link to post
Share on other sites
Advertisement
that was like the first thing i tried buddy.. thanks though..
i guess this isn't a common problem, i hoped it might be... :sigh:

Share this post


Link to post
Share on other sites
This question came up here a couple of times before. Try searching the forums. I'm leaving work now, and can't look for it. If you haven't found it by the time I get home and back online, I'll see if I can find the solution. I just can't remember off the top of my head what it was.

Share this post


Link to post
Share on other sites
close visual studio, delete the release & debug folders as well as the *.ncb & *.suo (this one is hidden) files. Then fire it up again and recompile.

Share this post


Link to post
Share on other sites
Quote:
Original post by Dave Hunt
This question came up here a couple of times before. Try searching the forums. I'm leaving work now, and can't look for it. If you haven't found it by the time I get home and back online, I'll see if I can find the solution. I just can't remember off the top of my head what it was.


Thanks Dave, I have been searching through things a bit for a while now, i haven't found anything that matches my problem, maybe im just searching too broad of topics, but ive tried a whole slew of them, 'direct input' (huge list), 'direct input link', 'direct input error', 'direct input corrupt', and none of them seem to have the same problem :(, im still searching though. I have d/led the sdk twice now ( so the file was not corrupt ), and it was working perfectly when i was using the directx 8.1 sdk :/ Thanks for helping Dave, its much appreciated!

Quote:
Original post by MichaelT
close visual studio, delete the release & debug folders as well as the *.ncb & *.suo (this one is hidden) files. Then fire it up again and recompile.



doesn't work, and as this is not a VC .NET project, i do not have a *.suo file

Share this post


Link to post
Share on other sites
the latest, the april 2005 version
after reading the other post regarding the new version of directx, i decided to try it on my VC .NET compiler, works fine :(/:).. i really cant stand the new .net IDE, but oh well i guess, i wonder if direct x 9c will ever work with VC6.. i hope someone comes up with a hack, any idea why the new sdk doesn't work w/ it?

Share this post


Link to post
Share on other sites
Quote:
Original post by BlueJester
i wonder if direct x 9c will ever work with VC6..i hope someone comes up with a hack, any idea why the new sdk doesn't work w/ it


The thing is that it does not work with VC6's compiler. You can replace the compiler and linker with the Visual C++ toolkit and still be able to use that IDE. That's where the problem lies. However, there is no reason not to get something like Visual Studio 2003 IDE, which has a lot of features that VS6 does not, such as tabbed pages and line numbers to name a few. I say that matter of factly, I do know it costs a lot of money that people don't have, but it is well worth the investment, esp. if you are doing DX programming nowadays.

I don't have the specifc link on how to get that to work, replacing the compilers and linekrs, but maybe someone else does.

Share this post


Link to post
Share on other sites
Quote:
Original post by BlueJester
the latest, the april 2005 version
after reading the other post regarding the new version of directx, i decided to try it on my VC .NET compiler, works fine :(/:).. i really cant stand the new .net IDE, but oh well i guess, i wonder if direct x 9c will ever work with VC6.. i hope someone comes up with a hack, any idea why the new sdk doesn't work w/ it?


Microsoft has officially dropped support for VC6. They're on VS2005 and it's not profitable for them to support something that old.

I would recommend buying VC++ .NET 2003 Standard Edition. This gives you the new IDE and a (non-optimizing) compiler. Then, download the Visual C++ Toolkit as Drew suggested. This gives you the optimizing compiler. Then, point the IDE to the Toolkit's bin directory (in the Options dialog) and you now have a nice IDE, a more standards-compliant compiler, and you're ready to go with the latest DirectX SDK for about $89USD. (Maybe even cheaper if you are a student).


Share this post


Link to post
Share on other sites
thanks guys, i have Visual Studio .NET, currently, i just really cant stand the environment compared to VC6, plus F7 no longer is the default build, what is up with that?? lol... yeah im just ranting now, but thanks again, ill definitely look into that tool kit thing though, is that in the enterprise version of VC6 somewhere?

Share this post


Link to post
Share on other sites
If you have VS.NET 2003 Professional, you don't need the toolkit. It's just a free download of the compiler/linker/libs from VC++2003 professional (without the IDE).

I have to agree with you on the IDE changes. It took me forever to stop hitting F7 to do a build. I've gotten used to it, though.

Share this post


Link to post
Share on other sites
I had the same problem, and I just wanted to clarify the solution.

Downloading the Visual C++ Toolkit works. After the install, copy the contents of the Toolkit's folder into your Visual Studio/VC98 folder. You also have to manually move the compiler exe into your VC98/Bin folder.

I got a warning, but DirectInput stuff compiles and links fine now.

Thanks everybody!

Share this post


Link to post
Share on other sites
You can change the key settings since VC6. There's also a complete key set which has F7 still bound to compile (i'm using that one).

Go to Tools->Customize then press the button "Keyboard" on the bottom. Choose one of the schemes from the combo or modify one to your liking.

Share this post


Link to post
Share on other sites
You can just use the vc6 IDE with ms toolkit 03, I did for quite awhile.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement