[WIP] FX Update

[Fifi]

Pfff...it's not my AST finally, i got it again without

Am i alone with this issue of FX 0.22?

Didn't try it in career, but in single missions it's very obvious...
Well, going back with previous 0.21 in the waiting of answer

[volodya61]

Originally Posted by Fifi

..Am i alone with this issue of FX 0.22?..

I guess you're the only who still testing the game/mods

[gap]

Originally Posted by Fifi

Pfff...it's not my AST finally, i got it again without

Am i alone with this issue of FX 0.22?

Didn't try it in career, but in single missions it's very obvious...
Well, going back with previous 0.21 in the waiting of answer

- What ships have you tested so far which are affected by the problem? There is a chance (though remote) that by accident I added some unwanted zones to them.

- Have you tried comparing the two zones.cfg files in winmerge? there shouldn't be any other difference between the two files than the new zone added by me to v. 0.22 of the cfg file, but I could have inadvertently changed the settings of some other zone.

- Is this happening when ships are torpedoed. If so, are you using one of the 4 add-on torpedo mods which were added by TDW to the latest version of FXU?

- Finally: have you used before the reworked torpedo effects while it was available as a patch? Again, as far as I can remember we didn't touch fire explosions (just water explosion), but some other particle generator might have been altered by mistake.

[volodya61]

Originally Posted by gap

- Again, as far as I can remember we didn't touch fire explosions (just water explosion), but some other particle generator might have been altered by mistake.

You're right, we didn't touch them.. because these settings are located in entirely different files..

[gap]

Originally Posted by volodya61

You're right, we didn't touch them.. because these settings are located in entirely different files..

Yes, exactly, but you never know

[gap]

An easy way to test what is wrong with v 0.22:

- enable v 0.21 => test if everything is Okay
- enable the new Zones.cfg on top of v 0.21 => test again
- enable the new ship zon files on top of the two previous mods => test again
- enable the patch version of the reworked torp explosion FX => test again
- enable any of the torp add-on's, if you used it during your previous tests.

Hopefully, one of the above test will unvail the mistery

[Fifi]

Originally Posted by gap

An easy way to test what is wrong with v 0.22:

- enable v 0.21 => test if everything is Okay
- enable the new Zones.cfg on top of v 0.21 => test again
- enable the new ship zon files on top of the two previous mods => test again
- enable the patch version of the reworked torp explosion FX => test again
- enable any of the torp add-on's, if you used it during your previous tests.

Hopefully, one of the above test will unvail the mistery

Yeah, but right now enabling 0.21 as it was before give me CTDs in single mission
I rolled back exactly as before though!!
Driving me a bit mad actually. I keep trying...

[gap]

Originally Posted by Fifi

Yeah, but right now enabling 0.21 as it was before give me CTDs in single mission

Volodya is right then: definitely your PC is possessed.
You don't need the help of fellow modders, but a team of exorcists

[Fifi]

More seriously, half of my mods deactivated, back with 0.21, i still have the problem...
So it's not coming from FX 0.22 obviously
Last to investigate is patcher now...with latest radio patches that i activated.
Trying without...

[Fifi]

Ok, problem is gone...i deactivated latest radio patches, and everything is fine again with 0.21

So those 2 radio patches are not working (on my rig at least) even giving CTD sometimes...