Posts by orange//de mather

Quote from W.B.

Hi,

I’m curious why it’s been a decade since Aerofly was born but we still can’t see weight and fuel, such a basic and important system in flight simulator?

I assume the physical measures such as mass and inertia are already there in the sim. Why not just change them from a constant to a variable and changed with the fuel amount and thrust? It doesn’t look that complex to me. Although it might be more tricky to consider how the weights are distributed within the aircraft. Why not just start with something simpler, I suppose it would be at least better than nothing?

P.S. (not relevant to this topic). Can I ask why the terrain errors in some major European airports such as Charles De Gaulle is still not fixed? It’s horrible to fly.

Thanks,

Display More

In this simulator, it is not just as simple as changing the weight. If the aircraft is too heavy or too light, it will cause the aircraft's thrust system to change, requiring the system to be reprogrammed.

Quote from FrankLFRS

Dear Jet-Pack (IPACS)

I tried it respecting the process, APPR AP1 and AP2 on non-ILS approach. It works. The F-LOC and F-G/S are disguised in a RNAV, but it works. APP NAV first and then FINAL.

May I ask which route you are flying?

Quote from Jet-Pack (IPACS)

Is this issue isolated to the Q400 or are other aircraft affected too on this particular runway?

Unfortunately I don't have full control over what the route spits out, so I can't debug this. It might be an airport elevation error, perhaps the designers entered a wrong elevation for the airport? Then it should be an issue in all aircraft.

I carefully observed the vertical profile of the aircraft with autothrottle. One mile corresponds to about 300 feet high, and the one shown in Figure 1 is much lower than 300 feet.

Quote from Jet-Pack (IPACS)

Is this issue isolated to the Q400 or are other aircraft affected too on this particular runway?

Unfortunately I don't have full control over what the route spits out, so I can't debug this. It might be an airport elevation error, perhaps the designers entered a wrong elevation for the airport? Then it should be an issue in all aircraft.

I feel it should be a problem with the aircraft, because the crj900 will also have this problem, and there are also aircraft with auto-throttle, but the chance is very small!

When flying DASH8-400, using vertical navigation, there are two situations: either you can land on the runway accurately, or you can land like the first picture, and the errors are almost the same. Is it an error in the system algorithm?

I would like to ask, when I sometimes fly the same route and turn on VNAV, why can an aircraft with autothrottle accurately guide the aircraft to land, but something like the Q400 cannot land well on the runway in the end?

There is a question that has always puzzled me. Why does the A380 have more codes than the A320, but the system depth is far less than that of the A320?

Quote from Jet-Pack (IPACS)

Hi Steve,

the texture animation basically copies a rectangle section from one source texture to the target texture. The rectangles for the source and target are specified as scaled UV coordinates. For the scale we typically use 1024 or 2048, this means the ...Size and ...Position can be interpreted as pixels.

In your example we copy a rectangle section with the lower left corner at x=0 and y = 896px (measured from the lower left corner of the source texture) and a height of 64px and a width of 96px from the source texture to the target texture position. The target texture is defined in the texture_animation which we usually call "DisplayTexture. In the "RenderList" for that target texture all the .Render draw calls are executed one after the other and each of the different displays draws either its texture animation or custom draw code like for the glass cockpits displays.

When the source is a texture with numbers on it you can iterate through several positions and sample the source texture depending on the input. The offset between the numbers is the stride, there is a stride for the source and target. SourceStride means how far did you space the numbers on your source texture and TargetStride defines how far they should be placed on the target texture.

The integer DotPosition is the number you have to multiply the stride with to get to the pixel coordinates of the decimal dot on the texture.

The TargetDotOffset shifts the dot on the target texture left and right.

TargetDecimalStride defines the gap of the decimal dot

Regarding your texture converting issue: as far as I know you can assign the display source texture to a cube or some other blank object and it should convert just fine, even though your cube or canvas will not be used as a geometry in the tmd file. You could also temporarily assign it to some material to get it to convert.

Display More

Answer, I would like to ask is it because of modifying these codes that the resolution of the text on the cockpit display of aerofly has been significantly improved starting from 2022?

Quote from Jet-Pack (IPACS)

为了截取垂直轮廓，轮廓必须是下降段。但该路线确实显示了一个可能不正确的水平。

I don't quite understand. Can you explain it in more detail?

Quote from racing147

There is no introduction about crj vertical navigation in the official website,but I found that when I came to the TD point during the flight and used FMS as thenavigation source,when I lowered the altitude to the altitude of the landing airport,after pressing the APPR button,the screen VAPTH will appear, vnav should have been intercepted at this time,and then the aircraft will automatically control the pitch angle!But I don't understand why the vnav cannot be intercepted sometimes when the aircraft is on the correct vertical profile?

When the aircraft is in a vertical profile, sometimes the vnav can intercept at around 40nm, sometimes at 25nm, or 15nm, or sometimes there is no response at all. I don't understand what is wrong!

There is no introduction about crj vertical navigation in the official website,but I found that when I came to the TD point during the flight and used FMS as thenavigation source,when I lowered the altitude to the altitude of the landing airport,after pressing the APPR button,the screen VAPTH will appear, vnav should have been intercepted at this time,and then the aircraft will automatically control the pitch angle!But I don't understand why the vnav cannot be intercepted sometimes when the aircraft is on the correct vertical profile?