NoJoy

I just noticed that the GBU-31 Penetrator has different effects on targets when dropped from different planes. Dropping 4 GBUs on the Command Center from the Hornet they can't kill it while being dropped from the F-15 they kill the Command Center each time. I used both the USN and the USAF versions on the Hornet. Not sure if it's a weapons bug or a plane bug or a bug anyways but I find it strange; well knowing that the Command Center is quite hard to level. Maybe someone has insights - I can upload trks if so wished - should it be a bug... Thanks out

Well, GS doesn't make too much sense as it takes wind speed into account. I'd set the mach number but the advanced waypoint task only allows knots. Here's what I found in the Mission Editor Wiki: Optional Parameters: All other variables are optional. ... speed: Speed in meters per second the AI will orbit at. If no speed is defined then the AI will orbit at 1.5 their stall speed. ... I think the wiki is outdated here as the speed in the speed box is set in knots. Anyways when I reduce the fuel to 50% and remove the drop tanks AI maintains the orbit altitude but with oscillating bank angle between 40% - 60%. So after all I think it's mainly due to the high bank angle. I will set a race-tack holding in my missions because an Eagle with 50% fuel doesn't have much time on station left. Oh and I think the speed in the waypoint options is TAS. When I set it to 440 it keeps a solid 260 IAS.

Ok the weight is too much. But still, 70% fuel has the same effect, speed will bleed off. Isn't the speed in the advanced waypoint tab IAS? Which should then be roughly 420ish TAS. Anyways, the bank angle in the orbit is too much, AI tries to maintain ~45°. I will do some more testing... Hear ya, thanks so far

As title says the Eagle can't hold speed/altitude for an orbit at 32'000 ft. It bleeds off speed quickly. If I did something wrong just give me a knock knock...f-15c_cant_hold_orbit_32k.trk f-15c_cant_hold_orbit_32K.miz

I had this bug myself for quite a while, the problem was colliding statics on the deck. So check carefully if static planes or tractors or anything else is slightly touching or blocking or colliding with each other. The most easy way would be to delete any statics on the boat and save the mission. Did the trick for me - with several missions. Cheers

Thanks Champ! Really nice and no hurry. I'll try myself to get it working too. Wish you a very nice Xmas!

@Glloq sorry mate I just missed your answer though I hadn't much time for DCS anyways. So here's the mission - I do have some triggers and sounds in it but I guess that's not a problem. Thanks a bunch for having a look, really really appreciated!!!! 2_2_Persian Gulf Sample Mission_aaa_test.miz

hm, I downloaded a new moose.lua and the error pop-ups are gone but still no fireworks. I'll setup a mission from the scratch, let's see what happens then... Thanks so far

Hey guys, I just startet to build more complex missions with triggers but never did a script. The script you did, to have that 'light-show' is just was I was looking for long time and tried myself quite some times - with no joy. So I tried to just set the triggers in a mission I built myself and inserted the lua files I found from Mist and Moose. But as soon as I start the mission i get these errors popping up: And here the trigger page from the ME: Maybe it's conflicting with a trigger I have in the mission or maybe I have the wrong .lua files stored in the wrong place but I just can't get it to work. I'd really aprreciate any help here... Thanks @Glloq for your cool script anyways - VERY COOL!!

I'd really appreciate a 'Return to base' command for the CA UI when in F10 map. When AI Flights are done with their mission or simply go nuts doing stuff not commanded it would be nice to just send them home before crashing or running out of fuel. Sure this would be a fall back solution for bad edited missions but could help in many otherways. Thanks. Out.

Thanks for the update ED! My frames are back up to where it were before - maybe even little better. With my older rig I'm back at 60 - 80ish from 10 - 15 with the august update. < I7 6700K@4500, 32GB@3200, NVME SSD, GTX1080>

I do have huge performance drops but it only affects Syria and the Persian Gulf map. Caucasus and NTTR runs smooth as they're used to. Since the last update DCS 2.9.7.59263 Syria & the Gulf I have 5 - 15 FPS where I did have some 60 - 70. Seems like the Chinook and Apache have at least something to do with. When I delete them from the missions from these maps frames recover to 15 to 30ish. Though - unflyable frames. I know trk files are a must and I wouldn't mind to upload some but right now I don't have time as there would be 2 for each map and with and without the helos to see the difference. Maybe some later... sorry.

Hey guys, quick question: After disembarking infantry from the transport e.g. CH-47, who do I get the 'guys on the ground' follow a route / waypoints? In the ME i only can give them waypoints from the spawn point but they won't follow the further route after disembarking. Thanks for insights and hints!

Heads up! Reported in another thread.

Hm, there is quite sure the need for some documentation and how to's. But really on my side as I stick to the 'standard fuses' like the kind we already had I don't have trouble to blow things off. I stick to the M904E Nose & M905 Tail fuse or the FMU-139 which are set from the scratch in the loadout menue. MFUZE N/T for dumb weapons and the EFUZE inst for the smart ones. Hence, there must be some bugs, a proper documentation (which is quite sure in the making by ED) would be helpful to at least sort out if things are broken or if it's just a user error.

I had some crashes even without a crash log. What I did and helped so far was to do a slow repair within the launcher, and delete the fxo and metashaders2 files. Here: C:\Users\user\Saved Games\DCS.openbeta\fxo And here: C:\Users\user\Saved Games\DCS.openbeta\metashaders2

I do confirm this! I do not find the option for the easy comms in the launcher so I'm not sure if this is connected with the launcher itself. Though since the update I do have to uncheck easy comms after each restart. I do have a track if so wished but it only shows that that comms are working in easy mode not that I do have to switch options prior to start. So the bug isn't considered in the mission but within the start of DCS.

On the F10 map there's the coordinates in your preferrd format on the upper left corner. Just click on that and it cycles through the different formats. Long Lat, Long Lat dec, MGRS, etc

It has always been a FPS killer to me. No matter what I set it costs me about 20 - 30% frames. I switch them on when I'm up high in the sky only. In the Hornet it's not hitting as much frames as in the F-15E so it also seems to depend on the module though. I'm on the lower end with my rig also (GTX 1080, I7 7600, 32GB Ram...)

I just had the same in Caucasus, wasn't able to get a lock down to 2 or 3 miles away. Daylight, Mav D. Though, I had a flight at NTTR where the Mavs locked like a charm. Also daylight and Mav D. Sorry not to provide a track as I just stumbeld over this topic. Will investigate and try to send one.

Patch Notes says something about the CVN-74 isn't functional anymore: Free USS Stennis is no longer functional.

EDIT: Everything is fixed and triggers like charm now. Thanks Mate! It really was to de-link the units from zones. Well, I couldn't try it out yet but I've read about a bug preventing triggers when a unit is linked to a zone. I just saw that I had a flight linked to the SEAD-Zone which I've now de-linked. Maybe that did the trick. But as said couldn't test it out yet. But here we go with the screenshot anyways:

It did work, really thanks! One thing left to clarify - I set up a trigger for launching HARMs with similar settings. Those still doesn't trigger, though. I wonder if the HARM doesn't count as "Missile in Zone" but "Bomb in Zone"??

Hey guys, I set up a mission and wanted some sound files triggerd for more immersion - and it turned out I'm not getting it done I want to play ogg files whenever a missile or sam is fired. To keep it simple I chose to just play the sound to coalition and not via the radiomessage action. In short: Trigger Zone set, every Missile fired from blue side or sam fired from red side should trigger the according audio file to blue coalition. I'd be really thankful if anyone could help me out. I've read some topics but none of them seemed to work for me. Please see the screenshots, they should make it obvious what I did wrong or what I maybe just forgot to do to make it work. The screenshots doesn't show the sam trigger.

This! SWOTL did a phantastic job ages ago!