Hey MT whassup mate?
Thanks for your help. Well I have good news and bad news. The good news is, I FINALLY got the damn game function somewhat properly now. You wouldn't believe some of weird ---steaming pile of meadow muffin--- that goes on with this game. What was really driving me up the wall was the fact that my Escape key didn't work, like....AT ALL in the game! It took me hours of trial and error messing around until I figured it out and narrowed it down to vJoy. For sosme stupid reason having the "rY" Axis enabled in vJoy causes the game to render my keyboard's Escape key absolutely useless. Why in Sam's Green Hell this is, is beyond me! Anyway that's taken care of.
Now...further good news.....I've come to the conclusion that it's fairly safe to say that the copy of the game I d/led is in fact the 1-Disc DVD version. Now why in the world my original 2-Disc PC CD-Rom version of OR2K6 won't launch at all is the biggest mystery I've ever seen. Perhaps they discontinued that version for a reason. It is afterall, the very first edition of the PC version of the game. Maybe it's disc drives but maybe it's Securom. Who knows? In any case the DVD image I have now is fully working which brings me to the third piece of good news.....
Outrun FXT is WORKING(well, almost, but I'll get to that in a second). I have tested out all the features of the hack and everything seems to be working in the game. I figured out why FXT was crashing and solved the issue. I have to say Howard, you've done a marvelous job with this hack. The fact that I can map views as well as gears to individual buttons is pretty awesome! I haven't tried any of the texture packs or the radio options yet but I'll get around to those soon.
OK now for the bad news.......the MAIN reason i was excited about this hack and have been frothing at the mouth over the thought of using it, is....yes, you guessed it.....the Force Feedback. Simply put, the FFB feature is not working. Here's what's wrong in a nutshell....having the "Enable Force Feedback" box checked in the FXT Config options is fine if I set device # to none. But changing it to #7, which is where my FFB wheel is in the Windows Device registry, causes FXT Troubleshooter to not function. If I leave FFB enabled and device ID at #7, FXT will launch the game, and sit in the taskbar like it's supposed to, but then it ceases to work, because right clicking or double clicking the icon does NOT launch the troubleshooter debug menu. Furthermore the app is almost certain to crash no more than a couple minutes into the game. Secondly, if I unplug all my USB controllers and leave only the wheel, and then select FFB and Device # at 1, I STILL get no reaction from the game. Could it be that the default values in the FFB.ini file are very low and I need to increase them? If so, I would like to know more about the parameters of the FFB.ini and just how far I can max those values? Can the Multipler be maxed to say 99,999?
Howard if you're reading this please assist me in any way you can. I'm really curious as to what is causing FXT to function improperly by setting the FFB Device ID # to 7? Otherwise the app is great.