Printable View
Hello Rob,
1 Not yet, I hope to do that before releaseing B25
2 It should be corrected in B25
3 if you are 6 knots overspeed, the MW should ring. There should be an overspeed aural sound, but not yet modeled. I'll check all that maybe for B25.
I hope to release B25 in a couple weeks, after some holydays most welcomed ;-)
Cheers,
JL
Hello JL,
hm? Thats strange... I don't get any MW due to overspeed. All it does is disconnecting AP and rolling the AC back to level when it exceeds this margin, not allowing the AC to keep any bank with center stick. Maybe you can have a look.
...again some remarks:
1. I noticed that the target Mach speed can be set to Mach>10. I assume it should be limited to a certain value like you've done it with max altitude of 45kft... I have not checked the max. target speed in kts.
2. I guess the N/W steering should be blocked when hydraulics are off. And for some reason...the NW can be controlled by ailerons when the AC is taxing. I quickly checked my settings but could not find a double definition. Any idea?
3. gear extention shouldn't be possible in high speed
4. I think I mentioned it before: The flap position indicator should hide the white dots when the AC is in clean config.
5. Ensure that lateral flight path sections are always tagential at there connecting waypoints on ND. BTW: Is a shown arc dependent on speed?
6. and... thats just an idea for later enhancements... maybe you can add some sort of small randomizer to some of the values displayed on the SD. I think of a 3% margin of the actual value. So the SD displays are not ALWAYS so perfectly symetrical and allow small & REAL!! mismatches like in fuel consumption, vibration, electrical power... But thats just an idea for "nice to have".
I know there are 100 more issues which are more important ... like correct & reliable V-NAV and the corrected time estimations for all waypoint and arrival... and many more :) Well, its just an idea...
Thats it for now... JL, enjoy your holidays!
Cheers,
Rob
Hi Rob,
If there is no MW, then it's not implemented yet, I'll do it when I add the aural OVSPD warning.
Concerning your other remarks:
1. I noticed recently, will do something about it (next version if I don't forget)
2. hydraulics are not completely linked to the simulator yet. As for the N/W moving the ailerons, you most probably left the auto rudder feature in FS realism options. Note that it's not possible in FS to have a tiller axis which steers the N/W but not the rudder.
5. The arc is dependent on ground speed. It's not always tangential, but as you can probably guess, the maths is not easy to get accurately AND CPU efficient at the same time.
6. I have a lot of systems to improve on the SD, this will come at the same time.
I always appreciate inputs, so feel free to post them ;)
Cheers,
JL
Hi JL,
here are some more things I noticed:
1. spoilers on Fight Controls SD: the upward-arrows should be visible when each of the spoiler is defected by >2.5deg. So when you do a very smooth roll input, I assume you should see the spoilers coming up one after another... and I am not sure but I think only spoilers # 5 to #2 are affected by roll in normal law.
2. Speed brake extension is inhibited in following cases:
− SEC 1 and 3 fault
− Elevator L or R fault ( in this case only SPLR 3 &4 are inhibited )
− Angle of attack protection is active
− In FLAPS FULL configuration ( A319 A320 ) or FLAPS 3 position (A321)
If speed brakes are extended, they automatically retract and kept retracted until inhibition condition disappears and lever reset.
3. ground spoilers: I am not sure but I think the ground spoilers autoretract if you exceed 20% throttle set... maybe somebody can confirm.
4. what you could add: rudder trim option
5. The max. bank should be 45deg at high alpha. Unfortunately I dont know how airbus defines a high AOA condition. maybe in alpha prot?
6. I have not tried but have you considered the rudder limiter which allows 25deg below 160kts and 3.5deg rudder deflection above 380kts? I can send you a picture of the function inbetween. Its not linear.
7. And something different and really really NOT important :): Do you know why the gear retraction/extraction animation is not as smooth as on some other planes? I just noticed it in the outside view of the idfg... same with the schematic animation on the SD.
8. regarding the tangential paths on ND ... I assume its not easy to check while keeping the code CPU efficient...but on the other hand its just not nice to load a SID or STAR and have some strange curves on the final even all waypoints are on RWY track. Maybe your algoryhm should be based on curvature. If you need help for algorythm brainstroming... drop me a line.
9. Hydraulics: I have not done many tests... but as you said its not very detailed yet. I assume, a first step would be that you can not control some of the surfaces without any hydraulics. second step would be a spilt of the systems wrt to the hydraulic systems G,B,Y. so an aileron stops working if 2 of the 3 systems fails... and the third step would be to change details like changing the color of the rudder on the flight control page on the SD from green to amber if all 3 systems fail...
BTW: I just think of the flight model if for example only some spoilers are working ... that means the max. drag would need to be reduced... oh man, it's getting complicated... :)
I am getting excited about B25 :)
Thanks JL,
Rob
Hi,
Some of your proposal will be very difficult to add because of FS limitations. For instance, you cannot control left or right spoilers separately, not to mention separate spoilers on each wing. It is possible to cheat a bit (like extending the spoilers halfway when half of the spoilers shold be full etc...), but this can still be very limiting. A few more remarks:
1. #2 to #5 for roll: should be added in B25 (if I remember correctly...)
2. Will add that at a later stage.
3. Just read the FCOm, it's during touh & go, they retract if one THR LVR is advanced at 20° or more (not %N1 but actual THR LVR position)
4. Will add that at a later stage.
5. Only normal law ias available for now, I will add some more limitations to the FBW later
6. Will add that at a later stage.
7. No idea, maybe because it's an old external model for FS2004...
8. If you have knowledge in that area, I'm interested, email or PM me please!!
9. Will add that at a later stage. Here again the loss of one system will be hard to reflect on the governs without cheating.
Cheers,
JL
Hello JL,
Sorry, I am not a pro in the area of trajectory planning :(
but I've done some more testing wrt the flight path trajectory --> I am not 100% sure but I noticed that the arcs which don't end tangentially to the next linear track only occur in turn-cases > 90deg. So I assume you have different approaches to calculate the path depending on the turn angle. For waypoints with angles <90deg I could not see any problems. Was that coincidence? Maybe only a part of your path algorythm needs some tuning?
I also checked the strange arcs after selecting a SID. Usually there is this waypoint on Runway Track @ lets say at 1500ft and i.e. 3NM from runway. Lets call it Waypoint -A-. Now insert a SID in which a waypoint -B- occurs which is between the waypoint -A- and the runway (like at 2NM from runway).
Now the FMGS will consider the path from runway to WP -A- at 3NM and back to -B- at 2NM before continuing correctly with the SID.
Did you get what I mean or should I take a screenshot of the ND??
Where is this waypoint -A- coming from? Is -A- the same WP you have when selecting "NO SID"? How is this waypoint defined? Or is it NAV data related?
Thank you!
Rob
Hello Rob,
I think a screenshot would help here :-)
Also, the navdata from leveld is probably not the best one. I'm trying to get another navdata format (from navigraph, as they are the only ones on the market anyway), but this is not an easy thing, as most payware addons have their own database format and do not release the format specs. I plan to add full ARINC424 support in B26 or B27 if I can get find a suitable navdata. This transition will also take a long time to code, but should be really worth it.
Cheers,
JL
Hi JL,
Sorry for the confusing... so again--> here are two screenshots of the problem. When you select a runway on the depature page, FMGS will show a WAYPOINT -A-. Even you have not selected any SID.
If you select a SID like shown on the second screenshot you see that the path is wrong. I guess the Waypoint -A- shouldnt be there. My question was: What does this artificial WP -A- represent/ how is it defined? Did you get my issue now regarding wrong path trajectories on SIDs? :)
Could you please explain the difference of white and green waypoints shown on ND?
I like you ARINC protocol support and I can imagine that all the payware providers keep their lips tight wrt their Navformat. :(
Thanks and regards,
Rob
Attachment 6630Attachment 6631
What you call waypoint A is indeed automatically added when you only select a departure RWY without SID. However, in your second screenshot, this WPT has been deleted (you can see that because it is not at the same distance on the ND). In this case, it's the navdata which contains this succession of waypoints. It would be interesting to look at the chart for this SID, the WPT B might be there for real, and in the same sequence order.
Cheers,
JL
Hi,
How is "your" "auto-WP" defined in terms of runway distance and altiude in case you dont select any SID/STAR?
So for my example ...here is the actual chart. The loaded SID would match the real thing except that this first "1900" waypoint? this point does NOT exist on the attached chart. I also just took a look into the original *.xml Navdata file. Now I got it! This wrong point does NOT come from your software. I thought its some sort of wrong auto point from your software. So its LevelD related.
BTW: I just noticed that the Navdata contains max. Bank. Could that be considered in B3XX? ;)
My currently used Navdata is pretty old (June 2010). Can somebody else check this stupid behaviour with this strange "1900" waypoint i.e. at EDDM 08L Anker ... whoever has a newer Navdata version? Fritz? Tom? :)
Regards,
Rob
Attachment 6633