Menu
▾
▴
1 Attachments
#266 bo105 cannot be started
Originally created by: aeitsch...@yahoo.de
Originally owned by: aeitsch...@yahoo.de
What steps will reproduce the problem?
1.use the latest GIT from today
2.select bo105
3.start the helicopter per Autostart or "}"-key
What is the expected output? What do you see instead?
I expect the heli-engine to start. Instead it won't start and a error message appears in the console.
Several other helicopters are affected as well
What version (or GIT date / Hudson build number)?
FGFS GIT Hudson win32 installer built 225
What operating system and graphics card?
win32 xp
DualCore 2,66 Ghz
4 GB RAM
Nvidia GeForce 460 GTX
Please use labels, text and attachments to provide additional information
(avoid expiring external links, e.g. imageshack, pastebin etc).
Related
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Does this happen with FG GIT or the 2.2.0 branch? If 2.2.0 isn't affected then it's not release blocker. Note that FG GIT already contains an FDM update which is currently causing trouble - but FG 2.2.0 isn't affected by these issues.
Also, this is not a Nasal issue. Nasal is just reporting the problem. There is an invalid numeric operation causing this - likely somewhere in the FG core/FDM.
Summary: bo105 cannot be started
Labels: Sim
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: aeitsch...@yahoo.de
FG GIT as written ("Hudson win32 installer built 225")
Our helicopters are using YASim, and so much as I know there wasn't any update(but I might be wrong)
Nasal isn't just reporting the problem- as the heliocpters needs heavy use of Nasal for simulating fuel-consume, engine simulation etc. there is something which prevent executing the nasal-script completly.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
The recent FDM/tank update also affects YASim.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: aeitsch...@yahoo.de
That's bad- if this is the cause it will affect 2.2.0 as well!
YASim helicopter doesn't have simulated engines like the YAsim-props or -jets.
They are faked per nasal- incl. fuel system
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
No, the FDM/tank update is only in FG/next. FG 2.2.0 was already branched weeks ago - and the FDM/tank update will definitely _not_ go into 2.2.0. So, if the tank update was the cause, then 2.2.0 isn't affected.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: aeitsch...@yahoo.de
I don't know which is the cause of this bug. I just see from time to time commits to the 2.2.0-branch in the log. And as I'm not able to compile 2.2.0-branch I can't test.
Anyway- with this bug I'm not able to go on my developement of my helicopters like the ec135 or ec130...:-(
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cumuluni... (code.google.com)@gmail.com
The tank update is causing the issue and that's only in next. It's not a blocker for 2.2.0.
I'll come up with a fix soon. I assume this bo105.nas has been copy 'n pasted over to other helicopters?
Status: Dev
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cumuluni... (code.google.com)@gmail.com
As a workaround, change the two lines in bo105-set.xml reading
<density-ppg type="double" write="n">6.682</density-ppg>
to
<density-ppg type="double">6.682</density-ppg>
This is _not_ a fix for the issue but gets you running again without a nasal-abort.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: aeitsch...@yahoo.de
Thanks so far!
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cumuluni... (code.google.com)@gmail.com
A fix is in SimGear. Please check against latest SimGear/FlightGear git. Don't forget to remove the workaround from comment #8.
Status: Testing
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: aeitsch...@yahoo.de
Works here for me!
If there is no disagree I will set the status to "fixed"
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
Confirmed to be fixed!
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: aeitsch...@yahoo.de
(No comment was entered for this change.)
Status: Fixed
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Temp
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Fixed