All Activity

This issue constantly happens. Spent hours trying to fix it. AFCS only works on initial flights, never works again after repairing at an airfield and restarting the exact same way.

Are the F-18 cockpit dimensions known to be inaccurate? I was under the impression it was pretty accurate in that regard. As far as rendering, textures and art looks great to me on the Hornet. The new Fulcrum and Hornet look similar to me, with maybe the Hornet a having slight advantage in clarity and performance (FPS) in VR. Quality is always subjective though, and it’s a balance in terms of ensuring the final product is well optimized. Insane levels of details are not fun if it ends up crushing all modern hardware out there. My personal opinion (again, in VR) is that the Hornet is the gold-standard module in terms of cockpit art, quality, and efficiency. I think the Mig29 has come close to matching it.

Thanks

It helped me

I already preordered it . but i don't expect the cdu information to be available in DcsBios at launch.

I think I did everything correctly. Here are the files you requested. The reshade.log was split so I included all fo them options.lua ReShade.log5 ReShade.log1 ReShade.log6 ReShade.log3 DCS_VREM_techniques.ini ReShadePreset.ini DCS_VREM.ini ReShade.log2 ReShade.log4 ReShade.log

I am having the same issues with my OG Crystal.

I agree, this last update is very nice.

I remembered this thread 4 years ago by the pilot. SPO doing its SPO things and a technician showing it could be fixed if it helps clear things out And there you have the RWR being blinded by the radars, and the N019 itself too...

With COOP, HMS, first sensor to lock is primary. But both will lock when possible anyhow. If you get HMS lock more then 30 degree from nose, guaranteed to be radar lock only with COOP.

This just happened to me after Speed and Angels Mission 13. Love how bugs from 5 years ago work their way back in... can't end mission.log dcs.log debrief.log

It should be possible, it was on older R-27, to reach 90 km with R and 130 km with ER. The limit is radar range. So you’ll probably be limited to 70 km in fulcrum unless it’s home on jam.

If maintenance manuals say it can be fixed, I believe them

with the coop switch funtioning , it will be possible to handover a HMD lock to the radar missles?

Latest update had "GPU upscaling" on by default; Looked terrible. Turning it off, I now have best perfomance/eyecandy ever. Also, try the MSAA 4x and no DLSS.

Absolutely a great candidate for an update!

You can adjust it client side. Both the font size and the size of the text box itself can be reduced without violating IC. In VR it's almost necessary for some servers, especially Contention.

It takes a while for content to come for a map… it requires a number of factors not least of which is a campaign creator to take an interest…

Alright, it does say it that way. But anyway, it seems like SPOs usefullness in such situation is questionable at best

Thank you, I think the canter line tank was the issue. Who would have thought of that…..

Hi all, Has anybody had any luck landing on the carrier? I just tried the instant action in the Caucasus, chose one of the 'air' slots, but I can't seem to catch the wire. This has happened several times. I'm not sure if it's a bug, as I was on AoA at about 130 knots and the track shows that I should have caught it. I'm not sure if the carrier is a 'dummy' ship or something. T-45_Carrier_Landing.trk

Fabulous work as ever. Will get it downloaded and tested on my machine tomorrow. Now the big question is how much do I need to bribe you, to look at getting this on the C130 when she finally lands.

From P57 in the manual: "Speedbrake operation is not possible with the centerline tank installed, or gear down. In case of general electrical failure, the speedbrakes retract automatically"

Hi everyone, I've purchased very recently a Pico 4 and I'm trying to set it up, although I'm a tech guy, I never had VR before so I'm out here for help and couple advises. After tweaking a lot I managed to have 72fps stable. This is what I've done so far: VD in Pico installed and running on 72 fps frame rate, 72 video frame rate, 120 mbps video bit rate, Ultra settings. VD on pc with HEVC, VDXR, Encrypting local traffic for that stupid BSOD (I'm using a 3.2 USB-C cable with the tethering trick) OpenXR toolkit installed but nothing really tweaked there. So as a matter of fact, no matter what I'll do, everything feels blurry in the cockpit and everywhere around, especially in cockpit, like numbers indications, lights etc. It feels like everything is zoomed and blurred at the same time. I get it that it might has to be that I'm running the whole thing in low settings to have these 72fps stable, but I've seen other people on Yt videos having their picture seem crystal clean. So i'm not sure what I'm missing here. On the other hand maybe I'm not missing something as this might be the drawback of using VR... I'll post my specs and screenshots of my settings rn in DCS. If you have any sort of suggestion to make it look nicer and more practical for PvP servers I would really appreciate your help. null PC SPECS: I7-13700k 32GB RAM RX9070XT SSD (with only DCS in)

Don't use Auto, Use P (150km scale) for situation awareness then switch to Dogon, this is what (Boro Zoraja actually did). For a kick try to make the transition too early (e.g. around 50km) and the RL will start fleshing and drop lock after 2-3 seconds, but if you wait a bit longer it will not loose it.