June 18, 20178 yr I deleted the "Standard.xml"... ( Let it rebuild a new one ) and now I have ground friction that I enjoyed before. I set my null zone to 35 for my brakes, had no issues with my test landing at LEVC. Taxied how it should, braking was normal, and had to use autobrake "2" I don't use fsuipc for callibration, so this may not help others. System: MSFS2024, ASUS Rog Stryx Z790-A, Intel i9-14900KF, Asus ROG Ryujin III 360 , Asus Hyperion Case,Rog Stryx 4090 OC, Samsung 970 EVO M.2 SSD, 1Tb Samsung 860 EVO SSD,64Gb G Skill Memory, Asus Aura 1200W Gold PSU,Win 11 ,LG C4 48" 4K OLED Screen., Airbus TCA Full Kit, Stream Deck XL. WinWing FCU, EFIS, MCDU
June 18, 20178 yr 1 hour ago, Travelling_Wilbury said: I deleted the "Standard.xml"... ( Let it rebuild a new one ) and now I have ground friction that I enjoyed before. I set my null zone to 35 for my brakes, had no issues with my test landing at LEVC. Taxied how it should, braking was normal, and had to use autobrake "2" I don't use fsuipc for callibration, so this may not help others. where is the standart . xml located ? just delete it and let it rebuild and it works again ? oh man ! always head up ! Andre Schütte
June 18, 20178 yr What is the standard XML? I did a full clean install of v4 so not sure why would I need to let it rebuild? I have no v3 on my PC. Where can we find standard.xml? Tomasz Zawadzki
June 18, 20178 yr Standard.xml contains all of the controller definitions and settings. Deleting it MIGHT help in the case where a mis-assigned axis is causing the brakes to drag, (and giving the false appearance of increased ground friction). But- deleting it seems strikes me as being a rather drastic solution. If you delete it, you will have to re-do every one of your controllers' axis and button assignments, and possibly all the calibration sensitivity and null zone settings as well - exactly as if you had just installed P3D for the first time. Jim BarrettLicensed Airframe & Powerplant Mechanic, Avionics, Electrical & Air Data Systems Specialist. Qualified on: Falcon 900, CRJ-200, Dornier 328-100, Hawker 850XP and 1000, Lear 35, 45, 55 and 60, Gulfstream IV and 550, Embraer 135, Beech Premiere and 400A, MD-80.
June 18, 20178 yr When I actually start to decelerate and use breaks, there is a green line on speed tape on PFD appearing depending on the strenght of braking. That's for me another hint that there is nothing happening with my hardware, as when I don't touch breaks, nothing appears there. I just let the aircraft slow down itself from 80 knots to 0 and there's definitely something off there. In turns aircraft almost stops. Tomasz Zawadzki
June 18, 20178 yr The aircraft behaves exactly like it would in Fsx or p3d without dynamic friction enabled. We just need to wait for pete to update fsuipc5 Aidan Hutchison
June 18, 20178 yr 1 hour ago, achutchison said: The aircraft behaves exactly like it would in Fsx or p3d without dynamic friction enabled. We just need to wait for pete to update fsuipc5 think so, renewing standard.xml did not solve it here always head up ! Andre Schütte
June 20, 20178 yr On 6/18/2017 at 1:53 PM, achutchison said: The aircraft behaves exactly like it would in Fsx or p3d without dynamic friction enabled. We just need to wait for pete to update fsuipc5 Has anyone told Pete about this because if not, don't expect him to read your mind. Eric
June 20, 20178 yr 9 minutes ago, B777ER said: Has anyone told Pete about this because if not, don't expect him to read your mind. Yup. May be a while because 64 bit has, and I quote "spooked" Pete! Aidan Hutchison
June 22, 20178 yr Author Just to report back: The ground friction issue is now solved with the latest micro update. Thanks for fixing it. Jan Jan Guetter
June 22, 20178 yr The ground friction problem has been 'almost' solved by PMDG in the latest update a few hours ago. But taxing still requires a little more thrust than previous versions. I'm now waiting for FSUIPC5's ground friction modification. Yunchong Huang
June 22, 20178 yr Author That's interesting. I can't confirm that. 28%N1 is enough to get the plane moving. Once at target speed (say 25 kts) I reduced to idle thrust and the plane kept moving at 25 kts. It would neither de- nor accelerate. To me this seems correct as I was almost fully loaded. Jan Guetter
June 22, 20178 yr 40 minutes ago, hawx2k said: That's interesting. I can't confirm that. 28%N1 is enough to get the plane moving. Once at target speed (say 25 kts) I reduced to idle thrust and the plane kept moving at 25 kts. It would neither de- nor accelerate. To me this seems correct as I was almost fully loaded. Just reinstall the update and I experienced the similar: advance thrust to 28% N1 the plane start accerating. Then reduced thrust to anything below 25% N1 the plane started to slow down but very gently, AND independent of weight setting. Kind of similar experience in the 747. Yunchong Huang
Archived
This topic is now archived and is closed to further replies.