Ginsu80

I recently upgraded my old Rift S to a Quest Pro. Does anyone have any settings or tweeks for the pro. The visual quality is much better but performance wise I've definitely taken a hit. I have been using Oculus Tray Tool and fiddling with some of the settings, without a whole lot of luck. Wondering if anyone has had more luck that me. Currently running a 5800x3d and 3080ti, DCS and windows on SSD, 64gb of ram.

Same, updated everything, clean/repair using skatezilla, downloaded opencomposite, openxr, follwed the guide. No hands with the G2

For some reason the UK faction shows only the Handy Wind for me, none of the new assets are available. I can see the assets in the encyclopedia, just can't place them with UK, or with Coalition Joint Task Force. I am running the latest open beta, I have done a full repair, and I have tried multiple time periods, all without success. I'ts like the asset file for the faction didn't update for me, any help?

Bump this topic. Frustrating to have your flightplan waypoints dragged around the map while targeting with the pod. Fingers crossed for a hotfix.

Still marked as needing replay despite having replay. Did the replay not work, it was very short and just included the bug.

I posted the track. I’ve tried repairing and done a full clean install and I can still get the bug to occur. Has anyone taken a look at it?

I did a little more testing, the bug only seems to be there when you have the JSOWs loaded with the Harms. With the JSOW powered on and the HARMS loaded switching to guns leave the pipper well below the Line of sight. Boxing and unboxing HARMS with one HARM still on a station can fix the bug. If you don't have any HARMS left boxing and unboxing won't clear the issue. I ran the same mission with CBU-99s loaded and couldn't get the same behavior. Hope the track helps. It was the simplest track I could get. pipper problem.trk

After using HARMS in TOO mode on the Nevada map the GUN pipper will not take into account the correct ground elevation and the rounds will land high. If you have a HARM left on the rail you can fix it by selecting then deselecting the HARM pushbutton on the STORES page. If you have no HARMS left you can't clear the error. I will try and get a track file but I have been able to reproduce the bug several times.

I am having the same issue, using .10 version of DCS-BIOS hub. After 5 or 10 min DCS Bios devices stop working, and the hub shows no ports connected. I have to restart DCS-BIOS and the game to get it to connect. I think I may have exceeded the limit for number of DCS-Bios devices. I have 10 connected for my simpit. I am trying to find a work around and am totally frustrated.

I also had this issue with the newest update. On my first run I was able to zoom in, on my second and subsequent runs the FOV button did not change the FOV.

I am wondering if anyone is still working on the Jug? I have been reading up on WW2 P-47 tactics, notably Zemke’s Wolfpack, and they note that the Jug had excellent dive performance and a good roll rate as strengths. This doesn’t seem to match in DCS as the roll rate seems sluggish compared to all other fighters and dive performance is so so. I don’t see many changes in the patch notes, are any changes coming to the P-47?

I haven’t had a crash yet with the AI on takeoffs, even with normal max take off weight but I know others have. The AI does pull stupid aoa, and come really close. I have also seen the AI get slow, 115kts or so and get stuck and fail to recover. Literally just fall out of the sky. Hoping it will be fixed this week as it’s caused me to be unable to work on t a campaign I’m building.

I have noticed that it isn't just takeoffs, I watched an AI Hornet attempt to rejoin with the recovery tanker. After turning in he bleeds speed down to 115 kts and gets stuck. Literally just falls out of the sky from 6000ft. Plenty of gas, this occurs just after take off. Never plugs the blower in, just sits there at high AoA, 116kts or so, chasing the tanker and falling out of the sky until splash. I'll try and grab a .trk file. Something screwy is going on and it's not just take off.

Bug: Wings are overfolded on A model static objects Can I reproduce it 100%: yes How to reproduce/ description: All static object A models have the wings overfolded, as the B model used to. B model appears fixed. Current Open Beta version patch from 2/21/21 Video/ Screenshots: Left is AI aircraft on ramp start, center is A model static, Right is B model static

So it appears this bug was fixed for the F-14B, but has no cropped up for the F-14A in the 7/21/21 patch. Strange, and frustrating. I had changed all my statics and templates over to the A model since it wasn't bugged, now it is and the B isn't.

Can you send a screenshot of the controls? I'm trying to tune to a preset and also change it to compass to radio direction find to a ground unit for a farp.

If you mean the one with the selector behind the left elbow of the pilot/commander the rotary dial does not change the presets I've set in the ME for the R-828.

I don’t see the r-828 where is it

Where is the control head for the FM air to ground radio. I can see it with SRS but can’t tune it.

The radios, navigation. Everyone is posting videos of the weapons, the beauty, the sounds. I don’t know how to navigate or get from point a to b and back. I for one am desperate for a more complete Mi-24 HIND guide.

Cool. How?

I wish there was a way to set it for AI aircraft, or at least get them to stack up. I have tried statics on deck etc, but currently the AI aircraft just fly the case 1 pattern and land immediately, I can't get them to stack in the marshal and wait on a launch before recovering.

Has anyone noticed the JSOW-A doesn't seem to do any damage. I put a couple on a sam site, SA-5, and watched the bomblets hit the launcher and the radar. There didn't seem to be any damage though. Radar continued to work, missiles continued to come off the launcher. Tried again with JDAMS, and no issues so the units aren't set to invincible or anything.

I have flown several CASE III approaches, and on each the lights have been on for me. One thing I have noticed is that the Long Range Laser Lineup System is visible for miles, but, the rabbit lights and LA lights are dim and can only be visually acquired from a couple miles. Edit: At your TACAN distance though they should be on. I'm thinking you needed to call inbound on comms. Flow is Inbound, Established, Commencing, Platform. Most of the other calls, Needles and such, are automated until the ball call if I remember correctly.