Quote:
Originally Posted by Rockin Robbins
A perfect example was Ducimus' struggle with environmental mods. Not happy with stock environment, he experimented with every environmental mod out there. But those environmental mods influenced the way sub sensors and enemy AI interplayed--badly! Finally, he nerfed one of the major environmental mods and tweaked it enough that he was happy with the balance between sub sensors and enemy AI.
But the first thing people tend to do, to this day, is say "the TMO environment sucks. I don't like the sky color. The waves are wrong and the wrong color. Yada yada." And they have a point. But what you see is not what the game mechanism sees. There is a reason TMO's environment looks the way it does and that is the result of hundreds of hours of testing every combination of environmental mods out there.
|
At the moment I have installed TMO and on top Improved Stock Environment v2 (because v3 does not work and gives lots of fog) + the 2 submods for color and clouds. It LOOKS very beautiful and to be honest I dislike TMO's default look, too.
Now when I look into the ISE folder, I see that it alters shaders for clouds and filters, EnvColors*.dat and SkyColors*.dat, and the scene.dat.
I suspect that scene.dat is very central also for TMO's changes, isn't it? So if I use ISE, do I contradict TMO's settings for sensors and AI (or any other important settings balanced in TMO)? Or are these imortant gameplays aspects part of other files (which then would not be affected by ISE)?
Edit: Answer to myself: Read the whole ISE release thread, and it seems ISE 3 is compatible with TMO (because it uses TMO's scene.dat as starting point), and his colors submod, too, but not the clouds & wakes submod, because that submod uses the default scene.dat as starting point. What a pity
And to make it worse, even though ISE 3 is said to be compatible in the TMO version, it has fog issues. So... I guess I can only use the color submod of ISE, but nothing more.