February 25, 201610 yr Not the tyres - those would be the brakes. Have you rejected a takeoff or two to drive the temps up? Yup! I do two RTOs at max weight until the plane wont move and the gear synoptic is orange and I get 10.0 break heat, but funnily enough No red brakes Same here. Was practicing RTO's a few days back and to my surprise no red glowing brakes. GEAR synoptic showing > 9.5 on all brakes and all fuse plugs melted. Probably broken by V3 or 3.1. Just like the landing/taxi/turnoff lights were not showing on the ground initially in V3. Fixed with 3.1
February 25, 201610 yr Commercial Member Yup! I do two RTOs at max weight until the plane wont move and the gear synoptic is orange and I get 10.0 break heat, but funnily enough No red brakes Same here. Was practicing RTO's a few days back and to my surprise no red glowing brakes. GEAR synoptic showing > 9.5 on all brakes and all fuse plugs melted. Probably broken by V3 or 3.1. Just like the landing/taxi/turnoff lights were not showing on the ground initially in V3. Fixed with 3.1 Yeah. Tested myself earlier as well. I've passed it onto the modeling team. Kyle Rodgers
February 25, 201610 yr Have you rejected a takeoff or two to drive the temps up?Hi Kyle, I can confirm I also see no glowing brakes anymore on P3D 3.1 Wes Meyer
February 25, 201610 yr Yeah. Tested myself earlier as well. I've passed it onto the modeling team. Theres a bunch of quirks I've noticed which im gonna attribute to P3D 3.1 and windows 10. 1 Theres a bug where entering a specific fuel number in the FMC at payloads lower than 50% causes ZFW to change around and you'll have to re enter fuel a couple times until you get correct ZFW and the fuel you wanted (in 777X, havent tested NGX, ask MR Gollnick for more info) 2. DELETE YOUR SHADERS: every time you install new textures like REX or PrecipitFX, change your display settings or CFG, update your graphics driver or change inspector settings you HAVE TO REBUILD YOUR SHADERS. failure to do so will result in stutters which culminate into an ntdll.dll CRASH!. Furthermore, I've noticed fewer stutters and random crashes (related to ASN rendering new weather after being paused for a long time at TOD) by using adaptive vsync in NVIDA combined with P3D internal vsync with triple buffering at unlimited frames 3.P3D is a moving target so every new update will break at least one thing and yes Ive done a clean install of windows and that did not change anything either. The only good thing about FSX is that despite its bugs they remained constant and we could confidently work around them with worrying about them changing 4.Theres more if you want to hear Flying Tigers Group
February 25, 201610 yr Commercial Member 4.Theres more if you want to hear Not much we can do if the various items are more related to the core sim and less to our stuff. I'd encourage you to reach out to LM to report things as you see them, though. I think, as a community, we've gotten so used to the sim being 'static' and not supported that we're still seeing people report everything to the add-on devs and not as much to the sim dev. If you see things like 2 or 3, definitely point them out to LM. 1 has been acknowledged. I watched the ticket from the sidelines. Kyle Rodgers
February 25, 201610 yr Not much we can do if the various items are more related to the core sim and less to our stuff. I'd encourage you to reach out to LM to report things as you see them, though. I think, as a community, we've gotten so used to the sim being 'static' and not supported that we're still seeing people report everything to the add-on devs and not as much to the sim dev. If you see things like 2 or 3, definitely point them out to LM. 1 has been acknowledged. I watched the ticket from the sidelines. True LM needs to know, but I also thought its worth telling you the major ones so you could pass it on to the dev team or share with people on the forum for awareness Flying Tigers Group
Create an account or sign in to comment