Activity for Sascha
-
Sascha posted a comment on ticket #2801
Ooops, sorry, thats my fault. xDraconian is correct. This 0 values are default inputs if no other input condition is meet. So they should defined as <input>0</input>. I updated my git-repo. Please test and merge into FG if all is fine.
-
Thats right, because the C172p in next (2020.4) use the new KAP 140 that Josh and i build from scratch. The old one in 2020.3.x is crap. It has never worked as it should. So this bug report relates definitive to the old KAP 140. (Maybe we should ship a new point release of FG with a newer C172p ?)
-
For some hours we had a discussion on Discord about this problem and Jonathan pointed us to this patch: https://sourceforge.net/p/flightgear/simgear/ci/7ac90850d3b8adc613fb07acaad7b6aaee0844d4/ I reverted the changed manually in the code and compiled a second time. So, i can confirm that this patch breaks the animations. But as i reverted the changes line by line i saw that this patch introduce the 'offset' to the animation and especially this line jump in my eyes: offset = axisSegment->getStart()...
-
Looks like some effects have problems with transparent objects. In the Citation II every instrument has a glass with the effect 'model-transparent'. Depenting on the view angle, some objects behind the glass (digits and stripes) vanish. In this shot, the view is close to perpendicular to the engine panel and all is visible. http://lepanto.at/download/flightgear/screenshots/fgfs-20211209180718.png In this two shots i turned the view and the digits and/or the stripes vanish. Also one digit on the VNCC...
-
DHC6 Twin Otter (stable - 2020.3)
-
DHC6 Twin Otter (trunk - 2020.4)
-
DHC6 Twin Otter (trunk - 2020.4)
-
DHC6 Twin Otter (stable - 2020.3)
-
DHC6 Twin Otter (stable - 2020.3)
-
DHC6 Twin Otter
-
Now i had a little bit more time. The C172p uses two of the Bendix/King KX-165. This device combine comm and nav radio in one device. First you need a filter that feed the actual voltage to: systems/electrical/outputs/comm-nav[0] for the first radio and systems/electrical/outputs/comm-nav[1] for the second. To manage that both parts are controlable via one CB, set the <power-supply> for comm and nav to the same property and the same minimum voltage. <comm-radio> <name>comm</name> <number>0</number>...
-
Now i had a little bit more time. The C172p uses two of the Bendix/King KX-165. This device compine comm and nav radio in one device. First you need a filter that feed the actual voltage to: systems/electrical/outputs/comm-nav[0] for the first radio and systems/electrical/outputs/comm-nav[1] for the second. To manage that both parts are controlable via one CB, set the <power-supply> for comm and nav to the same property and the same minimum voltage. <comm-radio> <name>comm</name> <number>0</number>...
-
Now i had a little bit more time. The C172p uses two of the Bendix/King K165. This device compine comm and nav radio in one device. First you need a filter that feed the actual voltage to: systems/electrical/outputs/comm-nav[0] for the first radio and systems/electrical/outputs/comm-nav[1] for the second. To manage that both parts are controlable via one CB, set the <power-supply> for comm and nav to the same property and the same minimum voltage. <comm-radio> <name>comm</name> <number>0</number>...
-
As i mentioned on the dev-list, i spotted this bug 2 years ago and it was fixed allready. The problem is, that the most (or all) electrical instruments check the power property but without the index. If you have nav[0], nav[1] and nav[2], all radios checks /systems/electrical/outputs/nav. If this property falls below 1, all nav-radios turn 'serviceable' to 'false'. To fix it, most instruments received a new setting. Open the file 'c172p/Systems/instrumentation.xml'. Change the entry for the nav-radio...
-
added: key binding for KAP140 disconnect
-
added: key binding for KAP140 disconnect
-
fixed: KAP140 disengagement via ap-disc
-
fixed: KAP140 disengagement via ap-disc
-
I dont have commit access to FG (i think, normally i do aircrafts). I have the patches local compiled in and it works fine. Can i download the latest apt.dat from X-Plane somewhere to test?
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.4.2]
-
Here are all other redio stations found in Austria: LOWG 55 11930 APP 54 11820 TOWER 51 12150 EMERGENCY 1055 119300 APP 1055 120440 APP 1054 118200 TOWER 1050 126130 ATIS 1051 121500 EMERGENCY LOWI 55 11927 APP 54 12010 TOWER 51 12150 EMERGENCY 1055 119275 APP 1054 120100 TOWER 1050 126030 ATIS 1051 121500 EMERGENCY LOWK 55 12682 APP 54 11810 TOWER 51 12150 EMERGENCY 1055 126825 APP 1054 118100 TOWER 1050 126330 ATIS 1051 121500 EMERGENCY LOWL 55 12962 APP 54 11880 TOWER 51 12150 EMERGENCY 1055 129625...
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.4.1]
-
You can find wrong frequencies with: zgrep -n '^5[0-6] 1[1-3][0-9][0-9][1,3,4,6,8,9]' apt.dat.gz To skip invalid frequencies, we can do this in '/src/Airports/apt_loader.cxx': // short int representing tens of kHz, or just kHz directly int freqKhz = std::stoi(token[1]) * (isAPT1000Code ? 1 : 10); if (!isAPT1000Code) { int reminder = freqKhz % 100; if (reminder == 20 || reminder == 70) freqKhz += 5; if (freqKhz % 25) { SG_LOG( SG_GENERAL, SG_ALERT, aptDat << ":" << lineNum << ": skipping invalid 25...
-
You can find wrong frequencies with: zgrep -n '^5[0-6] 1[1-3][0-9][0-9][1,3,4,6,8,9]' apt.dat.gz To skip invalid frequencies, we can do this in '/src/Airports/apt_loader.cxx': // short int representing tens of kHz, or just kHz directly int freqKhz = std::stoi(token[1]) * (isAPT1000Code ? 1 : 10); if (!isAPT1000Code) { int reminder = freqKhz % 100; if (reminder == 20 || reminder == 70) freqKhz += 5; if (freqKhz % 25) { SG_LOG( SG_GENERAL, SG_ALERT, aptDat << ":" << lineNum << ": skipping invalid 25...
-
Piper PA28-161 Warrior II
-
Piper PA28-161 Warrior II
-
Found 131 invalid frequencies in our apt.dat. To handle this i changed '/src/Airports/apt_loader.cxx' a second time. File '/src/Airports/apt_loader.cxx' (line 825): // short int representing tens of kHz, or just kHz directly int freqKhz = std::stoi(token[1]) * (isAPT1000Code ? 1 : 10); changed to: // short int representing tens of kHz, or just kHz directly int freqKhz = std::stoi(token[1]); if (!isAPT1000Code) { int lastDigit = freqKhz % 10; freqKhz *= 10; if(freqKhz % 50) { if (lastDigit == 1 ||...
-
hold on! The radios set the correct frequency, but i dont hear ATIS. There must be another place where the code checks if there is a station on that frequency. I'm currently searching where the code search for the nearest station on that freq. Any hint?
-
Had now hacked a bit in the source code. The frequencies will be pulled from the navdata.cache and the frequencies are already wrong in there. So i changed the function that read the apt.dat to fill the navdata.cache and fixed the frequency there. in the file '/src/Airports/apt_loader.cxx' (line 825): // short int representing tens of kHz, or just kHz directly int freqKhz = std::stoi(token[1]) * (isAPT1000Code ? 1 : 10); changed to: // short int representing tens of kHz, or just kHz directly int...
-
Piper PA28-161 Warrior II
-
More and more user tumble over this bug. For me its clear that the problem came from the apt.dat file. We actually support the version 1000 of apt.dat and this version also define the frequencies as MHz × 100 (like the old spec). So 126.125 will be saved as '12612'. The spec clearly define 'round down'. This shows also that Xplane cant actually support 8.333kHz spacing. I dont know if its difficult to change, but i think the code should check if it is a valid frequency. As example 126.15 becomes...
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.12]
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.11]
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.10]
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.9]
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.8]
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.7]
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.6]
-
Problem is aircraft.livery.init is Nasal/effects.nas (line 6). I changed it to: ## Livery select var model_path = getprop("sim/aircraft"); var model_name = ""; for (var i = size(model_path); i >= 0; i -= 1) { var char = substr(model_path, i, 1); if (char == "/" or char == ".") break; model_name = char ~ model_name; } aircraft.livery.init("Models/Liveries/" ~ model_name); This build the pathname correctly.
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.5]
-
airport lights
-
Sorry, my fault. Found the error inside my local files.
-
airport lights
-
Bug is back, but only for the rabbit. All other lights are working normal. I dont know when it comes back, but it is there in 2020.3.1.
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.3]
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.2]
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.1]
-
Cessna 550 Citation II | 551 Citation II/SP | Citation II Sierra [4.4.0]
-
Ryan Navion / Super Navion 260 [0.4.6]
-
Ryan Navion / Super Navion 260 [0.4.5]
-
Ryan Navion / Super Navion 260 [0.4.4]
-
Ryan Navion / Super Navion 260 [0.4.3]
-
Ryan Navion / Super Navion 260 [0.4.2]
-
Ryan Navion / Super Navion 260 [0.4.1]
-
Ryan Navion / Super Navion 260 [0.4.0]
-
Ryan Navion / Super Navion 260 [0.3.9]
-
Cessna Citation II (550) | Citation II/SP (551) | Citation Super II (550-SUPER) [4.2.10]
-
Cessna Citation II (550) | Citation II/SP (551) | Citation Super II (550-SUPER) [4.2.9]
-
Cessna Citation II (550) | Citation II/SP (551) | Citation Super II (550-SUPER) [4.2.8]
-
Cessna Citation II (550) | Citation II/SP (551) | Citation Super II (550-SUPER) [4.2.7]
-
Cessna Citation II (550) | Citation II/SP (551) | Citation Super II (550-SUPER) [4.2.4]
-
Cessna Citation II (550) | Citation II/SP (551) | Citation Super II (550-SUPER) [4.2.3]
-
Cessna Citation II (550) | Citation II/SP (551) | Citation Super II (550-SUPER) [4.2.2]
-
Cessna Citation II (550) | Citation II/SP (551) | Citation Super II (550-SUPER) [4.2.1]
-
airport lights
-
Cessna Citation II (550) | Citation II/SP (551) | Citation Super II (550-SUPER) [4.1.21]
-
Ryan Navion / Super Navion 260 [0.3.8]
-
Ryan Navion / Super Navion 260 [0.3.7]
-
Ryan Navion / Super Navion 260 [0.3.7]
-
Ryan Navion / Super Navion 260 [0.3.6]
-
Ryan Navion / Super Navion 260 [0.3.6]
-
Ryan Navion / Super Navion 260 [0.3.5]
-
Ryan Navion / Super Navion 260 [0.3.5]
-
Ryan Navion / Super Navion 260 [0.3.4]
-
Ryan-Navion [0.3.3]
-
airport lights
-
Have now tested on 2016.4.4 and on this version, all renderer take care of the normals. The sequenced flasher and pulsing lights (yellow pulse on holding lines) are visible with all renderer, if you turn off 'Use point sprites for runway lights'. If this option is turned on, ALS doesn't show the animated lights. Pictures (taken from 2016.4.4 on LOWW rwy 16): http://www.lepanto.at/download/flightgear/Lights/Dep-Default-nops.png http://www.lepanto.at/download/flightgear/Lights/Dep-Default-ps.png http://www.lepanto.at/download/flightgear/Lights/App-Default-nops.png...
-
Ryan-Navion [0.3.2]
-
Ryan-Navion [0.3.2]
-
Ryan-Navion [0.3.1]
-
airport lights
-
Aermacchi-MB-339
-
VOTE: flightgear
-
Cessna 550/551 Citation II/SP / Sierra Super II [4.1.19]
-
Cessna 550/551 Citation II/SP / Sierra Super II [4.1.18]
-
Cessna 550/551 Citation II/SP / Sierra Super II [4.1.17]
-
Citation II / Sierra Super II [4.1.16]
-
Citation II / Sierra Super II
-
Citation II / Sierra Super II
-
* corrected cockpit position (yasim)
-
* extracted and remodeled enginepanel from flightdeck
-
* remodeled AP panel
-
* remodel radio altimeter
-
Citation 4.1.10: overhaul two panels
1
