legoboyvdlp wrote in Thu Jan 15, 2015 4:49 pm:So, tried autostart, waited five minutes, the props spun, but nothing. The oil pressure light is on. How can I pump up oil pressure?
naplesAPF wrote in Thu Jan 15, 2015 7:46 pm:Watched your long range nav vid. Its a great lesson. Guess I have to study up A Lot more before I can do this correctly.
Thanks for changing the fuel on/off to j and k keys, this helped me and now can start easily and quickly and don't even need autostart.
Also I know this is a minor thing but can't get the livery select to work to select different liveries. If you have time to check this, great, otherwise don't worry about it.
Thanks again, this is a really great plane and your work has just improved it.
abassign wrote in Fri Jan 23, 2015 11:14 pm:
A little consideration:
I think it would be better to have the Garmin with an option from the menu, it's really nice to fly with this airplane in the vintage configuration and in that case the Garmin is not nice to see ...
Beautiful work!
abassign wrote in Fri Jan 23, 2015 11:14 pm:Is nice, but there is a problem with Garmin When I switch oh and press enter, start to display the map, but the frame rate immediately reduce (from 20 fps to 7-9 fps) end when the map is refreshed the program stop a moment... I not remember this problem, with DR400 ! My FGFS is 3.5 ... If I do stop the Garmin, immediately the program goes ok.
I try to activate, in the file preferences.xml, the multithreading option:
<multithreading-mode>AutomaticSelection</multithreading-mode>
But the problem remain
I try with DR400 and I found the identical problem...
With Rembrandt or without the problem is identical...
I think the problem is related between Garmin and 3.5 FGFS but is not clear.
A little consideration:
I think it would be better to have the Garmin with an option from the menu, it's really nice to fly with this airplane in the vintage configuration and in that case the Garmin is not nice to see ...
Beautiful work!
<checkbox>
<halign>left</halign>
<label>Advanced avionics</label>
<property>sim/model/show-hide-advanced-avionics</property>
<binding>
<command>dialog-apply</command>
</binding>
</checkbox>
<model>
<path>Aircraft/Instruments-3d/garmin196/garmin196.xml</path>
<offsets>
<x-m>-3.89</x-m>
<y-m>-0.14</y-m>
<z-m>0.7</z-m>
</offsets>
<condition>
<property>sim/model/show-hide-advanced-avionics</property>
</condition>
</model>
abassign wrote in Sat Jan 24, 2015 2:35 pm:
For the performance problem I notice this:
When the aircraft is stationary on the runway, the coordinates displayed by Garmin (and therefore also the map) change in a very marked mode, this could be the reason of slowing down the system, due to the need to reload the data that normally should not be recharged and calculated. So the problem may be related to interfacing with reading of the coordinate system inserted in the property-tree.
Patten wrote in Sat Jan 24, 2015 1:13 pm:My hangar is updated with the Twin Otter DHC6-300 with which I fly:
Some screens shots and more...
http://pattenflightgear.wifeo.com/dhc6- ... -otter.php
lambo64, thanks for your paint kit, no-smoking box is textured .
<!--
<file>Aircraft/dhc6/Nasal/failures.nas</file>
-->
lanbo64 wrote in Sat Jan 24, 2015 11:01 pm:Thank you so much, I am happy you like it.
I have tried your build. I completely understand that you may not like something such as engines failures . Forcing to turn on intake deflectors and heaters is not a good solution, because they will downgrade the engines.
Here is my suggestion:
By preventing from engines failures, you can mark (or delete) the following lines from dhc6-base.xml:
- Code: Select all
<!--
<file>Aircraft/dhc6/Nasal/failures.nas</file>
-->
Bo
Users browsing this forum: No registered users and 6 guests