VOGONS

Common searches


Search results

Display options

Re: Nascarheat (2002) - Digging Deeper

in Windows
I suspect the MAX_FILES is set to 22 somewhere, due to PC limitations at the time. It'd be great to be able to increase this to 43 Would anyone know how or where to change this? The code here looks like it's checking the MAX_FILES limit: http://i.imgur.com/z1YuCb3l.png If you could upload an …

Re: Nascarheat (2002) - Digging Deeper

in Windows
Zuh? I have no issues running the game from a d:\games\ subfolder. Maybe it's because I've used a "NASCAR Heat Essentials" package and not a retail game? But there are hardcoded paths and registry locations in the executable and game writes files there. Or maybe you have UAC disabled and\or running …

Re: Nascarheat (2002) - Digging Deeper

in Windows
Unfortunately, I couldn't find any working references for the vertex damage modifiers. So I resorted to the brute force: I've ripped all floating point constants used in the code and converted them to the CheatEngine table. All 728 of them. So now, anyone willing to spend time modifying those …

Re: Nascarheat (2002) - Digging Deeper

in Windows
Thanks! Couple of clarifying questions: I don't have the options.cfg file in the mod folder, only mod.cfg . I've assumed that mod launcher automatically renames it to the options.cfg . Is it so, or I should manually copy it as options.cfg ? I'm completely new to this game and it's mod system, so …

Re: BreakQuest by Nurium vs Win8.1 64bit fmod error?

in Windows
VirtuaIceMan wrote: Could it be related to msvcrt.dll then? The game works at work (Win7 64bit) but not at home (Win8.1 64bit). Maybe different versions of msvcrt.dll though. Personally, I don't think so. Anyway, putting msvcrt.dll in the game folder would be enough (as with sdl.dll), no need to …

Re: Nascarheat (2002) - Digging Deeper

in Windows
Just a heads up: Nascar Heat really-really has to be installed in "Program Files" directory. It's hardcoded and this leads to all sorts of issues and unnecessary workarounds (admin privileges, etc). I've circumvented it by creating a directory symlink named "Nascar Heat" in "c:\Program Files (x86)\ …

Re: BreakQuest by Nurium vs Win8.1 64bit fmod error?

in Windows
I've looked at this and it doesn't looks like FMOD issue. Actually game is trying to find files in folder .\noCode and fails. First three files I've tracked (it's ton of them in the code): ├───mon │ Drx-noex.oxm │ └───sfx └───pills ball_speedUp.ogg ball_speedDown.ogg ...etc Feels like game falls to …

Re: MechWarrior 3 on Windows 7: Yet ANOTHER Solution

in Windows
7: Go into Task Manager and right click on Mech3.exe. Set the Affinity to CPU 0 and CPU 0 ONLY It would be easier to patch Mech3.exe with imagecfg to force single-cpu mode, than manually assign affinity at every launch: This command is probably optional. It sets the exe to use only one CPU: …

Re: Viper Racing vs modern graphics card!

in Windows
Does everyone need a separate fix though, depending on how much memory their graphics card has? No, the fix will work for everyone. For those, who interested: Viper Racing uses slightly different (older?) version of the game engine than Nascar but the bug is absolutely the same as Nascar's (tries …

Re: Viper Racing vs modern graphics card!

in Windows
The problem seems to be pretty similar to the Nascar situation in that the reported vram is to big to fit into a 32 bit integer causing a change in signedness... Thanks! Seems like there should be an Application Compatibility Toolkit fix that fixes this... Yeah, it should, so we wouldn't have to …

Re: Viper Racing vs modern graphics card!

in Windows
Thanks for that! After reading your explanation I was able to get around a similar issue with 3dMark2000 which had been nagging me for a while. http://www.vogons.org/viewtopic.php?f=8&t=33579&p=406996#p406996 Glad to be of help! Personally, I'd enjoy some details about what was the problem and how …

Re: Viper Racing vs modern graphics card!

in Windows
If you run the game with Compatibility Mode of Win95, it then generates some log files in the C: drive, where it reports: vid: 0 meg card (reported:0.523438) vid: using AGP textures unsupported: 0 megs of vram So I think it's misdiagnosing my 4GB GTX 980 card (or it's yet another Nvidia driver …

Page 1 of 1