Supreme Cmdr

Boll Passing On Metal Gear Solid?

We are in the process of making some revisions to the fp portion of the game in order to make it feel a bit better to those who actually use it. During this process, we found a critical bug in the new audio system and which the developers of the FMOD engine have now fixed. This fix is in this interim version. Download the ucAWA_1.00.12.02.rar from the game registration page and extract into your game folder, overwriting all files when prompted. To see the revisions, check the VCF When the final patch is released, you can just use the game Updater to bring it up to the final patch version. This interim patch is for the Starforce version only.

Everyone is a psychologist these days

So much for that

Please vote!! http://www.fireflyseason2.com/BrowncoatProfile.asp

quote: Originally posted by Cruiser: 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). You will only get a log file if you add /d? (where ? = 1 to 5) to the shortcut. quote: When testing the intruders issue, I only get CTDs 80% of the time. Therefore the save before testing.Thats not good enough. I have had that same game running continuously in both the D2D and SF version with no such crashes. If you want to reprodue it reliably, do NOT introduce - yet another - variable to the equation i.e. the use of a saved game. Also, we need to know in what version this started happening. So before you start your next batch of tests, I suggest that you run the original D2D version of the game (which I think is 1.00.10) WITHOUT doing ANY patch upgrades. If you still get the crashes in that version, THEN you can upgrade to 1.00.11 and then on to the 1.00.12.01 which I sent you earlier today. You need to also be running in window using /w1 and with debug logging using /d2 also. This way, if/when it crashes, at least something will be displayed on screen or logged to the .log files.

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. 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. You are continuing to confuse this issue.

I sent you a reply. It looks like you are mixing D2D and SF files. You are also using the same saved game to run these tests, when you should have used a new one. So, please follow the instructions in the email I just sent and report back. Yes, if you run a Roam scenario with AG off, no intruders will be generated. My thought process is that if this is not an intruder problem, then it could be something else. One way to clarify that, is to remove the intruders from the equation. Not using the same saved game (which has the intruders) also removes the issue of it being a corrupted saved game. Using the SF version - and it too crashing - eliminates this issue as being a problem in the D2D version (which only differs from the SF version in terms of copy protection).

http://www.eff.org/deeplinks/archives/004344.php

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? Well, I'm stumped. I can't reproduce it, so I can't fix it. 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. ps: Did you get my email? If so, please send me the requested file.

quote: Originally posted by Cruiser: I just re-downloaded the file, and re-applied it to my Starforce folder. Still CTDs. Which CTD are you getting now? Because you told me on PM that you couldn't even run the game with the latest update I sent you.

There's something called Tacops. You might want to use it.

I got the files and will check them out later. Did you read my last PM from yesterday and re-download the file again to check it out?

I have discovered a bug in the FMOD engine related to playback of some sound files. e.g. when playing the EFM, firing the XN32 produces no sounds. And when you quit, the game will terminate (crash with an exception) instead of returning to the main menu. This seems to affect most fp weapon sounds. I am now working with them on a fix which I will immediately roll into a new patch asap.

Thats not the name of the game and the spam filter will delete the email.

Cruiser, can you please zip up these files and send to me via email please. Don't forget that if you don't have the name of the game in the email subject, my spam filter will reject it. All the INI files in the DATA sub-folder All the INI files in the root of the game folder The files above are for your D2D installation btw, not the Starforce version.

Tom Chick is a frigging idiot. But the rest of us already knew that.

I think we're having a language problem here. I never said that you were calling me stupid. As I've said before, I CANNOT fix what I CANNOT reproduce. And since - thus far - nobody has reproduced it on their own or with your saved game, what does that tell you? Even the debug build I sent you, does not exhibit the problem.

quote: Originally posted by Cruiser: 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? Yes. I'm not stupid. If it was a bug that could be reproduced do you think this thread would still be going on? At this point, I don't think it has anything to do with the game. quote: If I hadn't heard a number of other players reporting the same, I would believe it was my machine.....You are reading about something completely different. And the other person who posted here, didn't have UCAWA. So I deleted their post. There was an issue wrt intruders which was fixed in both UC and UCAWA. Read the VCF and stop confusing the issue. quote: 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). For the LAST time, I'm going to ask you to stop refering to builds that I have NO interest in. That Starforce build you are talking about is the same as the D2D build, except for the protection used. So yes, if one crashes, then the other will as well. And neither is a debug build.

I was expecting you to run the non-debug D2D build with the /W2 option.

After Subpoenas, Internet Searches Give Some Pause

LOL

http://vgstrategies.about.com/od/xbox360fa...360HDTVBars.htm

quote: Originally posted by Cruiser: 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". Try not to confuse the issue please. I'm not interested in any other version tests, except the versions I specifically ask you to test with. In this case, the Starforce debug build.

If you can't beat 'em, buy them.