November 20, 20178 yr On 19.11.2017 at 8:42 PM, J35OE said: In case of the PC-12 at MTOW this would mean it should be centered for flaps 0° at approx 118kts, 15°/96 30°/88 and 40°/83. As close as i can get to this Table is with a value of ...number) 2.35 - /-/ }</Script> 0° /125kts 15°/95 30°/80 40°/72 Win 10 Pro | P3Dv4.5 | X-Plane 11 | MSFS 2020 | I5-9600K @ 4.8GHz | RTX 2070 8GB | 32GB RAM | SSD | T.16000M
November 21, 20178 yr I can't find this gauge file: Gauge_EFIS_EADIVCV4.xml I have the PC12 v2 for p3d v4.1 Is this the gague for the S550 maybe instead? Ciao!
November 21, 20178 yr 18 hours ago, Raller said: As close as i can get to this Table is with a value of ...number) 2.35 - /-/ }</Script> 0° /125kts 15°/95 30°/80 40°/72 That's quite a big gap, especially at the 40° position.
November 21, 20178 yr 1 hour ago, briansommers said: I can't find this gauge file: Gauge_EFIS_EADIVCV4.xml I have the PC12 v2 for p3d v4.1 Is this the gague for the S550 maybe instead? It should be "Gauge_EFIS50_EADIVCV4.xml" from the Bert Mod... Win 10 Pro | P3Dv4.5 | X-Plane 11 | MSFS 2020 | I5-9600K @ 4.8GHz | RTX 2070 8GB | 32GB RAM | SSD | T.16000M
November 21, 20178 yr Maybe Bert can help: What value has the variable (A:Angle of attack indicator, number) ? Is this a Multiplier 1.88 - /-/ } ? To get closer to the required Table it should be something like this: <Script>(A:SIM ON GROUND,bool) if{ 0 } els{ ((A:Angle of attack indicator, number) +20) 1.62 - /-/ }</Script> We have to add a fixed value to the variable to get higher kts at the certain Flaps-Positions together with the Multiplier! I can't explain it better with my bad english Win 10 Pro | P3Dv4.5 | X-Plane 11 | MSFS 2020 | I5-9600K @ 4.8GHz | RTX 2070 8GB | 32GB RAM | SSD | T.16000M
November 21, 20178 yr You did explain it very well, but it looks like in FSX/P3D you can't use different values, so there's no way to get it to work as IRL.
November 21, 20178 yr I know, but if you add ONE fixed value to the variable and than multiply it with something, the result increases equal to there size value ?!?! I am not a mathematician but i tried it theoretically and it comes closer to the "Table". But i don't know if "(A:Angle of attack indicator, number)" is like 125 or 1.25 or 0.001346 confusing... Win 10 Pro | P3Dv4.5 | X-Plane 11 | MSFS 2020 | I5-9600K @ 4.8GHz | RTX 2070 8GB | 32GB RAM | SSD | T.16000M
November 21, 20178 yr Author 2 hours ago, Raller said: Maybe Bert can help: What value has the variable (A:Angle of attack indicator, number) ? Is this a Multiplier 1.88 - /-/ } ? To get closer to the required Table it should be something like this: <Script>(A:SIM ON GROUND,bool) if{ 0 } els{ ((A:Angle of attack indicator, number) +20) 1.62 - /-/ }</Script> We have to add a fixed value to the variable to get higher kts at the certain Flaps-Positions together with the Multiplier! I can't explain it better with my bad english "A:Angle of attack indicator" is a standard P3D variable that is measured in Radians , ie an angle It has a maximum value of 3.14. as best I can tell... maybe it is hundredths of a Radian... The gauge subtracts a fixed value (1.88 or 2.14) from this value, and changes the sign from + to -. This then is the shift distance for the pointer which goes from +1 to -1. There is no direct relationship to airspeed.. Bert
November 21, 20178 yr That may helps, my personal fight I will play around with it and try to figure it out... Win 10 Pro | P3Dv4.5 | X-Plane 11 | MSFS 2020 | I5-9600K @ 4.8GHz | RTX 2070 8GB | 32GB RAM | SSD | T.16000M
November 23, 20178 yr Ok, i tried a lot of very complicatet calculations including calculating parabolas, to optimise the indicator (btw i learnd a lot) to finaly found the easiest way to get close to the Table: <Script>(A:SIM ON GROUND,bool) if{ 0 } els{ (A:Angle of attack indicator, number) 2.25 - (A:TRAILING EDGE FLAPS LEFT ANGLE,radians) - /-/ }</Script> At any Flap-Position, the Value (ie 2.25) had to get a certain amount higher (in a smooth way so the needle won't jump to much) to correct the display. It limits the way to the (F) direction with each Flap-Positon, but that won't bothers to much. Now i get these values (at no wind, clear sky, 600 feet Alt): 0° /118kts 15°/96 30°/88 40°/81 Tata... free to try Win 10 Pro | P3Dv4.5 | X-Plane 11 | MSFS 2020 | I5-9600K @ 4.8GHz | RTX 2070 8GB | 32GB RAM | SSD | T.16000M
November 23, 20178 yr Hi Raller, Thans for your efforts - I’ll try it when I get home this weekend... Regards, Scott
November 23, 20178 yr Author Neat stuff Edit: Just tested it.. it works! Very nice! Personally, I am going with 2.14, rather than 2.25 just so that the indicator can go all the way to the F (Fast) mark. But that is personal preference. Bert
November 23, 20178 yr Win 10 Pro | P3Dv4.5 | X-Plane 11 | MSFS 2020 | I5-9600K @ 4.8GHz | RTX 2070 8GB | 32GB RAM | SSD | T.16000M
November 24, 20178 yr Author I have included this is the latest roll up of the various mods: V5.7. Are we going to see V6.0.? Bert
Archived
This topic is now archived and is closed to further replies.