Using latest SU9 BETA Update, I have Lost Nosewheel steering ( Via rudder
pedals) these were working On previously built models It would appear that
earlier models (Not built under Latest SU9) Still work without issue This was
first noticed on The SU9 Update Of April 14th (Subsequently Patched same day)
the ONLY changes made to flight_model (Contact points) have been for
Compression and height on MAIN GEAR and No changes to Nose Gear (see below) **
[CONTACT_POINTS]** static_pitch =0 static_cg_height =6.35
gear_system_type=0 tailwheel_lock =0 max_number_of_points =10
gear_locked_on_ground =0 gear_locked_above_speed =-1
max_speed_full_steering =13 max_speed_decreasing_steering =20
min_available_steering_angle_pct =0.2 max_speed_full_steering_castering
=25 max_speed_decreasing_steering_castering =40 min_castering_angle
=0.05236 max_castering_angle =3.141593 point.0 = 1, 20.5, 0.00, -6.0,
2000, 0, 1, 75, 0.4, 1.7, 0.8, 0.0, 0.0, 0.0, 0.0, 0.0, 1 point.1 = 1,
-3.5, -6.4, -6.6, 2200, 1, 1, 0.0, 0.489, 1.5, 0.75, 0, 0, 2, 0, 0, 1
point.2 = 1, -3.5, -5.4, -6.6, 2200, 1, 1, 0.0, 0.489, 1.5, 0.75, 0, 0, 2,
0, 0, 1 point.3 = 1, -3.5, 5.4, -6.6, 2200, 2, 1, 0.0, 0.489, 1.5, 0.75,
0, 0, 3, 0, 0, 1 point.4 = 1, -3.5, 6.4, -6.6, 2200, 2, 1, 0.0, 0.489,
1.5, 0.75, 0, 0, 3, 0, 0, 1 point.5= 2, -3.3, -25.5, 1.5, 800, 0, 0, 0, 0,
0, 0, 0, 0, 5, 0, 0, 1 point.6= 2, -3.3, 25.5, 1.5, 800, 0, 0, 0, 0, 0, 0,
0, 0, 6, 0, 0, 1 point.7= 2, -20.55, 0, -1.4, 800, 0, 0, 0, 0, 0, 0, 0, 0,
9, 0, 0, 1 point.8= 2, 5.75, 0, -4.1, 800, 0, 0, 0, 0, 0, 0, 0, 0, 4, 0,
0, 1 point.9= 3, -15.0, 0.0, -5.90, 2200, 0, 0, 0, 0, 0, 0, 3, 3, 5, 0, 0,
1 steering_time_constants= 3, 5 emergency_extension_type=1
hyd_need_power_to_function=0 SIM version - 1.25.7 (BETA) And latest 0.18
SDK Tools
Hello @ModelMuncher What’s the wheel debug
view saying? Is the steering angle changing? Do you have weight on the nose
wheel? Regards, Sylvain
Wheels debug shows all good params apart from ZERO STEERING Ample weight on
Nosewheel … Simvars.exe is showing me ZERO Change in A:GEAR CENTER STEER
ANGLE *This Var has previously been used without issue and is still active on
our BN2 edited- spurious information removed - See below BN2 Model compiled
under SU8 shows active movement in both A:GEAR CENTER STEER ANGLE and A:GEAR
STEER ANGLE using IDENTICAL Copy and PASTE XML Code Is this indicating the Var
has been deprecated?
PLEASE HELP WITH THIS ! I am pulling my hair out ( And I don’t have much left
) Project#1 built with 3dsMax 2018 and Output via Babylon exporter Built via
SU9 Beta / Used on SU9 BETA = Nosewheel steering ( AND Var ) Fails Built via
SU9 Beta / Used on SU8 RETAIL = Nosewheel steering ( AND Var ) OPERATIONAL
Built via SU8 RETAIL / Used on SU8 RETAIL = Nosewheel steering ( AND Var )
OPERATIONAL Built via SU8 RETAIL / Used on SU9 BETA = Nosewheel steering ( AND
Var ) Fails Project#2 built with 3dsMax 2018 and Output via Babylon exporter
Built via SU9 Beta / Used on SU9 BETA = Nosewheel steering ( AND Var )
OPERATIONAL Built via SU9 Beta / Used on SU8 RETAIL = Nosewheel steering ( AND
Var ) OPERATIONAL Built via SU8 RETAIL / Used on SU8 RETAIL = Nosewheel
steering ( AND Var ) OPERATIONAL Built via SU8 RETAIL / Used on SU9 BETA =
Nosewheel steering ( AND Var ) OPERATIONAL XML Animation code For nosewheel
steering Copied and Pasted from Project#1 to Project#2 Contact points,
Systems.cfg etc, checked and triple checked - NO errors or major differences
You will need to provide the sample projects to Asobo, very little we can do
to help you with without having the projects to troubleshoot. All I can think
of, is, some .cfg file parameter is causing this with SU9. Most EU is now in
easter break, so you might only hear back from Asobo by Tuesday. Best, Raul
Ok… it would seem I fixed this Irritating issue After a LOT of hair loss and
Stress 
I discovered that SU9 Beta contains an entry I haven’t seen before
in the FLT Files [Controls.0] section called NosewheelLock= I have set
this to NosewheelLock=0 and this seems to allow the animation and steering
again HOWEVER !! It appears as if the default, if the NosewheelLock is
omitted is LOCKED ! or NosewheelLock=1 Sureley this should be NosewheelLock=0
Hello @ModelMuncher The default value is 0 for
this parameter so I’m not sure what’s happening here. Tested with the Da62 SDK
sample, that is missing this parameter in its FLT files as well. When creating
a flight from the world map, the created CustomFlight.FLT contains a
NosewheelLock=0. Also tested with some custom Asobo mission and the
nosewheel ends up unlocked when that param is not defined in the FLT file as
well. With what FLT file are you seeing the problem? If you send me your
package, I can have a look at what’s setting it to true. Regards, Sylvain
This occurred only when there was no FLT File in the aircrafts folder
Tested this case with the Da62 as well and still can’t repro. There must be
something else.
Same issue for me. Since SU9 Nose steering became disabled.
Open your FLT File (s) … Whatever the line in [Controls.0] section states
NosewheelLock=“N” It should Say ( 0 or 1 ) change it to the opposite If
the entry is not there then add the line in NosewheelLock=0 Hope this
helps ?
@luklew Not sure I follow you here. Are you talking
about this aircraft?
meant it just has ground steering issue? Definitely not a nosewheel issue
though.
Thanks for that. Does it matter which FLT file I put it in? I tried putting it
into CustomFlight.flt but my nosewheel still doesn’t seem to work. Thanks!
Ah sorry, ignore the last bit. Mainly just issues with nose gear since SU9 for
me
I would assume its the FLT your going to use ? Firstly those found in the
aircraft folder of the aircraft with the issue apron.flt if thats where your
starting runway.flt if you start on runway etc etc
I would like to raise this to a BUG If a FLT File contains the line
NosewheelLock=0 then the Nosewheel is of course NO T locked If a FLT
File contains the line NosewheelLock=1 The the nosewheel IS Logically
locked IF a FLT contains NO NosewheelLock= Entry then the noswheel
steering is LOCKED by Default causing a lack of steering on the runway if
the Sim is Started in flight (cruise.flt, approach.flt etc) may I suggest that
this default should be UNLOCKED
OK More observations … I think this will lead us to a fix … IF the flight is
started IN THE AIR and the selected aircraft folder contains NONE of the
following Approach.flt cruise.flt final.flt Then I THINK the sim loads up
a default flt from somewhere Internally This Default.FLT May have
NosewheelLock=1 assigned causing the Aircraft to be Unsteerable on ground I
have now added the three Offending FLT Files that now contain NosewheelLock=0
and all is well upon landing
What aircraft are you testing with? Once again, I tried doing as you described
with the SDK Da62 but always end up with NosewheelLock set to false.
this is with our latest Trislander
I tried to repro as well using the trislander but without success. No matter
what, I always have the Nosewheel unlocked. I have an old version of your
package. Maybe something you changed in the meantime changed this behaviour.