Beagle Pup Development [crossposted]

[sanhozay]

Let there be light ... unless you aren't using ALS.

You might want to update again -- there's a dialog for the autopilot, and ALS procedural lights, plus some improvements to the cockpit for night flying.

[IAHM-COL]

This is awesome! Thanks for so much great work G-SHOZ
Rolling my NDB tracking tests right now. Wish me straight

IH-COL

Note: It is noon, so I just falsified time for a minute to take the screenshot above.

[sanhozay]

Pushed a change with a new dialog with quick access to all lights, plus slider to control cockpit brightness. It is on the menu (Beagle Pup ~ Lights)

[sanhozay]

@IH-COL: I've pushed what will probably be the last changes before your tour flight:

1. Fuel gauge: Note that this shows one tank only. Eventually it will have a switch to switch to show left/right tank but at the moment it's just a guide to your overall fuel level.

2. Several temperature gauges that you can safely ignore.

3. Updated EGT gauge: Usual method applies, i.e. 75*F rich of peak EGT, and this should come out near the asterisk on the gauge.

4. Flap indicator: next to the autopilot control unit. This will eventually sit on the centre pedestal but I've stuck it here for now. Vfe is 100kts.

On the exterior, the wheels now turn but I ran into difficulties with the scissors on the nose gear. Don't worry if it looks like it's falling apart.

[IAHM-COL]

Thanks G-SHOZ
I rebased and updated FGMEMBERS'
The Beagle is way more mature of an aircraft I've ever dreamt of

Thanks for all the updates these last weeks.

IH-COL

[sanhozay]

I polished it



Reflection shader requires View - Rendering Options - Shader Effects - Performance set to 1 or more. Or you can control it through Shader Effects - Custom Settings - Model set to something other than minimum.

Gear scissors are also fixed and, to my surprise, rotating the wheels to get the gear compression was quite simple. You'll see what I mean when you fly it -- watch the wheels angle inward and outward.

[IAHM-COL]

OK. I wonder if the C337 exhibits the same problem for you, given that it uses the exact same code for the DME?

If it does, and if you have time, and it bothers you enough, you could try adding print statements inside the constructor in:

https://github.com/FGMEMBERS/Beagle-Pup ... /KN62A.nas

So, between lines 60 and 106, every few lines, add print statements with different letters, so like this:

Code: Select all

print("A");
... some code here
print("B");

Then watch the output in your console and see which step takes the time.

Hi Sanhozay

Here is the debug code I tested with and the report of where the code lags

https://github.com/FGMEMBERS/Beagle-Pup/commit/f918cf0e5ccb6a27447450f9135009e46296e9b1

[sanhozay]

Good job! It looks like this library function is causing the delay:

http://wiki.flightgear.org/Nasal_librar ... ange.28.29

If you open up a Nasal console in Flightgear, go to one of the windows and try this:

Code: Select all

print("Finding airports ...");
findAirportsWithinRange(60);
print("Found airports");

I suspect it will produce the delay you see in the C337 and Pup. The question is whether this is a quirk of using Terrafs. You might try smaller numbers for the range and see how it affects the time taken.

(The reason you removed the delay by removing the DME is that you created Nasal errors that stopped the transponder loading. In the Pup, if you delete the line that has KT76A.new on it (the transponder), the delay probably goes away without breaking the DME).

[IAHM-COL]

yes. It does produce the delay. I tried 60 first, it takes a while to print "Found"
Then it will be almost immediate to find Airports within the same or any smaller range lookup. But if I increase the range, then it will delay again.

I agree with you, the fact that the Airport directory gets transferred all (as oppose to be already available via terrafs) seems to be the culprit of the lag.

I wonder whether launching again (after loading once) will be a more fast launching, or whether it releases VFS and needs to "find" airports again.

You are correct; if I disconnect the transponder, it launches just fine (fast)

[IAHM-COL]

I wonder whether launching again (after loading once) will be a more fast launching, or whether it releases VFS and needs to "find" airports again.

No. It lags again, after closing and relaunching