Razor18

Hi There, Is it the apps problem, or DCS problem, if I can not launch Model Viewer? null

New RAID video This is a 17 hours old YT video. I assume it was made with a newer version. Look at BRA at bottom left corner, TGT is at 26.8 NM on a 40 NM display. When switching to RAID, TGT range increases to 26.9, then 27, at the same moment the top right corner becomes from 26 to 27 NM and bottom corner becomes from 16 to 17 NM. Based on the RAID display logic described in all sources, those numbers should be 32 and 22, with the 27 NM target in the middle. EDIT: looked up RAID SAM in the same video at 7:25, the story is the same. So maybe worth a look at RAID SAM too...

Hi There, SCAN RAID mode shows a "zoomed in" picture of 22° x 10 NM with the L&S in the center. For example if the L&S target's range is 25 NM, then in RAID mode, at the top and bottom right corners of the radar, the range figures should be 30 and 20 NM respectively. But it never shows it right, the top right corner always shows the actual range to the L&S target, and the bottom number is simply the top number minus 10. Is the calculation really wrong from the get go, or am I missing something? You can see it at 1:05 in Matt's first YT video of the RAID modes way back when Matts RAID modes video

I know it's a kind of old topic, but I was wondering if bank limiter (NAV and TAC) works today as it supposed to work, or is it still not fully implemented? Flown a lot recently, I definitely never saw bank angles anywhere close to 60 degrees with tactical bank selected.

Nope, my pictures above were taken from a 4k monitor and a Quest3.

No, its not the same problem. For the F-18 it never happened before, only since the last or next to last upgrade. And no, it does not just happens to non-16:9 monitors, I have a 4k 32" 16:9 monitor, thats where I took the pancake pictures about the problem from.

Oh, sorry, it didn't came to my mind to make it when happened. It happened on the way home when I checked out from corridor with Magic, and I had to check back with Strike. Guess it was a one liner all capital prompt saying something like "PUSH 2 on PRI TO CHECK IN WITH STRIKE" or something to this effect.

Hi There, towards the end of the mission a prompt tells you to push 2 on PRI to check in with Strike, but Strike is always on Ch3. Ch2 is Marshal. Approaching the boat, first you get Signal is Charlie, but then it says to enter Marshal stack at Angel 3. But 3 and 4 are already in the stack at exactly Angels 3, so there comes an endless circling at Angels 3, looking for the othere Element to avoid a mid air. Apparently never get Charlie again. If you just disregard, and go for tha trap, everything is OK with the comms, Kiss off and Clara in the menu, as if marshalling would never happened after the first "signal is charlie".

Same here, first I thought I messed up something with adjusting the DLSS drivers, but whatever I do, HMD res is now only abut the resolution of the HUD reg. chunkyness. Previously it was very sharp, now it is chunky. Moreover, in VR it is very bloomy due to extra brightness. Top pic is taken from pancake, bottom pic is VR, but the VR screenshot was taken from the LCD too, so bloomyness only visible if you zoom in.

Yup, when I heard Angels 29, but it only changed a couple of ten feets, I was about 28140ish

Thanks! Just a non campaign-specific question comes to my mind: why is the altitude recognition somwhow off? Tanker says he is orbiting Angels 25, but in fact he flies at around 24 500. Or if I fly at 28200, my check in message to Magic says I'm at Angels 29. Probably core DCS related, just asking, if it is a known bug?

What are the proper orbit procedure to start orbit, so that the game can see I'm starting my orbit? Altitude, position, bank angle, or?...

Uhm... nope, I checked that one too. AFter F10 "Engage" order was used up and disappeared, I gave all possible stock commands on AUX, no reply, eventually WM went and targeted something on a distant enemy airfield. Probably because I also tried "Engage ground targets", and that one works for whatever reason? But WM never acknowledged any command on AUX.

Hay Gents, I dropped the two JDAMS by the book (PP coordinates, terminal settings, altitude, ATTK HDG double checked), even "Bank building destroyed" message, still mission failure,. BTW, my "I'm in orbit" trigger (WM stating situation) only kicked in after I overflew the target. As long as I orbiteg 5-6 NM out, nothing happened.

Hi There, after the Gecko kill, using the F10 command for wingmen to attack the GND TGTs, command disappears, but wingman doesn't acknowledges and doesn't do anything. THX for looking into it.