http://wiki.flightgear.org/Walk_view
clm76 wrote in Sun Feb 18, 2018 11:42 am:A little problem with the button "Flip": the ground is on the ceiling.
<Nasal runtime error: No such member: Control
at /input/keyboard/key[62]/binding, line 1
No such member: control:
at <canvas-repl>, line 1
Initializing addon 'Spoken GCA' version 0.3.6 from /..../addon-main.nas in __addon[org.flightgear.addons.SpokenGCA]__
GCA control 0.3.5 loaded
GCA tools loaded.
in the canvas-REPL Try gca.Control();yanes wrote in Wed Feb 21, 2018 11:22 pm:running gca.control(); ...
Not at all. Each addon is "standalone".yanes wrote in Wed Feb 21, 2018 11:22 pm:Is FGPlot & oscilloscope addons required for this in order to work properly ?
You are right, yanes: is my fault.yanes wrote in Thu Feb 22, 2018 10:40 pm:t seems to be loaded at startup , and UNLOADED due to a fatal error caused by failed lookup for the oscilloscope addon
rleibner wrote in Thu Feb 22, 2018 6:27 pm:I've just uploaded the new PAR addon and you can download it from here.
This addon will replace the current SpokenGCA. If all runs OK, there will be no reason to keep SpokenGCA into the repository.
if (size(err)) {
….
var gcaCtrl = nil;
var err = []; # new
var instrument = func(){ # Shows hidden screens (if any) or instanciate a new one.
….
Nasal runtime error: non-objects have no members
at /home/chris/fg2018_2/install/flightgear/fgdata/Nasal/canvas/gui/Widget.nas, line 125
That bug was fixed yesterday. Only par.nas changes, so you can update it fromclm76 wrote in Fri Feb 23, 2018 5:36 pm:1 – A nasal error occurs line 291 showing that the « err » variable is not define.
and also occurs when changing RWY.clm76 wrote in Fri Feb 23, 2018 5:36 pm:2 – A nasal error occurs when we change the final distance :
May be because there is not a 3deg slope anywhereclm76 wrote in Fri Feb 23, 2018 5:36 pm:4 - It seems that the 3 degree slope is not correct
drawCones: func(){
var mS = mSlope(me.profile, me.TerrainResolution); # as ft/nm
me.minSlope = math.atan2(mS,6076)*R2D; # 6076 ft = 1 nm
var xvec = [10, 0, 10];
var yvec = [10*mS, 0, 10*(mS+425)]; # 425 ft = tan(4°)
me.Vcone = me.xzGraph.polyline( xvec, yvec, white);
yvec = [10*math.tan(6*D2R), 0, -10*math.tan(6*D2R)];
me.Hcone = me.xyGraph.polyline( xvec, yvec, white);
me.Vcenter = me.xzGraph.line([0,0],[10,10*(mS+212)],red); # 212 ft = tan(2°)
me.Hcenter = me.xyGraph.line([0,0],[10,0],red);
},
That bug was fixed yesterday. Only par.nas changes, so you can update it from
A 'minimumSlope' is calculated according the terrain. (not always will be zero).
The 'maxSlope' = minimumSlope + 4 deg.
The normal 'glideSlope' = minimumSlope + 2 deg.
I know this may seem a bit arbitrary. For that reason (among others) my plan is to allow customizations using the "Set" button...
By the way, clm76: How beautiful and precise was your half-standard turn !!
To improve the terrain getVertProfilefunction when unloaded tiles are needed.
Users browsing this forum: No registered users and 3 guests