Board index FlightGear Development Aircraft

dhc2 failure in 2018.3.2 and 2019.1.2

Questions and discussion about creating aircraft. Flight dynamics, 3d models, cockpits, systems, animation, textures.

dhc2 failure in 2018.3.2 and 2019.1.2

Postby dilbert » Thu Jan 23, 2020 1:47 pm

Have long enjoyed flying the dhc2, as it's well appointed and all features operated flawlessly-at least until to FlightGear was updated from 2018.2.2 to 2018.3.2.

When employed in 2018.3.2, 2019.1.2 in Windows or in 2019.2.0 in Ubuntu64, the plane spins endlessly at the end of the runway, when throttle is added.
It is obvious this was brought about by a change in the 2018.3.2 update. In the Ubuntu Terminal there now is an endless series of "ERROR: cannot add listener to tied property/controls" messages.

Syd Adams has not been active in a long time. Is there still a maintainer for the dh2?


P. S. I also had a problem with a legacy version of the F-14 (retained because radar, targeting, and weapons systems work extremely well).
In its case there was a failure in directional control. Since Richard is actively maintaining the F-14, this problem seems to have been resolved in its
current version, though I haven't tested radar and other systems.

Kind Regards
dilbert
 
Posts: 774
Joined: Wed Jan 07, 2015 9:36 pm
Location: KJKA, Alabama, USA
Callsign: db1
Version: 220.3.19
OS: W10,Ubuntu64

Re: dhc2 failure in 2018.3.2 and 2019.1.2

Postby AndersG » Thu Jan 23, 2020 3:09 pm

dilbert wrote in Thu Jan 23, 2020 1:47 pm:It is obvious this was brought about by a change in the 2018.3.2 update. In the Ubuntu Terminal there now is an endless series of "ERROR: cannot add listener to tied property/controls" messages.


While this message is new the problem that caused it (adding a listener to a tied property) has been around forever but without a report, so I am very uncertain to connect it with your engine control problem.
Callsign: SE-AG
Aircraft (uhm...): Submarine Scout, Zeppelin NT, ZF Navy free balloon, Nordstern, Hindenburg, Short Empire flying-boat, ZNP-K, North Sea class, MTB T21 class, U.S.S. Monitor, MFI-9B, Type UB I submarine, Gokstad ship, Renault FT.
AndersG
 
Posts: 2524
Joined: Wed Nov 29, 2006 10:20 am
Location: Göteborg, Sweden
Callsign: SE-AG
OS: Debian GNU Linux

Re: dhc2 failure in 2018.3.2 and 2019.1.2

Postby Thorsten » Thu Jan 23, 2020 6:12 pm

It seems to be the same problem that has been reported on the mailing list by gallonf&z.

We lack information to follow up unfortunately - what causes the loss of control (as the Nasal warnings are harmless)?
Thorsten
 
Posts: 12490
Joined: Mon Nov 02, 2009 9:33 am

Re: dhc2 failure in 2018.3.2 and 2019.1.2

Postby Bjoern » Thu Jan 23, 2020 9:14 pm

What joystick are you using, if any?

This could be caused by the same bug that I've reported here: https://forum.flightgear.org/viewtopic.php?f=17&t=36797
Ticket on SourceForge: https://sourceforge.net/p/flightgear/codetickets/2185/
Previous mailing list discussion: https://sourceforge.net/p/flightgear/mailman/message/36892659/ (Click "View entire thread" to view all replies)
Current discussion: https://sourceforge.net/p/flightgear/mailman/message/36907426/


- Edit:
Edited link permitting accidential, easy, email address leakage.
Last edited by Bjoern on Thu Jan 23, 2020 10:15 pm, edited 1 time in total.
Bjoern
 
Posts: 484
Joined: Fri Jan 06, 2012 11:00 pm
Location: TXL (RIP)
Version: Next
OS: ArchLinux

Re: dhc2 failure in 2018.3.2 and 2019.1.2

Postby Lincoln » Thu Jan 23, 2020 10:09 pm

I wouldnt consider links that could leak emails to be a very nice move to make :wink:
Currently flying the 737-800YV / MD-11-GE / 747-400

GE90-115B for life!

Follow me to the sun on SXS98X!

LincolnWorks discord!
Lincoln
 
Posts: 128
Joined: Mon Jan 20, 2020 6:34 pm
Location: In the sky ofcourse or in The Netherlands
Callsign: ATC_Lcn/RM01/SXS98X

Re: dhc2 failure in 2018.3.2 and 2019.1.2

Postby Bjoern » Thu Jan 23, 2020 10:16 pm

Lincoln wrote in Thu Jan 23, 2020 10:09 pm:I wouldnt consider links that could leak emails to be a very nice move to make :wink:


Noted. I've edited the link to minimize that risk.
Bjoern
 
Posts: 484
Joined: Fri Jan 06, 2012 11:00 pm
Location: TXL (RIP)
Version: Next
OS: ArchLinux

Re: dhc2 failure in 2018.3.2 and 2019.1.2

Postby dilbert » Sat Jan 25, 2020 1:41 pm

Have since noted that differing failures occur in various JSBSim aircraft, which I ascribe to the fact various JSBSim aircraft employ different nasals and at various points in program execution. The one thing that's consistent is that errors are always nasal related; such as, for example, [ALERT]: nasal parse error: parse error in, line 1 [ALERT]: input Failed to execute command nasal.

It would appear that a modification to the executable in 2018.3.2 created some sort of nasal recognition and execution problem for some JSBSim planes. Pretty vague, at this point :(

Further, It does not appear related to changes in JSBSim; as I overwrote the JSBSim directory in 2018.3.2 with that of 2018.3.1, without making any difference.

Also, these comments wouldn't apply to the F-14, as I believe it's YASim, and probably a separate issue.

Still seeking an answer to the dnc2.

Thanks for the responses, and regards to all.
dilbert
 
Posts: 774
Joined: Wed Jan 07, 2015 9:36 pm
Location: KJKA, Alabama, USA
Callsign: db1
Version: 220.3.19
OS: W10,Ubuntu64

Re: dhc2 failure in 2018.3.2 and 2019.1.2

Postby dilbert » Sun Jan 26, 2020 4:42 pm

Well I solved my problem.

Surprised to find an old version of the dhc2 in one of my aircraft libraries works just fine in 2018.3.2 and 2019.1.2.

Odd, since am unaware of a current maintainer who might have effectuated a change in the add-on hangar version.

To restore usability of the dhc2 for the general membership recommend reverting the add-on hangar version from 20190827 to 20160103.

Will assume the deleterious 20190827 update was made with good intention. :)

Kind Regards to all. :D
dilbert
 
Posts: 774
Joined: Wed Jan 07, 2015 9:36 pm
Location: KJKA, Alabama, USA
Callsign: db1
Version: 220.3.19
OS: W10,Ubuntu64

Re: dhc2 failure in 2018.3.2 and 2019.1.2

Postby wlbragg » Sun Jan 26, 2020 7:50 pm

dilbert wrote in Sun Jan 26, 2020 4:42 pm:Will assume the deleterious 20190827 update was made with good intention. :)

Kind Regards to all. :D


I'm really afraid there is some co-mingling of potential bugs going on and it is getting carried away, in my opinion.

First, if you have a bug which is reproducible and correctable by reverting to a previous version of the aircraft, then that bug can be tracked down and understood.

This is not the same "serious" bug that is being search for currently on the mailing list.

The one thing that's consistent is that errors are always nasal related; such as, for example, [ALERT]: nasal parse error: parse error in, line 1 [ALERT]: input Failed to execute command nasal.

It would appear that a modification to the executable in 2018.3.2 created some sort of nasal recognition and execution problem for some JSBSim planes. Pretty vague, at this point

Again, reproducible = traceable and a distinct point in the code execution that can be investigated.

One further issue I have. I am running 2019.2 next and I have no issues with the current dhc2, so there is that as well?

Everyone needs to step back and "if possible" clearly identify the issue before making any assumptions.

I'm not admonishing anyone here, mearly noticing a trend I don't think is helpful.
Kansas and Ohio/Midwest scenery development.
KEQA, 3AU, KRCP Airport Layout
Intel i7/GeForce RTX 2070/Max-Q
User avatar
wlbragg
 
Posts: 7588
Joined: Sun Aug 26, 2012 12:31 am
Location: Kansas (Tornado Alley), USA
Callsign: WC2020
Version: next
OS: Win10/Linux/RTX 2070

Re: dhc2 failure in 2018.3.2 and 2019.1.2

Postby dilbert » Sun Jan 26, 2020 9:25 pm

Thanks. Not really a bug, as I had thought. What confused the issue between versions for me was the fact that in the earlier version, the tailwheel was locked in default at startup.
Latest version works fine. However, plane comes up sitting on the runway with parking brake set, but tailwheel unlocked; so the tailwheel needs to be locked by pressing "l" before releasing the parking brake and adding power. Otherwise you are quickly in a situation that neither rudder nor toe brakes can handle. Taxiing requires tailwheel being unlocked, use of toe brakes, and low engine rpm.

Sorry for any confusion caused by my earlier posts.

Thanks for the reply and best regards

I don't disagree with Bragg. I will say that I still haven't found a locking lever or tailwheel position indicator in the cockpit. So I was unaware that there was a change in the default position of the tailwheel that occurred between versions. You might say I should have used a checklist-granted. But how does one know whether it's locked or unlocked, other than guessing from its behavior, or seeing the wheel unlocked in rear view? Anyway,
thanks for your responses and help., and sorry for the bother. :oops:
dilbert
 
Posts: 774
Joined: Wed Jan 07, 2015 9:36 pm
Location: KJKA, Alabama, USA
Callsign: db1
Version: 220.3.19
OS: W10,Ubuntu64


Return to Aircraft

Who is online

Users browsing this forum: No registered users and 12 guests