Cruiser

Yeah ok. It's just showing the same error as in the other cases, but ok, if you can use this offset for anything, I'll provide this also. Saved game? I did not save the game while testing. I'm a little at loss here .... help me

Yes, just tried this with the /w1 option also. First perscan starts with the collapsed intruders section, and an arrow pointing up (see image in last post). Then when I try to drag it, it changes to a double arrow (up and down). I also took a screen shot of this. If I then again try to drag this section (with the double arrows) it CTDs instantly.

I got a CTD with intruders in SF v1.00.12.02 in full screen (1024x768) just now. And I have an idea (partly) why it didn't crash in the other tests with SF version. I noticed during a test that the PERSCAN looked like this. As you can see the intruders section where collapsed. When I tried to drag it open, it CTD'ed instantly. I tried this twice to be sure. I've updated the logs mentioned in my previous test report with the CTD logs. I will now test the /w1 mode and see if it behaves like this also.

Ok, I've been doing some testing on the intruders / PERSCAN CTD issue. I've uploaded all log files for download. *********************************** TEST 1, Original D2D v.1.00.08. ran with /d2 /w1 - Started new game, ROAM + NPC auto gen, got intruders and CTD'ed. Logs are included in the file mentioned above. - Started new game, ROAM + no NPC auto gen, ran for approx. 12 hours in PERSCAN while all marines on search duty (like when intruders board my ship) , no CTD. Logs are also included even though no CTD. *********************************** TEST 2, D2D v1.00.11 (by updater util), ran with /d2 /w1 - Started new game, ROAM + NPC auto gen, got intruders, CTD ************************************ TEST 3, D2D -> SF v1.00.12.02 (custom build that you sent me), ran with /d2 /w1 - Started new game, ROAM + NPC auto gen, got intruders, no CTD - Just to try, I loaded my old save game but even after many tries, no CTD ******************************** Bottom line: I was able to get both D2D v1.00.08 and D2D v1.00.11 to CTD just by starting new game and run until intruders boarded my ship. I ran in PERSCAN all the time, but did only CTD when I was boarded. I was not able to get the SF v1.00.12.02 to CTD, even when, as a last resort, I tried loading my intruders save game. No CTDs. Note that sometimes had to try several times to get the CTD with TEST 1 & 2. Sometimes being boarded by intruders did not cause my machine to crash. But even with intensive testing, I could not get SF v1.00.12.02 to crash. I can't conclude anything though because I could just have been "lucky" knowing that the D2D version did not crash in ALL tests. I will of course also be testing in full screen, and still try to see if I can get the SF version to crash. Will let you know if I'm successful. Well thats all for today, please tell me, if I screwed up the test scenarios somehow. Thanks, Cruiser.

Understood. I'll get right on it this weekend. I'll write exactly what I did in the test, so you can correct my in any mistakes.

quote: The saved game you sent me and the log, showed that there was planetary activity. There wouldn't be any planetary activity if you were using a NEW and CLEAN profile while you were in space. Yes, that log was from my old Starforce folder which I played with for a while before the testing. I looked in the fresh install, and it hadn't any log information. (yes one log file with one file stating that some fx module was being initialized if I remember correctly). quote: And if the intent is to prove that it is intruders that are causing the problem, why do you need to save and restore the game? If its the intruders causing it, then it should eventually crash as long as they are on board; without you having to save and restore. When testing the intruders issue, I only get CTDs 80% of the time. Therefore the save before testing. quote: You are continuing to confuse this issue.

Yes, I will do exactly as you write in your mail. In case I didn't make it clear before, then I've tried to: 1. uninstall UCAWA and delete folder 2. re-instal and run updater -> D2D v1.00.11 3. Start new game 4. Wait for intruders 5. Save the game. 6. Restore it and watch PERSCAN 7. CTD. Tried with both the Megaron and MK3 because I realize that I always per reflex start with the Megaron. Thanks.

quote: So what you're saying is that the D2D 1.00.11 and the Starforce 1.00.12.01 builds both give you a CTD when viewing PERSCAN if intruders are on board? Yes, with the exception of the debug build, which never crashed once. quote: You might want to start a new game, go somewhere where you don't start a chance of intruders showing up (e.g. one of the sub-regions in Jupiter) and run some tests again. I don't believe that this has anything to do with intruders and the only way to be sure, is to remove them from the equation. So, do this and give you personnel orders so they move around the ship and view them from PERSCAN. Ok, I'll run some tests the next few days. I'll also let it be in PERSCAN all night. Does it remove intruders to disable NPC auto generation? quote: ps: Did you get my email? If so, please send me the requested file. Just sent it.

I just tried a clean D2D install, applied the Starforce INI archive + update 1.00.12.01. Still CTDs in PERSCAN when I've watched intruders for a while. Just so you know, every other aspect of UCAWA is very stable on my machine. I have let it run for several days, entered FP mode, attacked bases and never one CTD. Only intruders CTD seems to persist.

Ok I will try to be more specific. I wrote "It seemed to result in the same CTD's as above". I meant the intruders CTDs. Still the same. If I experience any other crash than the one I've been posting about I will let you know. I've never had one CTD anywhere else in the game while we tested this. If I've indicated this then I'm sorry for the confusion.

I just re-downloaded the file, and re-applied it to my Starforce folder. Still CTDs. I will now try to re-install D2D, apply the Starforce ini, protection and exe files again to see what happens.

Ok, sent the files to your profile email. Files are from my fresh D2D install with applied 1.00.11 by the updater util. BTW, I noticed some debug log files in my folder also. Just tell me if you want them. Again, thanks for helping me out.

Ok then UCAWA -> Universal Combat A World Apart.

Will do. I'll send an email called "UCAWA - Intruders CTD INI files - D2D - Cruiser". You can expect me to send them about 1700 hours GMT. Thanks.

Not calling you stupid SC, people talk past each other sometimes thats all, especially when it concerns software. Ok then, I give up. If there isn't anyone who will comment on this, who actually have the UCAWA 1.00.11 installed, and have experienced the same PERSCAN problem (or have tried my saved game), then I guess there's not much more I can do about it. Aren't there really anybody who has tried my save game and - like SC - isn't able to reproduce? I'm not posting here because I expect SC to help me, it's just as much you other guys - Who has BTW been very kind to help me before... thx. (and no, I'm not talking about the old and already fixed problem concerning intruders being transported).

Ok, just tried D2D with /w2 and /d5 /w2. CTD on both tests. But still, the debug exe for Starforce hasn't produced a single crash on my machine. And at the same time you've never been able to produce 1 single CTD? And you do just like me: Get some intruders and then watch them until they're dead in PERSCAN? If I hadn't heard a number of other players reporting the same, I would believe it was my machine..... [EDIT] Ok just received your PM. Will try now. Just remember that I tried in my previous test with a plain Starforce build. It crashed just as much as the D2D (hmmm, not really a plain Starforce, as I remember you sent me files to modify the D2D into a Starforce version).

Ok, only debug build. I ran some more tests with /d5 /w2 and bottom line is, that I've not had one single crash with the debug build, using my previously mentioned saved game, running in either /d5 /w1, /d5 /w2, just /d5, and with no parameters at all. It's rock stable.

quote: I don't understand. You said that you can't get it to crash, but above you listed that you got a total of three crashes. By "Starforce / full screen | 2 crashes / 2 runs" I meant the original exe file, not your debug build. The debug build test runs is the ones with "debug exe". So what I meant was, that in test-runs with the debug exe, I got no crashes, but apart from that my Starforce version crashes just as regularily as the D2D version. But what ever I do, I cannot get the debug build to crash. I tried all combinations with and without /w1 and /d5. quote: What exactly happens when it crashes? Don't you get a message from Windows? When the game CTD's I get a message of the kind: AppName: ucawa.exe AppVer: 0.0.0.0 ModName: ucawa.exe ModVer: 0.0.0.0 Offset: 0006006a And a lot of other windows-stuff about kernel32.dll. I've attached the windows generated txt file (http://cruiser.person.dk/intruders_ctd_details.txt) in one of my first posts in this thread. quote: And did you say that when run in a window it doesn't crash at all? Did you try this with /w1 as well as /w2? It also crashes at /w1 mode. This is from my post above: * Starforce / w1 mode | 1 crashes / 1 run Sorry for my self-invented notation, but this mean: Starforce version (not the debug exe), /w1 mode, made total of 1 run and got a total of 1 crash. I have not tried with /w2. Good idea. I will do that.

BTW, I also reinstalled my D2D version, ran the updater, started a new game, got intruders onboard, saved, resumed, watched PERSCAN, crashed.

Ok, at fist I should find out that the debug exe you sent me only worked in my Starforce version, you gave me during testing the PTA problem. But then, weird, I can't get the debug exe you sent me to crash. Here are my test results so far: * Starforce / full screen | 2 crashes / 2 runs * Starforce / w1 mode | 1 crashes / 1 run * Starforce / debug exe / w1 mode | 0 crashes / 5 runs * Starforce / debug exe / full screen | 0 crashes / 3 runs I don't know what's special about this exe file, but it is affecting the stability of my system. Bottom line, I can't get this debug build to crash, so I can't report any errors. Sorry.

Dammit, typo'. Sorry about that. I mean PERSCAN of course.

Please let me know, if you need anything else than the text file i supplied above.

quote: Apparently, in space, where there is no friction and no air and whatnot, a large ship turns like a mule. Who knew? Heh, he must be the first that actually thinks that the large ships should handle more lightly? Momentum obviously doesn't play a big role in his opinion. quote: A professional aircraft controller would probably have a hard time monitoring all the displays that you need to keep your eye on and understand in order to play this game well. I hope not, else I won't set a foot in a plane again quote: Perhaps 3000 AD Inc. should re-name their company ÔÇ£Missing the Point Inc.ÔÇØ Hmm, can you hire this guy, he's really funny ...hmm. quote: This is technically a very good game if you are a technically minded person who is prepared to put some work into your gaming Amen! I thought this was the basic idea with a simulation.

Good point. Lets me re-phrase At first i thought that I could only reproduce the CTD if I accessed the perscan at the exact moment the game was in a certain state. I was not able to reproduce by just watching PERSCAN. But then a seems that I was only "lucky" in my tests where I just let the display stay in PERSCAN. The CTD also occurs if you immediately switch to tacops and just watch your marines fight back the intruders. But not every time. I can't see any similarities in the cases where I get CTD. I have tried to get it with both 5 intruders left, and also when only 1 was left in shuttle 4.

And BTW, I was wrong in my procedure for reproducing this. Apparently it occurs even if you just view the intruders in PERSCAN and not when you access PERSCAN. And even with my saved game, it occurs far from every time.