oldmanflan

Very cool. My Dad and I tend to fly together but he gets overwhelmed by the chaos of the big servers and it's not enjoyable for him. This lead me down the rabbit hole of creating/hosting my own server a while back. I was successful, but the overall setup, including removal of Windows firewall protection and constant re-configuration of the router settings seemingly every time I wanted to host it, got very old, very fast. I'm creating a new training mission for him and I, using the South Atlantic map. I'm going to give your hosting solution a shot and see how it goes. Thank you for creating this!

Yep! I managed to add confusion on top of confusion. @Grimes - I appreciate the help. Thank you. I ended up figuring it out, last night. The issue was definitely with the Autolase lua script. I edited the line that said "KIA!" and changed it to "RTB!". When I initially did this, it didn't seem to work. It was still giving me the "KIA!" message, leading me to go back to the drawing board and start messing with a signal flare condition and then even a "time since flag" condition. But, in the end I discovered that I had to duplicate the autolase script and upload the new one, in order for ME to recognize the change. After doing that, the problem is solved.

I was wrong. None of the above is working and the more I read your post the less sense it makes to me. First trigger deactivates the enemy group, activates a green signal flare, and sets Flag (8) to ON Second trigger deactivates the JTAC if: 1) The signal flare is activated & 2) Flag (8) is FALSE With this configuration the JTAC never deactivates because Flag (8) was is not FALSE. Did you mean that I should have Flag (8) TRUE in the JTAC deactivate trigger? If so, that makes sense and I'm testing it now.

FWIW: I also just discovered that I can edit a line in the autolase lua file to remove the KIA message. So that's another alternative, in case anyone else is curious.

After some tinkering, I got the drone to deactivate using a signal flare condition. Trigger 1) Enemy group deactivates, sends a "Mission Complete" message, sets off a signal flare, and sets Flag 8 to "On" Trigger 2) Friendly drone deactivates and vanishes with no KIA message and a new random mission gets spawned. That said, I still don't understand why turning on a random flag (which isn't associated with the drone) prevents the KIA message from popping up. I tried the same configuration without the "Flag 8: On" variable, as well as having the "Flag 8: False" condition in the Drone deactivate trigger. In both cases, the KIA message pops up. And including the "Flag 8: False" condition in the drone deactivate trigger prevents the drone from deactivating at all. Nonetheless, the configuration I have now works (screenshots attached. But this one's a real head scratcher for me.

Jesus, I don't know why I'm having so much trouble understanding this. I've created a new trigger so that the enemy group deactivation and the drone deactivation are in two separate triggers. The first screenshot is of the enemy group deactivation trigger. It deactivates the enemy group (Waypoint-1) and sets Flag 8 to "On". The second trigger deactivates the drone (WPT-1) and spawns a new random mission from a pool of 40. In this trigger, I added the condition that Flag 8 is "False". However, in testing, when the enemy group deactivates, the drone continues flying and does not deactivate. I'm sure I'm overlooking something silly. But I simply cannot figure it out.

Thanks for the quick response. I've read, then re-read what you suggested and I'm not sure I follow. I've attached a sample of a "mission complete" trigger I'm using, for reference: This trigger: 1) Sends a "Mission Complete!" message when 90% of the enemy group is dead 2) Deactivates enemy group (labeled: Waypoint-1) 3) Deactivates JTAC drone (labeled: WPT-1) 4) Spawns another random mission (Flag "1") Based on this, I'm not sure how I'd implement the Flag 1 is "True" and "False" conditions properly. Do I need a completely seperate trigger(s) for that? Sorry for being dense, I'm just now getting into this more complicated mission building. Any additional insight you can provide is greatly appreciated. Thanks for your help!

Scenario: Group of enemy armor pops up on the map, automatically spawning a JTAC drone to lase the targets from above. I've got my trigger setup such that as soon as I've destroyed all the enemy units, the JTAC drone gets deactivated. However, when that happens, a pop-up message appears that the drone was "KIA". Is there a way to adjust the trigger or use a new flag to simply remove the friendly JTAC unit from existence without actually "killing" it and setting off the "KIA" mesage?

Bumping this. 1.5 years since this has been reported and even on 2.7 Open Beta, we still cannot see range or time to intercept of tankers when setting them up in Mission Editor to transmit on Y band. X band works perfectly, even if the tanker's tacan is setup for Y band. What's weird is that the default Through The Inferno missions have properly working Y band. I've even spoken to Deadlyfishes via Discord and he's unable to explain how they got it working. Even if you add a new tanker into their default mission, Y band for that new tanker doesn't work while the others do. It's extremely odd.

^ Yep. There are a ton of different preset options you can use when creating missions. If you only rely on multiplayer servers, then you are obviously going to be at the will of whoever hosts the server. In my personal missions, I've been testing everything from maximum clouds/storms to minimal cloud cover and I'm loving every bit of it. VR was already extremely immersive. But now, the dynamic realism is on a level well beyond what I expected from this update. For instance... This morning I took off from the Lincoln, which happened to be inside a clearing in the clouds, with a dry deck and the sun shining through. I took off, ran into a wall of rain/clouds about 3nm out, with a new sound of rain hammering the canopy. So I punched above the cloud layers to reach blue skies. After going on to complete my A2G mission, I decided to keep heading North and land on the Washington. The Washington happened to be smack in the middle of a massive storm. Despite flying in perfectly clear/blue skies just 15nm out from the carrier, on my final approach I was flying head on into a very dense storm to complete a Case 3 recovery. As I got within 3nm of the carrier, visibility diminished to 0 and all I had was my gauges and the LSO to get me down safely. It was the first time in a very long time that I've completed a flight then had to sit back, reflect on the entire experience and think... "Wow."

Welp, I'm blown away. Not only do the new clouds look amazing, but they've notably improved the VR visual clarity inside and outside the cockpit. Everything just looks much more 'crisp'. So much so, that it's halted my plan to swap my Rift-S out for the HP Reverb G2. To top it off, performance didn't seem to take much of a hit, either. I am seeing a little more stuttering on the carrier in very severe weather. But nothing crazy. And once airborne, it's gone. One issue I am seeing is the thicker clouds appear to bounce and stutter around a bit. Granted, with all the new VR setting options, it could just be that my settings need to be tweaked to correct that. Regardless, I'm more than impressed. EDIT: Looks like they are already aware of the jumping clouds issue and are working to resolve it: https://forums.eagle.ru/topic/267894-jumping-clouds/

In 5-6 years, someone is going to read that and think, "Woah! There was a time when even someone with a beefy setup couldn't read text in the cockpit?!" I'm already excited to see what future hardware will do for DCS in VR. Just imagine a 4K VR image at consistent 60fps. One can only dream.

Great point.

Watching those HARM videos today, all I could focus on were those new clouds. That said, I remain pessimistic that the new clouds are going to bring the VR performance of my rather beefy system (water cooled 3090 FE & 5900X + 32GB 3600MHz RAM) to its knees. I truly hope I'm wrong. However, in nearly all other games I play, "cloud quality" is one of the main things I inevitably turn down to notably boost overall performance at 1440p. If ED can pull off the addition of these clouds with "minimal" graphic performance (let's call it 5-10FPS), it'll be a miracle and all other game developers should use this as a case study. Needless to say, I'm quite skeptical. But man, they look so good that I may even consider putting the VR headset away and going back to playing on a 2D monitor with TrackIR, just so I can experience those new clouds in their full glorious form.

Commenting to subscribe to the thread. Really looking forward to this.

Thanks for the reply. I've triple checked that I've got the settings right while in each jet. A/A range works properly with Y band when flying in online servers or in missions created by others (ie - Through The Inferno). However, for the life of me, I can't figure out how to get Y band to work in my own missions.

I've been getting my hands dirty and having fun learning the ins/outs of mission editor. However, there's one issue that I cannot seem to solve. Which is getting range to show up when I have a tanker set to Y band in the advanced waypoint tacan settings. If I leave it on X band (ie - "41X"), bearing and range show up just fine. But as soon as I change it to Y band ("41Y"), the range no longer shows up. I've tested this with the hornet and the viper and the issue persists in both airframes. I even downloaded the Through The Inferno missions (where Y band tankers are working correctly) and confirmed that my tacan settings are setup just the same. So I'm at a loss on this one. I've attached a screenshot, in case it helps. I appreciate any input.

Right after the AMD announcement this morning, my neighbor texted to alert me that BestBuy got a bunch of 3090 FE's in stock. So I decided to give it a go, thinking there was no way I'd get through check out in time. But sure enough, I snagged one. It's now set to be delivered Monday. Thanks to Best Buy's extended holiday return policy, I'll have until January 16th to return the 3090, if I wish. With that said, I did watch the AMD announcement this morning and the 6800XT really surprised me. So now my plan is to put the 3090 through its paces with DCS with the Rift S, as well as Cyberpunk 2077 and the new Assassins Creed. During this time, I'll be watching real world reviews of the 6900XT, very closely. If it's within even 10-15% of the 3090, in terms of performance, It will be very hard not to jump ship to the 6800XT and return the 3090. Especially with the $500 price difference. It'll be interesting to see how the next 2 months pan out, regardless.

Target Management Switch - Up to lock a target in default RWS mode Target Management Switch - Right to lock an initial target in TWS mode Target Management Switch - Up to lock additional targets in TWS mode Target Management Switch - Down to unlock targets in RWS/TWS modes I'm going off memory here, so someone correct me if I'm wrong.

Yeah, I was just using the JTAC laser code, with no pod. But I've done that countless times previously and never had to make the MAV page SOI in order to uncage. This additional step had to have been added within the last 1 or 2 updates.

Excellent. I'll give this a try right now. If this solves the problem, then it is definitely a recent change that was implemented since I last used the MAVs in the hornet ~2 months ago. EDIT: That did it! Thanks! I wonder what update they added the step where you have to be in the MAVs page with it SOI'd for it to uncage. That's definitely new, to me at least.

AG and Master Arm are on. What screen would I want to make SOI? I'm not using a targeting pod so no need to SOI that screen and as far as I'm aware, you can't SOI the Stores page (where the MAVs are selected). Master Arm is on.

TDC Depress isn't doing any good either. I'm at a real loss here. Literally just circling my JTAC target as I type this. LOL

I just tried using the AGM 65E's in the Hornet to attack a JTAC target. It's been a while since I used these. However, I'm noticing that I can no longer uncage the maverick to scan for the lased target. I ensured my key binds remained unchanged ('C' for Cage/Uncage). But I can't get it to uncage, even when i have the target waypoint designated, proper JTAC codes programmed (1686 in this case) and within 10nm of target. I checked Matt Wagner's videos to see if there was a recent video discussing a change to this system and didn't find anything. Any suggestions?

Unless I missed an announcement, I wouldn't say it's "confirmed". Nvidia and board partners have not officially confirmed it. But based on all the reputable leaks, I think it's safe to say it is definitely coming. With that said, I'm with you on the wait. While I do think 10GB VRAM is adequate for almost all games, including DCS, waiting a bit longer for a 20GB 3080 seems like the smarter move. I'm going to hold off on the GPU upgrade, which is out of my control anyway, considering the complete lack of stock. For now, I'm going to turn my focus to the 4000 series Ryzen CPUs. I know I'm leaving a bit of performance on the table with the 3900x, compared to something like the Intel 10900k.