TorqueDemo.exe 1.4 illegal operation failure

#1 Did you try running a debug build?

What's in the console.log? Anything foreboding looking?

#2 Ben,

Appreciate the rapid response. I post this information as soon as possible.

#3 Same problem here. AMD XP 1800+, GeForce4 MX 4000, 512 MB of RAM, Windows 98 SE. I'm on Linux now (I had to dual boot to see the 1.4, I want 1.4 for Linux!) and I uninstalled the demo but I'll try to get the log ASAP.

The view tool or whatever it's called did work though.

#4 TorqueShowToolPro worked for me as well.

Used VC6 to compile Torque SDK.dsw workspace. It produced identical warnings found here:
www.garagegames.com/mg/forums/result.thread.php?qt=36865
when compiling torqueDemo_DEBUG.exe.
additional info here:
techlord.blackeve.com/torquedemo1.4compile.txt

I proceeded to launch the torqueDemo_DEBUG.exe. No new console.log generated. I took a snapshot of C:\Torque\SDK\Example directory arranged by date:

Reviewing Gabriel's post leads me to suspect AMD XP or Geforce4:(

#5 I'm having a similar problem running demo.exe from the TorqueDemo-Installer-1-4.exe download and torqueDemo.exe from the TorqueGameEngineSDK-1-4.exe download on Windows ME.

The TorqueShowToolPro.exe in the SDK does work fine.

I blame Microsoft. :p

#6 I too, could not launch the v1.4 .exe, while the TSTpro opened just fine. I think this issue will be on a few machines running pre-XP OS's...just a note. This box and ma' other need some upgrading anyways, and with the mad tossing of laptops into the air at Wal-Marts around,lol, I should be able to get the nice upgrades of 1.4 working on some machine by the end of the year...:).

...and the closest I got was a version, compiled by a kind soul at the IRC MaxGaming channel which had the Unicode commented out and the preprocessor out as well. I got a window environment opened to a black hole and a frozen machine, eh. Wasn't really surprised on these older machines...just confirms a need to upgrade for the next generation, TSE, etal...! Just a minor setback.

Anyone know of some smokin' deals on a system out there; I need a whole new box with all the innards. I don't really want to assemble one on my own. Right now, I'm looking at a generic box with an AMD Athlon 64 3500+ S939 with a Dual NVIDIA GeForce 6600 GT 128MB graphics, running XP pro...that should hold me for a while, shouldn't it?

#7 If you run the debug exe, do it from your IDE so you can figure out WHERE it's crashing... Anything else will just be slow and painful. :)

It might be some version of a library or another innocent snafu that can be easily fixed. Eventually Torque will drift away from 98 suport, but it doesn't need to be any sooner than necessary. :)

#8 I don't have Visual Studio installed there. The only reason I booted Windows was to try TGE1.4. However, as a developer of casual games, I'd really appreciate the continued support for legacy OS/videocard/whatever as long as it doesn't require drastic efforts from your part, since doing otherwise gratuitously would narrow our potential customer base, which is clearly bad.

So I hope this get fixed soon. Although I'd really like to see the Linux version earlier though ;)

#9 As recommended I executed from torqueDemo_DEBUG.exe and it generated the error. I pressed the 'Debug' Button on Alert Dialog Box and a Debugger window opened. Here are snapshots of what it produced:


CXX0030: Error: expression cannot be evaluated.

I have to admit I'm not a seasoned C++ programmer, nor am I familiar with features of the IDE:(

#10 Do you have the latest drivers for your video card and sound card? I know NVIDIA has a recent driver. http://www.nvidia.com

Another thing to try would be to adjust the sound acceleration:

Start | Run | DXDIAG | Sound | Hardware Acceleration

#11 @Frankie: Alarming, the memory allocation seems to have failed. :-/ buf is NULL! No asserts or anything come up? Nothing dangerous sounding in the console.log?

#12 Ben, its doesnt get far enough to generate a new console.log, however, below is the only console.log file in the example directory dated 11/24/2005

techlord.blackeve.com/console.log

#13 @Ben: i dont think that the actual memory allocation is the cuplrit. but rather the function call above which returns 0 as the length of the buffer to be allocated. Allocating this buffer with 0 bytes results in no buffer at all and the pointer still pointing to empty space. I'm not sure if the pointer is NULL in this case but i think that derefencing a NULL pointer might be the crash here.

Since GetLogicalDriveStrings is a WinApi function defined in winbase.h maybe getting a new Platform SDK might help.

But the Windows Platform SDK doesnt support Windows 98 and VC 6.0

[quote]
System Requirements
Supported Operating Systems: Windows 2000; Windows Server 2003; Windows XP 64-bit; Windows XP Professional Edition ; Windows XP Service Pack 1




Hard Disk Space. Choose a disk drive with a minimum of 1 GB of free space.


High-Speed Internet Connection. If your connection speed is 56 Kbps or less, it is best to purchase the low-cost SDK CD (US/Canada or International) or install the Web Download.


Development Tools. To build the C/C++ samples, you must have a C/C++ compiler. If you are using Microsoft Visual C/C++

#14 First, you may want to change the first GetLogicalDriveStrings to GetLogicalDrivestringsA(), to be consistant.

To see what the error is, add this line after the first GetLogicalDriveStrings():

DWORD dwError = GetLastError();

This will give you an error code you can look up in MSDN (or in the header files...)

[edited]

As a followup, if the GetLogicalDriveStrings() is calling the unicode version (GetLogicalDriveStringsW()) due to the way it is compiled, then this will cause an error on the Win95 line (95, 98, etc), as Unicode is not supported by default on those operating systems (according to MSDN). Changing it to call GetLogicalDriveStringsA() in the first call would get around this issue.

#15 Mine crashes exactly same place as Frankie

#16 I made the change Jaimi suggested and now I get the error:

FileStream::_read NULL Destination pointer with non zero read request

in main.cc

// Set up the command line args for the console scripts...
Con::setIntVariable("Game::argc", argc);
U32 i;
for (i = 0; i < argc; i++)
>>> Con::setVariable(avar("Game::argv%d", i), argv[i]);
if (initGame(argc, argv) == false)
{

#17 Any progress with this bug? Since there's no 1.4 for Linux and TGE crashes on Windows 98 I haven't been able to see it :(

#18 The same thing happens to me on both of my machines running windows 98 se 1 of those systems is an AMDk6
256mb ram
3dfx Voodoo 3
YADAYADAYADA

the other an

athalon 1.2ghz
512mb ram
Nvidia Gforce2
YADAYADAYADA

The results the SAME. The problem is not related to hardware... And I'm even about to install Windows ME which I think will do nothing since it's just a buggy hacked version of win98.

The question is Does it run for anyone? I assume ofcourse that it runs on XP. That's okay I suppose but I just bought it and though I could go buy XP tommorrow I'd rather download an older version that ran in win98.

-Requests Re-release of 1.3.0 for windows until 1.4.0 is repaired

#19 P.S. I forgot to say that the linux version of 1.3.0 Ran, though slowly, it ran.

#20 I dont think the problem is with 1.4 it's win98 and ME dont have unicode support. The fix is to install unicode dll from MS or rework 1.4 to take out unicode references. The real fix is to have the engine detect the os and take care of it. MS says that win98 based machines are only 5% of the market and dwindling as time goes by. In a world market place it makes sense to use unicode.