Blooze

I Have the latest version of the OB installed but would like to revert back to the previous version. The current ID number is 1.5.1.46722. Does anyone have the ID number for the version just one step back? I think it would be the version after hotfix 2.

I don't think it's working yet but has been reported HERE

Here's one I'm working on....not quite so weathered.

I am not one to give advice about the ME but after having numerous experiences like yours I have come to the conclusion that if I save a mission after editing, close DCS World and return to desktop, then re-open DCS World BEFORE running the mission, I get more reliable results. It's my theory that there is something about the SAVE function that is not working properly. Take it for what it's worth.

Here is an example of a weathered A-10C skin created by Ryan Barnes and available on the LockOn files website. You may want to check there to see what they have.

If you look at the weather for a mission in the ME you will see fog unchecked with a setting locked in. Check fog then uncheck it to clear it.

I stand corrected then and apologize for sounding an unnecessary alarm. I sure hope this gets fixed soon. I stay so confused. :cry:

Do you have an extreme setting after the latest patch?

EXTREME? There shouldn't be an extreme setting nor the option to choose 25000 as tree distance. I believe this is a residue left over from the improved distance mod. I have seen this happen before with 1.2. In my experience this mod cannot be completely removed with JSGME and has the potential to cause issues that can only be corrected with a new install. Please do not take this as advice but rather just a theory from my past experience.

I saw the same thing and thought it must be on my box so I dumped the whole damn things and am downloading a completely new install. I sure will be disappointed if this was a bug that came with the latest patch.:mad:

I am using Photoshop but I found a great free product called Paint.NET that has many of the same features.

'

Eureka!!! I ran a test and everything was working fine. I added all my voice overs back to it and everything works great. One of my favorite missions is running again and I appreciate ya'lls help more than you know. Salute!:thumbup:

That works great. Thank you very much indeed!:thumbup:

Thanks guys, I just finished a 2 hour MP mission so I'll run a test a bit later and report back ASAP.

Thanks but that's way over my head. I should have said easy solution for dummies.

I can't seem to get this working in 1.5. Stonehouse would it be possible for you to create a working JSGME folder for this and provide as attachment or a link to download?

Eureka! That's it and thanks for your help.

There once was a mod listed in the forum that allowed the placement of fire on the map using the mission editor. Does anyone else remember it and know how to find it? I have tried searching but no joy. Thanks

Can anyone tell me what this error means and if there is an easy solution. MP mission and error message attached. Operation_Saturn_V2.1 WC12v7.miz error.txt

Try LFT CTL+F11 for a free camera view.

With the A-10C I have my F1 cockpit view set the way I like it and my Track IR set the way I like it and never have to change it so it's hard for me to understand why all of the changes you mentioned are needed. I guess each one has to find their own solutions.

If you use Track IR it's quite easy to get in a pit with Track IR enabled, move your body to acquire the position you want, pause Track IR and hit RHT ALT+NUM0 to save. Un-pause Track IR and it should look like you want and this will become your new default F1 cockpit view. Be sure to enable USER SNAP VIEW SAVING in the DCS Options/MISC page first. Whenever you want to return to default views for whatever reason just go to your saved games/dcs world/config folder and delete the VIEW folder and start over.

Although I can't find the thread, for some changing the default animated clouds GUI theme to any other module theme has solved this problem.

I only have the 1.5 OB installed and plan on changing to the full release when it is out of beta. I see no need to have 2 installations when it is so easy to simply change from one to the other. Click HERE for instructions.