April 4, 201313 yr If your problem continues it might be worthy to try it without running FS2Crew to check for conflicts.
April 4, 201313 yr Moderator Good point Ron but only one change per test should be made otherwise if it is solved we won't know which change fixed it. :wink: Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
April 5, 201313 yr Author I did lots of flights with FS2Crew but never experienced any conflict (by the way, I run RC4 on a laptop through WideFS). This is the first time I have such a problem.. I will do some more tests today, but I feel the key is that FL 110. I have now changed the max deviation altitude to 300 ft in the RC settings. James Goggi
Create an account or sign in to comment