boo_n_817

I'm having the same issue. Seems like it went away after the last update.

First off, if you're starting a mission, you must be parked to change your skin. Simple ask the "Chief" to Re-Arm and one of the drop down menus will be all the liveries available. Pick it and hit okay. Now, it can get more complicated than that but if that doesn't work, let me know and we'll find a solution. Good luck! :thumbup:

iFoxRomeo - sorry for the delay in responding but a big THANK YOU for your reply. This is perfect!

Is it possible to embed a sound file so it plays when you tune to a certain radio channel? This is strictly for immersion purposes. Thanks!

FYI, I noticed this thread is under the Persian Gulf Map versus the Nevada Map.

Deleted the Nevada map and reinstalled it. That seemed to have fixed the problem. Thank you for your help!!

GPU updated driver did not resolve the issue. Could the map have a bug? Would you recommend reinstalling the map?

Cleanup and Repair did not resolve the problem. I'm running DCS OpenBeta. I've attached the latest log file. Basis System Specs: OS Name Microsoft Windows 10 Home Version 10.0.18362 Build 18362 System Type x64-based PC Processor Intel® Core i7-8700K CPU @ 3.70GHz, 3696 Mhz, 6 Core(s), 12 Logical Processor(s) Total Physical Memory 63.9 GB Graphics Card: NVIDIA GeForce GTX 1080 Ti Is it possible to uninstall and reinstall just the Nevada map? Thank you sir! dcs.log-20190808-141132.zip

There are 2 clients and 12 AI planes, nothing else

I'm creating a mission in the Nevada map and DCS has crashed numerous times in the process. It only happens when I'm moving the map around or zooming in & out. No other map has this issue. Any news or fixes for this? Thank you!

This might be old news to some of you but thought I'd post this in case. If you're trying to make your AWACS or tankers Invisible & Immortal in the Advanced Waypoint Actions AND you have them in Orbit mode, you must list the Orbit command AFTER both the Invisible & Immortal commands or they will be vulnerable, or at least visible. Hope this helps.

Thanks guys. I think ED needs to create a condition in the Triggers for friendly kills. The game does recognize it but there's no way to program an Action in the mission. That's what I'm looking for.

Is there any way to build in a "punishment" for a friendly kill? I don't see anything in the Trigger options. I know TTI has this capability so if it has to be done by LUA script, please post an example. Thank you!

Thanks fellas! The disclaimer is a good idea, I'll certainly make sure they know.

I have a few missions I'd like to post but before I do, I wanted to ask about any guidelines. These are tough & thorough missions but there's some fun built in as well via voice messages, namely some adult language. I really want these missions out there but just want to make sure I'm not violating some DCS protocol nor offend someone. What are the guidelines?

I'm constantly getting the same error (SP & MP), usually after I've completed 5ish or more missions. It occurs when I hit 'OKAY' after a successful mission. I have never finished a campaign because of this. Hopefully the developer is reading this but PLEASE, somebody come up with a solution!

Is there an updated user guide out there or one in the plans?

There are no layers in a .dds file, it's all be flattened. I even tried to create a separate layer and that didn't work. All I've had to do in the past is simply change the color of the #'s on the background and it works, as it does for the Left side #'s in this livery. A very weird deal.

Does anyone know why only the right side BORT #'s are not showing up? There's just a faint outline of the #'s. I've created a ton of different skins and have never seen this issue. The only change I made was to make them white, which I have done many times successfully. And the left side #'s look fine! It's a head scratcher for sure! :helpsmilie:

I'm getting a similar error except mine is on line 1459. It has to be an issue with OB version because there are no issues when I run the same mission in the stable (release) version.

Yes sir, the names are all correct. I've reloaded the lua script and the sound files just to be sure. It was working on this mission just a few days and then, poof! :mad:

Script Error message I have created several missions using your LSO script. I was editing one of them (non LSO related) and received this script error message (attached) when I started it, which renders the LSO script inop. Any idea what's causing it and how to fix it? It's an awesome script btw, donation via PayPal on its way. Thank you!

I got it to work, thank you!! I had to change the Type to 'Switched Conditions' but your suggestion worked great!

Thank you for the response, that makes sense to me. Just so I understand for future missions, if you randomly generate a unit and set a flag, the flag will only be true if the unit spawns?

At the end of my mission, after the last bad guy is killed, I have 2 bombers that are randomly generated, so it's 50/50 if they will spawn. I want to generate a 'Sound to Group' to signify that all bad guys are dead but I'm not sure how to recognize whether the bombers will be present or not. Any ideas?? Thanks everyone! P.S. I'm not a coder