Jenson

Those non-AI players in multiplayer server are like the fanatic war boys in Mad Max.

I encountered the same issue, A/G gun actual impact point above pipper point.

Hi there, I read in the manual that the hornet pitch should be trimmed according to the take off weight as follow: less than 44,000 lbs: 16 degree 45,000 - 48,000 lbs: 17 degree above 49,000 lbs: 19 degree I have a few questions and wonder if anyone could advise: 1. Why there isn't 18 degree recommended? 2. If take-off weight is way below 44,000 lbs, should we adjust it further down to 15 degree or even less? I noted if trim is less than 15 degree, the Master caution will lit, however, when I take off with 35,000 lbs, even if trimmed at 15 degree, the hornet will lift nose up like a rocket after launch. So the real question is, why the take-off trim isn't calculated more precisely based on aircraft weight, especially when take off at a super light weight? Thanks

I have no idea then.

Hi Col. Nakesh, thanks for letting me know. No I haven't read the book yet. I understand that I must be ignorant to suggest this suggest that before reading the book. Maybe I should find some time to read it. Yet I just couldn't help to post some feedback about this campaign, most of them are purely personal preference indeed. I didn't mean to ask the developer to revise it, but just wanna brainstorm some ideas, cheers!

Maybe try if you can open other steam games in VR mode or not, just troubleshooting if this is a more general issue or DCS-specific issue.

Did another attempt, still got a score of 40 and failed the mission. BTW Tron 52 flew away again at 5:50. I kept radar off all the time, and formation on the left of Tron 51 from waypoint 1. Got to the factory, hit all targets, and.... mission failed again, very frustrated. attached debriefing log. F18C Raven One Mission 14 Debriefing.log

Tron 52, the two SEAD escort hornets just flew east after take off and I have no idea where are they heading to. This happens 33% of the time (happened twice with 6 attempts). Sorry no track files. I noted this because after we start to push from waypoint 1, I couldn't find them, even after passing waypoint 3 and only Tron 51 is flying alone. I checked F10 map and found Tron 52 are flying east.

I think you're referring to the SA-2 in the northeast, it will fire at you when you're close to the target area. my advise is after releasing one GBU, make a 45 degree turn to the left so the SA-2 will be on your 3 o'clock, keep lasering at the target and no need to do any defensive maneuver, only a few chaff will help you evade the missile.

Twice I've seen only 3 planes in Sledge team. The second time I checked with F2 view, the other plane was flying like 3k feet below, I have no idea why.

Had the same issue here. In think once we are spotted by the radar (say triggering by flying above some certain level), the radio should transmit "THUNDERSTORM" instead of "HOUSEBOAT" when we reach waypoint 5, otherwise, it's just a waste of time continuing the mission.

Hi there, I had the same issue: The mission just ended automatically when I egress southeast, but when i click end mission, it shows mission failed and gives me a 40% rating. Me and my flight had bombed the weapon factory facilities to the ground. I've tried 3 times and it all end the same, with 40% completion, did i missed something?

I'm willing to pay a one time purchase for additional skins or other special content but not monthly/annual subscription.

Thanks.

Yes, I also experienced the contacts jumping everywhere. Especially in TWS RAID mode, after I acquired 2-3 target as L&S, TD2, TD3, then these already-acquired target just jumped away and I lost like 1-2 target. They just tend to get lost every a few seconds. This happened while I was playing Ravon One mission 13 alert 7. 10 contacts are all within 40 nm.

Does this V33 only apply to quest 2 or it also capply to rift S?

I just take a guess that maybe INR will eliminate the risk of being masked or scene affected by weather.

To clarify, it only affect the HSI map layer in AMPCD display. HSI symbols display is okay, only the map layer turns dazzling in night mode and turns gloomy in day mode.

Trackfile attached hereby. AMPCD night-day brightness bug report.trk After latest update, the AMPCD night/day mode switch seems working in an inverse way. With contrast knob below AUTO 5: Looks okay, as clicking night switch to dim the AMPCD display and clicking day switch to brighten it; With contrast knob at AUTO 5: No difference (AMPCD brightness) between night/day mode; With contrast knob above AUTO5: Looks inversed, as clicking night switch will brighten AMPCD display, and clicking day switch will dim it. Hope above description is clear. Thanks.

I have my air-conditioner installed just above my PC desk. Hope someday the VR headset will be like a sunglass that we could casually put on (with wireless 8k streaming), haha.

Quest 2 wobbles too but the level is insignificant and acceptable, I could feel that it's coming from my head shake or heartbeat. But with Rift S, it kinda bounces up and down irregularly (even in Oculus VR menu, the console bounced with the same behavior). But after unplug the USB and plug it again, the wobbling reduces but still noticeable. Could you please explain more on the open composite (how to solve the problem)? I'm not using steam VR, but I click on the DCS name in my steam game list, then in the pop up window, I click "Start DCS in Oculus VR (something like this)" option to activate the game.

Good to know that, thanks for the adivse

Sorry I need to raise this topic again. With a 2D screen or any single eye in VR, the NVG works fine. Even if with both eye open in VR, there's no problem most of the time. However, when I focus both eye sight on the NVG lense, the problem appears. I conjecture that the randomly-generated lense noise are rendered using the same logical, so the left eye noise could be 100% matched with the right eye noise, which allows the player to find an "illusionary" focus of the NVG lense. It created a illustion that the NVG lense is floating about 3-4 feet away, instead of the actual NVG optical tube length. I hope below picture to demonstrate this issue. I never used a real two-eyes NVG but I assume the noise on the both lenses should be different? (because they're random background noise). If my conjecture was correct, I think using two different logical to generate the noise for left/right eyes should be applied and fix this "bug" - i.e. we shouldn't find any focus for left and right eyes. If you have the same feeling, please kindly add to this post, thanks.

Thanks, this is useful.

After putting on my Rift S, the menu wobbles slightly (sometimes more serious but unplug and plug the USB wire would reduce it wobble). So after I entered the game and sitting in the cockpit, I could see the cockpit also wobbles slightly, does anyone else encouter the same issue and any advise or solution would be much appreciated. Thanks!