Blooze

Can you explain what you mean by go-to "turn it off and back on again" solution for mission compatibility?

Try

Go to your Saved games/DCS/config folder and delete the view folder. Start a SP mission. A new view folder will be created and your views will go back to default.

Click for a good tutorial for the A10C

Click HERE for a recent example. In THIS mission there are 2 AI F117s that bomb a bridge early in the mission. In SP it works fine, in MP they fly towards the target, make a U-Turn and fly away.

I have experienced many times triggers not working in MP that work fine in SP when I am the only one on the MP server. I don't know enough about the ME to troubleshoot a mission to make any corrections. I appreciate your info but what I was hoping to learn is, what is it about loading a mission to the MP server that causes missions to behave differently from SP mode? I really don't think anyone knows and although we blame the DCS World updates for breaking MP missions I believe the problem lies within the master server. I sure would like to see someone from ED comment on this issue. Thanks for your input.

Does anyone know why a MP mission can run as intended in SP mode but the same mission malfunctions when run on the MP server? What is it about uploading the mission to the master server that causes the missions to fail?

Click and for some video tutorials that may help you get started.

Click HERE for a mod that increases visibility of ground objects but I don't know if it will help with increasing the visibility of aircraft. Either way it's a cool mod to have and worth a try.

Question, when I run a MP mission called Talon's Reach on the MP server I get the following error message. SLMOD ERROR: invalid variable type in slmod.units_firing_net Can someone tell me what this indicates and if there is a way to resolve this issue?

Click my sig for something that may be of interest.

Update: Having a good looking sister would be a real plus.

You're welcome.

I host MP missions daily at 8PM CST so click my sig for details and feel free to log in to our Teamspeak channel if you like. It's just a small casual group that flies coop missions designed for 4 to 8 pilots. No pressure, just good times.

One can only hope.

Click my sig and read the "About" page for something that may be of interest if your time zone fits.

There is a simple step that sometimes can solve these problems. Try renaming your saved games/ DCS folder to DCS1. Then fly any SP mission so it will create a new one. Then try to enter a passworded mission to test. If it doesn't work and you want to go back to where you started, just delete the newly created Saved games DCS folder and rename the original back to DCS.

What troubles me is that EDGE is a graphics engine and it has been said that the ME will be the same and these problems are likely to carry over with the transition.

Some servers have integrity checks enabled so some installed mods may be causing this.

Photoshop CS2

it's always best to let people know what time zone you are in.

Does this happen after you have typed in the correct password?

When you get ready for some multiplayer action click on my sig for something that may be of interest.

For those that understand the technology of the overall MP master server process, is there something inherent within the ED master server that has the potential to have an erratic affect on MP mission triggers? I have seen numerous times where missions that run perfectly when run in SP mode, malfunction when run on the MP server. I have been one to jump to conclusions by blaming the updates for these issues but am wondering if it's just the nature of the beast regarding the master server.

I am not a wizard with the ME but in an effort to try to figure out why a MP mission was malfunctioning I began looking at a few things in the ME. The mission is Talon's Reach by Joyride and had been working in the past but not recently. There are 2 F-117s that are supposed to bomb a bridge early in the mission but lately they have just flown in circles and then left the AO. This led to a disruption of other triggers as well. I noticed that in the trigger list description they were supposed to be at an altitude of 21,000 feet but when I looked at the aircraft's waypoints the altitude was set at 30,000. On a hunch I changed the waypoint altitude for both planes to 21,000 feet so it matched the trigger description and tested the mission. Both F-117s proceeded to bomb the bridges as intended after the change. My question is this, did the altitude in the waypoint section change from 21,000 to 30,000 as the result of one of the updates and if so would this explain problems with other missions and their AI aircraft? I'll leave that for the experts to decide but I felt compelled to at least post my findings Update: Mission worked fine in SP but not in MP and I have no clue as to why that would make a difference.