2.8.3 wont work and if 2.8.2 crashes nothing works

[Angel]

Hi again

ok i downloaded the new one you created z-man, i put it in the folder but as soon as i click on the exe, i get the windows error message again, sorry.

i ran the windows debug programme and below is the information of the Call-Stack


i hope this helps

[Z-Man]

I guess we'll release official builds of whatever comes next after beta3 using all three compilers we have available: VC++ 6, VC++ 2003 and GCC. We'll see which one causes less problems for everyone.

[Walking Tree]

you need a vc++2002 ? or 2005 beta ?

i have next to no expierience with them, but if you need a test with one of them, i've got them here, my dad's a microsoft phreak...

[Z-Man]

No thanks, I guess. It's important that more than one team member can generate a build; some of us appear to own Visual Studio 6 (it's old and cheap), GCC is free, and VC++ 2003 costs nothing. Those are the options available, having the build done by someone else done with a more modern Microsoft compiler won't work. How are we supposed to debug as soon as something goes wrong? Just look at my cluelessness when it comes to problems with the Mac build.
There is also a cost-free compiler from Borland, but from my earlier experience, Borland is even worse at C++ standards compliance than Microsoft.

[klax]

z-man: at last I've updated the codeblocks projects to also build all the SDL libraries and it works. Debug libraries pending...

[Z-Man]

Cool. Note to others: I had to upgrade my code::blocks installation to load the new files. Maybe I can get some benchmarking done. The only thing I know so far is that GCC surely produces bigger files than Visual C++; after compression, the difference is below 100k, so not much of a problem.

[Z-Man]

Benchmarks are done:
http://forums.armagetronad.net/viewtopic.php?t=2658

Beta4 has a GCC build available done with klax's updated project files. Angel, could you test it? Direct link:
http://beta.armagetronad.net/fetch.php/ ... urce=sf_aa

[Angel]

Hi i downloaded the latest beta release via the link you sent me
I installed the game as normal but when i try to run it i get the error below


i did check and the var folder is in the game directory

i ran the windows debug programme and the results for the callstack are below


i also took a screenshot of the command thing, sorry, i'm not so technical lol it is a lil large so i've posted a link to it
http://angelic.tk/ArmagetronBeta/commandbeta4.jpg

is there anything more i could maybe do ??? just let me know

[Z-Man]

But actually, that's a partial success. I think your previous error happened before that. I just wonder why klax's binary worked and this didn't. Klax, any ideas why a build directly from CVS should do something different than one from a zipped source when it comes to the var directory?

is there anything more i could maybe do ??? just let me know

Not right now. Your_mom is getting the same error and I'll build a new installer with more diagnostic output and possibly a fix. Ha, got a second victim to test it on I'll get back to you. Thanks again so far!

[Z-Man]

New builds and instructions can be found here:
http://forums.armagetronad.net/viewtopi ... 7454#37454
Please test. There is no need for a run in the debugger this time, the information isn't really useful anyway.

[the pig]

I installed the game as normal but when i try to run it i get the error below


i did check and the var folder is in the game directory

I've never been able to use beta 3 or beta 4 because of this error. I've tried looking for the right directory (shortcut in program menu works), verifying directory is not read-only, etc...

I finally got it to work today by specifying the same var directory location the installer created on the command line. Hope this helps the rest of you having problems.

"C:\Program Files\Armagetron Advanced\armagetronad.exe" --vardir "C:\Documents and Settings\UserName\Application Data\Armagetron\var"

Tried a quick look through that code, but nothing jumped out at me. If it works with the path specified manually, the wrong path must be getting configured for the default case...

[Z-Man]

Welcome! Yes, passing the true directory as an argument can help. We could even tell the installer to automatically add it, but it would only work for the user who installs the game.

Could you run the alpha build linked to in my last post, too, and send over stdout.txt? Preferably, also by moving your old data directory out of the way first, so we see whether the creation works.

It's possible that there is some mixup when the path to the user data directory is determined.

[Lucifer]

In Xp and Windows 2000 (don't know about others), there's an "All Users" directory in Documents and Settings, isn't there? And your start menu is built using that and what's in your own directory.

Of course, it would be ideal if the game itself just worked from any directory without requiring special registry/shortcut hacks...

[dlh]

The Mac OS X version kinda had a similar problem. The user data dir was being but in the application bundle, which is not where I specified it to be. It was fixed by disabling some code in tDirectoriesCommandLineAnalyzer. Maybe this is a similar problem?

[the pig]

Could you run the alpha build linked to in my last post, too, and send over stdout.txt? Preferably, also by moving your old data directory out of the way first, so we see whether the creation works.

Sorry, tried but the server is down. The other thing I just noticed is that it acts differently based on where I run it from. I get the issue if I run it from the program menu or from a shortcut on the desktop.

If I run it from the command line, it works but with different settings. It is using the var directory created under the program installation directory.

So, one question is, how does the program determine where the var directory is? From the tests I ran, it looked like it was using the directory I run it from. I bet if I created a var dir in my desktop, the desktop shortcut would work.

One suggestion would be adding the var path it is trying to use to that error dialog that pops up.

I can try running that alpha tomorrow if the server is back up.