JSGME (Jonesoft Generic Mod Enabler)

[propbeanie]

Originally Posted by Rockin Robbins

Tomorrow I run FOTRS Ultimate through the Large Address Aware JSGME Gauntlet of DEATH. Several times. I won't be making a video of that one.....

Awww ma-annn.... You know what'll happen if you ~don't~ video it? Something really ~strange~... If you tape it, it'll go smooth.

[fithah4]

Murphy............Murphy?...............is Murphy's Law here?.........

Be interesting if the 7 anomalies of GFO are the same line anomalies listed in FOTRS ULTIMATE are a link to the SH 4 pristeen copy. Maybe like you said adding JSGME after large address aware will correct this issue.

GOOD LUCK with the mad scientist computing!!

There IS an answer out we have yet to stumble over, fall, trip, upon it!!

Fith

[Rockin Robbins]

Originally Posted by fithah4

Murphy............Murphy?...............is Murphy's Law here?.........

Be interesting if the 7 anomalies of GFO are the same line anomalies listed in FOTRS ULTIMATE are a link to the SH 4 pristeen copy. Maybe like you said adding JSGME after large address aware will correct this issue.

GOOD LUCK with the mad scientist computing!!

There IS an answer out we have yet to stumble over, fall, trip, upon it!!

Fith

That was the interesting part. They were NOT the same. They were entirely different files. In FOTRSU it was ConteVerde and German flags. But GFO doesn't change any of that stuff. So those files were unaffected. In order for a file to be affected, JSGME has to replace that particular file with a mod file. Then JSGME must forget to change it back on the uninstall.

So in that respect it wasn't a fair test. I just wanted to find out if there was a lower limit to the size of a mod JSGME would have trouble with. And GFO wasn't small enough to find that limit. I was surprised by that.

Nobody tested more than Webster. He is the only supermodder ever to make an RSRDC mitigation patch to avoid being squashed like a cockroach when it was installed on top of GFO. I would have expected that he would encounter the problem. But if you weren't doing a compare and were just looking at game effects, with GFO the effects would be subtle. After all GFO is designed for an essentially unchanged game experience from stock. Anybody who thinks the stock game is crap needs to play GFO and find out how good it really is. GFO is a blast!

You have to remember than in 2010, when the golden era of SH4 modding died, 64-bit computers and operating systems existed, but nobody used them. 64-bit Windows didn't have drivers for enough hardware and if you were to be bold enough to use it you'd find your printer, monitor, keyboard, mouse, touchpad or any combination of those wouldn't be working. So everybody pretty much stuck with 32-bit Windows.

[CapnScurvy]

Originally Posted by Rockin Robbins

If you are running a 32-bit operating system, anything GFO size or bigger will not work for you. If you are running a 64-bit operating system the fix is in!

Are you telling us that you've tried the 32 bit LAA setup and it doesn't help. Or, are you just guessing?

You do realize that there's an additional "Switch" to throw for a 32 bit OS before LAA works??

You aren't making your procedures clear with your "test" results, if you've tested it at all.

[Rockin Robbins]

32-bit Windows can directly address only 3.2 GB of memory, period. Yes, you can make it seem like more by bank switching, but there's a lot of overhead to a bank switching scheme. The Large Address Aware module was specifically made for 64-bit Windows.

So maybe Large Address Aware could have minimal benefit for a 32-bit machine. Probably not, since it was designed for a 64-bit OS. In a week I'll have a 32-bit virtual machine to test it on, but there's a lot of time in setting that up, a disk drive to buy and install--just doesn't fit my priorities right now.

The question I'm asking later today is "Will Large Address Aware fix our Conte Verde and German Flags problems on my 64-bit machine? We'll address later the questions of whether FOTRSU is appropriate for a 32-bit OS and machine.

[propbeanie]

From my old days (pre-Win2k), if you had 4 gig of ram on your 32-bit OS machine, you could use one of those utilities, but you also had to change settings in the Boot.ini file for Win-2k or XP. You use BCDEdit in Vista, Win7 & 8. Thirty-two bit versions - not 64. I haven't a clue about 10... Both the program ~AND~ the OS have to be "aware", and still, some apps just don't like it and will crash.

Anyway, about the most concise site for that still is the AutoDesk Knowledgebase. I used to use that for video editing back when... Doing that on a machine with 2gig of RAM would be an exercise in futility and crash recovery.

[CapnScurvy]

I think you guys are barking up the wrong tree in thinking huge files make the reason why JSGME causes corruption in changing stock game files. Which moots the idea of testing JSGME with LAA and seeing if it does any better. I think you'll be wasting your time. It's nothing more than modders not following good modding techniques.

I just ran a little test. A 64Kb, JSGME compatible modification that only has two folders changed containing 6 total files. I copied the two FOTRS TLowRes/tex/German.dds-remove and German_m.dds-remove to my mod. I also copied from FOTRS..... TNormal/tex/German.dds-remove and German_m.dds-remove along with the new images it uses of the German flags (they contain the German Swastika)....German.dds and German_m.dds

I compared my present game files through JSGME "Compare Snapshot" to my original game files, all was in order. I ran the game with the test mod only. I viewed the newly changed German flags in the games Museum for the German ships, then exited the game. I deactivated the test mod, then ran the Compare feature again. The results were two files REMOVED. Yep, the two TNormal/tex/German.dds and its partner the German_m.dds were removed from the stock game.

I've had stools bigger than a 64Kb file!! Yet, this stock game corruption occurs with a very small file size.

But here's the interesting thing.....The two TLowRes/tex/German.dds files were intact and back where they belong after the "-remove" modification was used on them! What's the difference???

The difference is the FOTRS modder used replacement images in his mod of the same name that he also used the "-remove" flag for. There are no replacement images in the TLowRes/tex folder....there are in the TNormal/tex folder.

In this case, the modder simply needed to replace the original images with the Swastika images, using the same naming scheme as the stock game, and leave out the "-remove" files from the same folder. JSGME doesn't know what your trying to do if one pair of files make changes to the original, yet another pair ask for you to remove them?!?

Modder error, nothing more.