Just so everybody's on the same page, that's what I was doing. It's just that the SPAD suicide bug wouldn't hit right away, so I'd be testing a single mod out for several flights, testing a single setting change one at a time, etc. This wasn't a case of dumping a bunch of stuff in all at once - I was spending two or three hours one night testing two mods one at a time and everything would be fine. Then, a day or two later, suddenly the same exact configuration would stop being okay.

So it's a matter of testing each individual mod like you say, but specifically testing each individual mod by itself for a couple days minimum before moving on to test the next mod individually for a couple days, and so on.

Regarding the read me's, I've been reading those, but there were some areas where the user has to be able to read between the lines to infer the implications.

E.g. I used to work in a music shop, and saying "this bass amp isn't a guitar amp" or "this fuzz pedal isn't a bass effect pedal" wouldn't mean anything, because you could still use them just fine. But it was very important to know that not only is a guitar amp not a bass amp, but specifically don't plug the bass into the guitar amp! These are very different ideas.

So when I first read the multi-mod read-me, "This is not a JSGME mod" didn't mean anything to me - it read like it was just a statement of fact. Something like "Don't use this in JSGME" would have conveyed that point to somebody w/my low level of knowledge - just like it's important to know not to plug the bass into the guitar amp.

But there's a certain point at which those sorts of miscommunications/misinterpretations are inevitable. As silly as it might sound, interpreting the language of the read-me's is a skill that takes some time to develop. Live & learn!

AlbrechtKaseltzer;

The default path is (C:\OBDSoftware\WOFF\OBDWW1 Over Flanders Fields), not ((C:\OBDSoftware\OBDWW1 Over Flanders Fields).

I suspect that your registry shows the correct default path, but the actual location you specified doesn't match the registry entry.

Check it and let me know.

Best Regards

That sounds we have to write manuals like: "Do not put the cat in the microwave oven!"?
I am sorry, but you must also consider that for many modders is not English their native language.

I checked again and that's the file path I've got. (I'd done a direct copy-and-paste). It sounds like that's not what the path is supposed to be, but all I know is that's the path that the install program set up without any human interference during the installation process.

Yeah, it can sound a bit silly. In my mind, it's like how microwave ovens often come with manuals specifying not to insert metal objects inside.

In general life, there's many things that aren't expressly designed to go together but that work just fine together anyway. However, much like microwaves and aluminum foil, this was clearly not one of those cases!


Oh for sure. I get that English isn't a first language for a lot of people, and English can have many quirks that can throw people off - and all of that is also very true for any sort of programming/coding/troubleshooting/etc where some idiot like me gets thrown off in unexpected ways.

I get the impression this is getting taken somewhat personally, and I just wanted to say that there wasn't any finger-pointing intended. The goal was to walk through my thought process & learning process, how I got it wrong despite reading the read-me's. I wanted to show where my effort & intentions were present, and where my knowledge was lacking - because I find that it helps other people to help me if I'm honest about what my areas of ignorance are and what I'm misunderstanding. I also wanted to be able to show that I'm at least making a good faith effort and not just wasting everybody's time.

So the point isn't to say "Oh this is so-and-so's fault!" I'd rather focus on the fact that now we know what happens if the multi mod gets placed in JSGME - and it can be valuable to know this for future trouble-shooting & diagnostics: "Oh, if there's sudden issues with the flight model, check to make sure you're using the multi mod correctly!"

OK, no problem I did not take it personally. It was just my attempt to lighten the tense a bit.



I am not sure, if that ( i.e. MultiMod enabled by JSGME) can even have described impact on flight models. MultiMod does not modify any respective flight models, as far as I am aware. Just simulation.xml and few other xml files.

Hallo AlbrechtK,

does the "User Files Backup Utility" work now? If not, I can't help from the distance, only with the first manual way, @VonS has mentioned Side one.

Why is a test with one mod for 2-3 days on your system too long (WOFF is great, also without mods!)? Okay, if so, then I can only recommend the first variant, I have mentioned on side 1:
After an uninstallation of WOFF via "WOFF ToolBox" check the registry with CCleaner and restart your system,
Check which mods have an influence on the DM/FM of your SPAD (the fire-rating, the gun-jamming, the own-bullet-hits, etc?). And these mods don't use and see the results.
Basically activate one jsgme-mod after an other, not all at once.

A third idea is, that you make a screenshot of your WOFF-installation with subfolders, a screenshot of your jsgme-modlist (and maybe the installation-path of other mods outside jsgme if they are not visible in the screenshots).


Sorry, I can't say more at this point of investigation. I would only repeat, what I have written so far. Maybe an other member with more knowledge has further tipps.


Greetings and success!

No change. I'll just go manual and hope for the best.


Maybe I miscommunicated - basically what I was saying is that you and I are on the same page, that I was following the process you'd outlined already, it's just that an hour or two of testing one single mod is insufficient so longer testing is necessary. That just caught me by surprise; generally any time I've delved into game-modding, bugs and errors would show up right away, whereas in this case the single mod will be fine for an hour or two but then that same configuration will stop being fine a day later without any discernible changes in between.

So it's not that 2-3 days is too long, but that 2-3 days is necessary even if that's not necessarily obvious.



Amen to that! The one thing I'm realizing is that modding WOFF is a completely different animal than anything else I've fiddled around with, and maybe in my case it's better to just leave the game as-is.

Ah okay, gotcha! Yeah, I hadn't experienced any tenseness. It's all good!


I don't know how or why it happens - all I know is that on my system, when I implement that one mod that one way, those are the results I get, and I don't get those results any other way. That's not on the mod or the mod developer - that's just an unintended consequence of misuse/user errors. Given that this was misuse/user error, by definition that opens the door to all sorts of unpredictable & idiosyncratic consequences that can be particular to a specific device.

Albrecht

As I stated before, the User Files Backup program looks at the registry entry and gets the path to WOFF from there.

If you know how to look into your registry, go there and check the path and compare it to the path on your hard drive to see if they are the same.

If you don't know how to check your registry, send me a PM and I can help you.


The attached picture shows where the default WOFF path is stored in your Registry: Click Here

Best regards