@LoneSpaceGaming
Hi LoneSpaceGaming. Your math is right.
Normally, as a rule, climbing and descending is performed at 80 mph (70 kts) on both the C-172 and the C-150.
@SOP
I saw the video: only the name of the destination changes but everything else is blocked. As if the activators were missing in the variable "Lat", "Long" and "Alt".
For example: <Setter variable = "Lat" function = "128879" priority = "0" activator = "LCode = 0" />
If the activators are in place, right now I can't tell you what the problem could be,
@SOP
If you copied the variables it should work.
The label of the cursor ⌂ on the directional has this text:
<rotate={-deltaangle(Heading,Hdng)}><pos={sin(deltaangle(Heading,Hdng))}><voffset={cos(deltaangle(Heading,Hdng))}>⌂
The two labels of the ILS lines are on the attitude indicator.
@Default4
it may be that the striped labels above the flaps and stabilizers weigh down the frame rate.
Delete them, and try if it gets better.
I have tried now.
@L0RR3B0RR3
+3Yours is a magnificent 104A, and just seeing it that I came up with the idea of making an S version.
@Krikkit42
+2Yes, the panel drops the frame rate. I could do a light version, without too many details.
@CorporalWojak
+1Using AG3 the throttle lever remains limited to the only power necessary for taxiing.
@MrCOPTY
+1Good. I am glad it is useful to you.
@SyntheticL
+1Synthetic, thank you.
@PlaneFlightX
+1No, I don't have Discord.
@PlaneFlightX
+1Thank you. Of course you can use it in your new SWL-120.
@WNP78
+1Thanks, now I understand where the problem was. Very helpful.
@Kennneth
+1In fact it would take a way to simulate the BLC (Boundary Layer Control).
I guess it's not easy to do!
@COMAC919
Have you copied the data from the variables section correctly?
Without <variables> it can't work.
@COMAC919
Hi COMAC919, of course, you can use it.
@LoneSpaceGaming
Hi LoneSpaceGaming. Your math is right.
Normally, as a rule, climbing and descending is performed at 80 mph (70 kts) on both the C-172 and the C-150.
@Cocomax400
I could try! ;)
@Aerozack
the stopwatch should start.
@Aerozack
Let's just say I enjoyed doing it.
@HololiveFan
It's ok for me. Good.
@ThePIanePerson
At the moment I have nothing in the pipeline. I'm waiting for inspiration to come back, probably in a month or so.
@JacksEpicGamingYT
Yes of course. Good idea.
@Unablegameing
Many thanks for the information, I'll take that into account.
@Unablegameing
You entice me, the lookheed electra L-188 (if that's the plane you indicate) has always fascinated me.
@Jedediah
CAAC livery? Good idea.
@SOP
I saw the video: only the name of the destination changes but everything else is blocked. As if the activators were missing in the variable "Lat", "Long" and "Alt".
For example: <Setter variable = "Lat" function = "128879" priority = "0" activator = "LCode = 0" />
If the activators are in place, right now I can't tell you what the problem could be,
@SOP
If you copied the variables it should work.
The label of the cursor ⌂ on the directional has this text:
<rotate={-deltaangle(Heading,Hdng)}><pos={sin(deltaangle(Heading,Hdng))}><voffset={cos(deltaangle(Heading,Hdng))}>⌂
The two labels of the ILS lines are on the attitude indicator.
@indonesia87
If you feel like doing it, great.
edit: Oh. I saw now that you have already done it, well.
@jamesPLANESii
I will gladly do it. 1600 parts? No problem.
@Walvis
Walvis, thank you. You can take everything that could be useful.
@WNP78
Done. I have updated the xml.
(I set the controls to Disabled instead of 0 and I have
leveled the cameras).
@WNP78
I will try to update the xml. If I can, ok. If not, I'll let you know. Thank you.
@jamesPLANESii
you can take anything that will be useful to you. Your cessna have been among my favorites.
@Default4
it may be that the striped labels above the flaps and stabilizers weigh down the frame rate.
Delete them, and try if it gets better.
I have tried now.