Shahdoh

Should be able to get a bit more by manually controlling the radiators. Just have to watch the temps closely and not let it get TOO hot. Fair bit of drag induced by them on auto.

The mission can also keep you from using your custom view settings. If you are playing online an a server, would have to talk with the mission creator/server host if the would be willing to remove the restriction ( IMHO, no good reason to be there anyways). If Offline, need to open up the .miz file with your zip utility and see if there is a CONFIG folder. If so there will be several files relating to the View. Can remove this whole folder and it will revert to YOUR settings instead of the mission's.

Fly by wire and Auto trim are seperate functions. Fly by wire just means there is no longer control rods or cables directly connected to the input devices the pilot controls. Instead, its just electrical relays that sends signals to a motor that manipulates the control surface. Being fly by wire might make it easier for an auto trim system, but it is not an automatic thing.

Definitely safer there! Suppose the AI is smarter then we have given them credit for!!:music_whistling:

Ah, ok, thanks! The way things were worded, I thought the standard release was upgraded to 2.5.2 for Steam Users. My apologies for passing on bad info.

2.5.0 is the release build and is up to date. 2.5.2 is the Open Beta build intended as a pre-release for testing before it is pushed to the release build. DCS has made it easy to swap from either version, so much so, that many will just update to Open Beta and deal with the new bugs so they can get access to the new things sooner. This link here shows how to do so: https://forums.eagle.ru/showthread.php?t=114030 To make things a bit more confusing, apparently they released the Open Beta build for Steam users, so they got the upgrade to "Release" early.

That is the master list, if its not on there, its either a different version or not being seen. I bring this up because I have witnessed 1st hand a server showing that it was running, but not in the list, so, no clients were connecting. Sometimes they reset the master server, so all servers need to restart to be seen by the master server again.

Well, so far things are working great. Can check it out on the VARS OB server: Virtual Air Racing Series|http://www.VirtualAirRace.com Currently running the Nevada RENO Unlimited mission were I have setup an AI Pace Plane to lead people onto the race course. Info is on Page 2 of the briefing.

Switched to using Moose for the respawning and so far so good. As you said, the double spawning wasnt working (Swore it did first time I logged on, there after that, it was back to every other time I tried, the AI was invisible).

I have had this happen to me last couple times updating OB (erroring out on different files each time and not the same as yours). I just cancelled out, deleted the files manually and reran the updater and it would go through fine. I would then run a repair afterwards just to make sure everything was back in order.

Thanks for the heads up, will keep an eye out for that. Has this bug been reported to ED?

I seem to have found a work around for my situation. When I realized that if you could see it in the mission, the next respawn you could not, and if you could not see it, the next respawn you could, I came up with the following: I do not use late activation, allowing the pace plane to be in the mission from the start. It will run its route, eventually land and sit there. When a client hits the trigger zone, I run the spawn script twice, essentially skipping past the bugged AI to the next one which is visible and runs its route. Needs more testing, but initial results are favorable.

Though many have, moved to OB, it looks like those diehard servers still on 2.5.0 (Release/stable) will need to restart to be seen on the master list again.

This issue crops up right away so it's not an issue of mission length for us. It is 100% repeatable for all clients that have tried it so far. Will try some different things and will definitely relay any successes here if found.

Well, not ALL of the servers are on Open Beta, here is a screen shot taken moments ago of the 2.5.0 stable server list from my South West US location (List sorted by number of players to show the active ones): Yep, the numbers are down, and maybe not the servers you want to fly on, but far from ALL being on Open Beta. Here is the Open Beta Server list taken at the same time: Of all of those servers, 42 of them were running the new Persian Gulf map which of course is only available on OB. There are many reasons for server operators to choose the version they want to run on. Some are personal, others for what best fits their client base they are hosting for. Many of those want the shiny new things first, they'll be on Beta. But you take your risks with Beta, sometimes it comes out great and is better, in which case, is moved to release in about a week or 2. Other times its worse as was the case with 2.5.1 when many steam users on OB got messed up and couldnt update/fly and a few other issues. Those stating that OB is the only way to go are those without the patience to wait for bug fixes to be addressed and moved to Stable release, or can't live without the shiny new toy just released. Again, personal choices. If your favorite server is on a version, and you want to fly on it, then as a client you need to follow suit or find a new favorite. Pretty simple really.... /Salute

So have you been able to come up with a work around? Multiple AI to switch between for the same position? Or despawn it before respawning it?

Information update: The Server sees the respawned AI. The Clients do not unless they reconnect to the server. If there are multiple clients, its the same for all of them. If one of them reconnects, that 1 can see the respawned AI, but the others still can not. If they then respawn the AI again, the situation will reverse. Those that could not see the respawned AI can now see the new one, and those that could now can not. Here is how the trigger is set up, Flag 1 is used for a timer condition on when to allow the respawn to happen again. Again, appreciate any insight on how to resolve the issue, thank you!

Using MIST to respawn an AI aircraft whenever a CLIENT a/c hits a trigger zone. Works beautifully in SP, but in MP, I am getting a weird response. The FIRST time a client hits the trigger area, the AI a/c spawns as expected. Subsequent attempts to spawn SEEM to not do so. There are audio events that go off so I know I hit the spot properly. Now, if I disconnect and reconnect to the server, the AI a/c I could not see before is up and running as expected. Has this been seen before and what is the fix? Thanks for any help. This is on Version: 2.5.0.15365 I do not have access to Open Beta atm.

This too! I get what the OP wants and indeed would be a cool feature, but as usual it is not a simple single thing. There are many layers to the complexity of adding such a feature that needs to be worked out.

With all of the issues of lag and load times. Many mission builders try to trim out things that do not add directly to the mission as much as possible. That means excess aircraft flying around the airport for atmosphere are usually the first to go. Maybe if they can ever get the resources to be used more efficiently, these types of things can be included more than they have been. In the meantime, choices and compromises have to be made.

Well, My user data is on a plater drive with my operating system on my SSD, never a problem. But it is your choice. Just saying you do have a viable option.

Bananimal, you can always move your user data folder to another drive, I have. It works fine and doesn't slow things down that I can tell.

DCS has been constantly working towards getting custom files out of the main install. They created the SAVED GAMES folder to be used for this purpose. Try it instead, you will need to create the liveries folder and the aircraft folder for which you have custom skins for. Example: C:\Users\"USERNAME"\Saved Games\"DCS VERSION NAME"\Liveries\FW-190D9\"Custom Livery folder name" As stated previously, make sure the files are not zipped up. After the FW-190D9 folder should be folders with the name of the skin and in there, the description.lua file along with the *.DDS files. PS: One additional thought. The description.lua file identifies which country the skin is selectable for (At the bottom of the file usually), be sure in the mission editor, that the country for the a/c is selected or you will not see it available.

Yes, was another great event put on by Grinelli. Just would like to remind folks, that even though the tracks look like and are modeled in the same style, VARS is not sponsored by Red Bull, does not use the same rules and in no other way affiliated with Red Bull. This is the VARS World Cup Series, a new phenomenon on its own. /Salute

Server does not HAVE to have the skins to for them to be seen, but it does help under 1 particular circumstance. If both pilots have the skin, BUT pilot B enters the server AFTER Pilot A is already in the A/C with the custom livery. Pilot B will NOT see the skin UNLESS the server has it as well. IF they are on the server at the same time when Pilot A enters the skin, Pilot B will see the skin whether or not the server has it loaded. At least this is how it worked prior to 2.5, have not confirmed that it still works that way.