Redliner7

Count me in as also having unintentional induced oscillations on the pitch axis after pulling back on the stick, when I return the physical stick to neutral, the virtual stick and stab will pitch too far forward upon return and have forward stick axis. I've also noticed that I trim a lot LESS than the Tomcat as well, I thought I'd be trimming more often, which is peculiar to me. I've tried turning off the ffb option as suggested, no effect for me. I'm flying with a TM Warthog. Sent from my Pixel 7 Pro using Tapatalk

Do you think some of that discrepancy is just comparing newer Hornets at the time to worn out Tomcats in up time? https://news.usni.org/2023/02/10/cbo-report-on-super-hornet-availability In this article, newer Super Hornets are suffering greater downtime in lesser time it took than the Legacy Hornet even. Which both are way worse than any AF planes. Also, even current F35 Readiness is at 55% according to: https://www.gao.gov/products/gao-23-105341. You're more in-tune than me so i always value feedback from someone that was there but my take away is that any new technology will perhaps suffer from reliability and maintenance issues. And in the case of the Tomcat, combine that with the first of its kind wrapped in analog 60s tech and a big heavy plane that's living in salty conditions, i think it was always going to be an uphill battle after year 10. Sent from my Pixel 7 Pro using Tapatalk

[emoji106] Sent from my Pixel 7 Pro using Tapatalk

The juice isn't worth the squeeze - it's such a tiny part of the overall Tomcat experience, I think it should be removed if it pulls dev time away from the bigger issues at hand. I mean if I'm reading it right, you also prevent guns from working and increases engine stall margins so what's the point? Sent from my Pixel 7 Pro using Tapatalk

Thrustmaster Warthog with the T1600 rudders Sent from my Pixel 7 Pro using Tapatalk

[emoji106] when i mean no AOA, nothing more than just keeping level flight at around 300kts. I'd test more but my headset is blacking out now :( Sent from my Pixel 7 Pro using Tapatalk

I've never tested the plane a lot until recently to try to get a handle on it but after this discussion. i went out to play with the rudders to see its behavior at various speed, altitude and AOA and i could not for the life of me figure out repeatable tests. Specifically this one test... Level flight, no AOA, full rudder and it would side slip a tad before drawing a lazy roll with the nose tracing a circle. That's expected behavior, correct? This is what i remember in past FMs But every once in awhile, doing the same thing but maybe at a different altitude and speed, i got into a flat spin. This isn't possible, is it with just rudder input? Again, no AOA on the jet, just level flight. I wish i was a better "test" pilot, i didn't take very good notes on what altitude and speed i was at :/ Maybe my rudder pedals are broken?? Sent from my Pixel 7 Pro using Tapatalk

Thank you! Sent from my Pixel 7 Pro using Tapatalk

I hope Heatblur looks at this. If they verified high AOA FM with SME in '21 and made adjustments for yaw SAS since then, it might've been some unintentional side effects. Definitely gotta figure out new ways to beat the Bugs until then [emoji23] Sent from my Pixel 7 Pro using Tapatalk

Thank you for taking your time to respond and appreciate the hard work. I'm not the only one reporting it, others feel there's something a little off too, but I also have no way to quantify my own experiences (or theirs) either. You're right, i don't try to live at 25+ units at all, but if you end up in a one circle with a hornet or mirage, that's what usually ends up happening. It's here where I *feel* like I've lost some rudder authority and/or pitch authority. I've never turned off Yaw SAS FWIW so i have no idea how it behaves with Yaw off. Roll SAS is off for any BFM that I do however. Sent from my Pixel 7 Pro using Tapatalk

If you're reducing YAW SAS, doesn't that mean we're supposed to have more or less Rudder authority? The rudders feels pretty ineffective at high AOA and pitch authority feels significantly reduced as well past 25 units. Sent from my Pixel 7 Pro using Tapatalk

I thought i was the only one experiencing this. Completely unscientific.. But did we lose a few degrees of nose authority at full 30AOA with the last 2 FM updates? I know wing rock and transonic drag was moved around to be more realistic to match the charts. I ask this because I used to be pretty even with my buddy in a Hornet by getting him slow and dancing on the stick and rudders, i was *just* able to hang with him in a 1 circle. And it could go either way in kills. For example i used to be able to nose over with rudders going slow vertical, or be able to squeeze just a few more degrees of nose attitude to get a shot off while really pouring on the AOA. Now he just dominates me and I can't seem to get the Cat to do what i think I was able to do with the high AOA stuff earlier in the year. And man do rudders feel a lot less effective at high AOA... Even on the deck where I used to dominate him in the 2 circle, I'm pretty much helpless now. Maybe I've just flying poor BFM but it's been difficult fight in the Cat lately. If that's what the real jet is like than so be it - but i didn't see any notes and would like clarification or if it's just me. Sent from my Pixel 7 Pro using Tapatalk

Has flat spins and post gyro stalls become more difficult to initiate with the latest FM changes? I can't get it to depart flight and I'm doing some really stupid things on the stick including cross-talking all 3-axis and one engine idle and the other in burner. I figured at least one or 2 of these stupid moves would've departed flight. Sent from my Pixel 7 Pro using Tapatalk

I for one, bowdown to the great overLord supreme chancellor Lance for the skin! Sent from my Pixel 4a (5G) using Tapatalk

IFF is a big one. I don't fly in multiplayer servers bc the few times that I have, I end up with a team kill. It's very frustrating when I thought it was for sure a bandit. Sent from my Pixel 4a (5G) using Tapatalk

Quick and dirty test w/ Dragons Tooth but I used to only hit 1/4 or best case scenario 2/4. I've always chalked this up to "old missile tech getting notched" and just accepted it as fact. This time my wingman splashed all 4 first...great work, whether it's been buffed or nerfed, I don't care. I'm just glad it's accurate. And if this is how the -54 was supposed to be in real life, then all the better! Thanks HB!

Rift s -> hp g2 here. Can't go back to flat screen at all.. but setting up the HP G2 was a pita for me i went from crashing, to micro stutters to finally getting stable framerates. 11700,3080,32gb. Just stupid how much time to get it running decently but worth the pain. Sent from my Pixel 4a (5G) using Tapatalk

Update: Trying to replicate the factors that cause the issues I've discovered that if I start up the F14 Instant Mission, Clay Dagger Lantirn MIssion in the Marianas - after a fresh reboot the frames are stable at 45fps on the carrier and climb to 70fps in the air. If I exit the mission and restart - the frames are jumping from 45fps down to 20fps while it's around 30-45FPS in the air. But if I restart DCS then the frames climb again to stable 45fps. Is this some kind of memory leak? I've reinstalled WMR and Steam VR as well, deleted metashader and FXO folders to no change in effect. Other things I did: DCS, VR server set a high priority. Turned off Dropbox and Windows Defender for sessions. Pagefile set to 65k. Edit: Testing this morning, even after restarting DCS - frame rates are still terrible. A reboot solves the issue for a round of play. Any help appreciated!

Huge 8-bit jagged edges at night when you point the flash light at the canopy frame in VR. It's looks like blocks of white and unfinished graphics. Not a big deal for me but just thought HB would like to know. Sent from my Pixel 4a (5G) using Tapatalk

I've tried both Beta and Stable Steam VR and neither really makes a difference. I also read that turning PCIE to Gen 3 over Gen 4 would help. I haven't gotten a Win BSOD yet thanks to that change but I'm not 100% positive that has solved it. HP G2 is from Black Friday so it should be the latest variant. Affirm on the latest firmware as well.

Thanks for the reply I'm still testing for maximum FPS, so my 2 test missions is the F14 Instant in Syria against the 2 Vipers and the Lantirn at Night mission at the Marianas. I test these over and over with different settings and after awhile my FPS degrades until it hops around to 20FPS-60FPS but it's stuttering and pretty much unplayable. If I reboot the computer, it's between 75-90FPS again. I'm on Version 21H2 and there's no additional updates required according to Windows Update. Logs - Copy.zip EVTX compressed as requested. DCSViewer.zip

Specs: 11700KF, 32GB RAM, 3080, HP G2. Issue: After getting this setup to run smoothly at 90FPS, the framerates will drop to about 50 with dips into the 20s and a lot of stuttering after 30mins of running. I followed the 2 VR guides linked below below in getting my DCS to run well. Attached are my DCS logs. This is a brand new build, only a month old btw. The only mod I run is Kegetys VR shaders mod. I've ran it disabled with no change in effect after the frame rates have dropped. Can someone help point me in the right direction with my logs to see what the issues are? FWIW, I never had any issues with the Rift S crashing or losing frame rates. I have also randomly gotten a "Unexpected Kernel Mode trap" BSOD as well after these sessions. Here was the info in the Windows Event Viewer: - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" /> <EventID>41</EventID> <Version>8</Version> <Level>1</Level> <Task>63</Task> <Opcode>0</Opcode> <Keywords>0x8000400000000002</Keywords> <TimeCreated SystemTime="2021-12-19T17:23:25.7206399Z" /> <EventRecordID>8902</EventRecordID> <Correlation /> <Execution ProcessID="4" ThreadID="8" /> <Channel>System</Channel> <Computer>DESKTOP-3SOJROR</Computer> <Security UserID="S-1-5-18" /> </System> - <EventData> <Data Name="BugcheckCode">127</Data> <Data Name="BugcheckParameter1">0x8</Data> <Data Name="BugcheckParameter2">0x0</Data> <Data Name="BugcheckParameter3">0x0</Data> <Data Name="BugcheckParameter4">0x0</Data> <Data Name="SleepInProgress">0</Data> <Data Name="PowerButtonTimestamp">0</Data> <Data Name="BootAppStatus">0</Data> <Data Name="Checkpoint">0</Data> <Data Name="ConnectedStandbyInProgress">false</Data> <Data Name="SystemSleepTransitionsToOn">0</Data> <Data Name="CsEntryScenarioInstanceId">0</Data> <Data Name="BugcheckInfoFromEFI">true</Data> <Data Name="CheckpointStatus">0</Data> <Data Name="CsEntryScenarioInstanceIdV2">0</Data> <Data Name="LongPowerButtonPressDetected">false</Data> </EventData> </Event> dcs.20211218-141818.crash dcs.20211218-141818.dmp dcs.20211218-142031.crash dcs.20211218-142031.dmp

I suck as a pilot? I dunno!

All in all tho, I think there is probably an advantage being able to turn at .8-.9 mach with the wings @22' - there's just more lift & more predictability right with the wings forward... The biggest thing against the JF17 was that I was able to get my nose around in the 1 circle so much faster than when I'm doing .8-.9 mach with the wings swept all the way back to 68' at the merge and was able to get the kill so much quicker. If I miss the kill at the first circle against the JF17, then I'm doing the usual dance as the Tom gets slower. But it also makes sense why real life pilots would not do this at all...longevity and maintenance mainly!

Cool thanks! I'm asking about wings being wide open at the merge and I want to say that at .8 I'm getting partial sweep if it's in auto-wing... however the point remains...they kept it in auto wing. Appreciate the feedback!