Der Michel Posted June 14 Posted June 14 (edited) Following is wrong for the VD. a.) the vertical line at the end of the scale has to be solid, not dashed. Dashed it's only, when ND has ARC greater 160 or ROSE greater 320. b.) vertical MORA line has to be horizontal aligned with 0 range line c) if the constrained is missed, the constrain symbol has to be amber with an dotted line: d) if alt constraint is ignored, it has to be white in the VD: 1. empty FMS: VIEW ALONG ACFT TRK is missing Aircraft should be at the bottom of the VD no green arrow would be correct, as no f-pln avail currently MORA is missing if SIM DEFAULT is used, but NAVIGRAPH is linked RADIO HEIGHT indication is missing 2. citypair/route entered FMS: MAGENTA AREA missing...distance to airport reference coordinate GREY AREA for the remaining VD RADIO HEIGHT indication is missing Aircraft should be at the bottom of the VD 3. runway and SID entered FMS, but no perf data avail: MAGENTA AREA missing...distance to RWY TRESHOLD coordinate GREY AREA for the remaining VD RUNWAY missing RADIO HEIGHT indication is missing Aircraft should be at the bottom of the VD green arrow should still be indicated, because no predictions are avail 4. runway and SID entered FMS, but perf data now avail: MAGENTA AREA missing...distance to RWY TRESHOLD coordinate GREY AREA for the remaining VD RUNWAY missing RADIO HEIGHT indication is missing green arrow should still be indicated, because aircraft does not follow the FMS trajectory or the selected trajectory vertical profile has to start at the calculated takeoff point In selected mode the VD is not showing the Vertical Cut along the TRACK and should show the selected vertical track not the arrow. Edited June 15 by Der Michel Specs: CPU-13900K, RAM-64GB-6800, GPU-4090
Farlis Posted June 14 Posted June 14 This one I'm not so sure of Michel. Visual differences can often come down to different software suites in the aircraft modeled. I would be hard pressed to believe that the artists at IniBuilds would not be able to draw a dashed line when their reference material tells them to do so. So I assume that the aircraft they based that appearance on is using a different version of the software and is drawing these differently than the ones you work on.
Der Michel Posted June 14 Author Posted June 14 (edited) 1 hour ago, Farlis said: This one I'm not so sure of Michel. Visual differences can often come down to different software suites in the aircraft modeled. I would be hard pressed to believe that the artists at IniBuilds would not be able to draw a dashed line when their reference material tells them to do so. So I assume that the aircraft they based that appearance on is using a different version of the software and is drawing these differently than the ones you work on. Might be yes, but believe me, system devs can forget, miss or just shortcut a lot. And they did it correct for the red version: Edited June 14 by Der Michel Specs: CPU-13900K, RAM-64GB-6800, GPU-4090
Eddie Posted Thursday at 05:19 PM Posted Thursday at 05:19 PM I'll check in with the team. Thank you EddieCommunity Manager IniBuilds Ltd. | inibuilds.com
foliainfx Posted Thursday at 06:31 PM Posted Thursday at 06:31 PM On 6/14/2025 at 6:24 PM, Der Michel said: Following is wrong for the VD. a.) the vertical line at the end of the scale has to be solid, not dashed. Dashed it's only, when ND has ARC greater 160 or ROSE greater 320. b.) vertical MORA line has to be horizontal aligned with 0 range line c) if the constrained is missed, the constrain symbol has to be amber with an dotted line: d) if alt constraint is ignored, it has to be white in the VD: 1. empty FMS: VIEW ALONG ACFT TRK is missing Aircraft should be at the bottom of the VD no green arrow would be correct, as no f-pln avail currently MORA is missing if SIM DEFAULT is used, but NAVIGRAPH is linked RADIO HEIGHT indication is missing 2. citypair/route entered FMS: MAGENTA AREA missing...distance to airport reference coordinate GREY AREA for the remaining VD RADIO HEIGHT indication is missing Aircraft should be at the bottom of the VD 3. runway and SID entered FMS, but no perf data avail: MAGENTA AREA missing...distance to RWY TRESHOLD coordinate GREY AREA for the remaining VD RUNWAY missing RADIO HEIGHT indication is missing Aircraft should be at the bottom of the VD green arrow should still be indicated, because no predictions are avail 4. runway and SID entered FMS, but perf data now avail: MAGENTA AREA missing...distance to RWY TRESHOLD coordinate GREY AREA for the remaining VD RUNWAY missing RADIO HEIGHT indication is missing green arrow should still be indicated, because aircraft does not follow the FMS trajectory or the selected trajectory vertical profile has to start at the calculated takeoff point In selected mode the VD is not showing the Vertical Cut along the TRACK and should show the selected vertical track not the arrow. In the next update there should already be a few things fixed (RADIO HEIGHT, constraints). VIEW ALONG ACFT TRK will be implemented at a later point is what I got told previously
Der Michel Posted yesterday at 09:26 AM Author Posted yesterday at 09:26 AM (edited) just as addition to my first point in opening topic. The last vertical line is done vice versa currently. It has to be dashed when the arrow is displayed top right and solid when there is no arrow. Edited yesterday at 09:27 AM by Der Michel Specs: CPU-13900K, RAM-64GB-6800, GPU-4090
foliainfx Posted yesterday at 11:56 AM Posted yesterday at 11:56 AM 2 hours ago, Der Michel said: just as addition to my first point in opening topic. The last vertical line is done vice versa currently. It has to be dashed when the arrow is displayed top right and solid when there is no arrow. It's dashed when the FCU altitude is different from the CRZ ALT entered, this should also be fixed in the next update already
Der Michel Posted yesterday at 01:47 PM Author Posted yesterday at 01:47 PM (edited) 2 hours ago, foliainfx said: It's dashed when the FCU altitude is different from the CRZ ALT entered, this should also be fixed in the next update already NO. Last picture from my last post. FCU alt 5000. CRZ ALT is definitely higher, you also see the dashed vertical profile. And here the vertical line at the end of the scale is solid, not dashed. And the other photo....FL400 pretty sure the current CRZ Level...dashed when arrow is displayed. Now this photo: Also FL400 and pretty sure the current CRZ level...solid without arrow. Edited yesterday at 02:18 PM by Der Michel Specs: CPU-13900K, RAM-64GB-6800, GPU-4090
foliainfx Posted yesterday at 03:19 PM Posted yesterday at 03:19 PM 1 hour ago, Der Michel said: NO. Last picture from my last post. FCU alt 5000. CRZ ALT is definitely higher, you also see the dashed vertical profile. And here the vertical line at the end of the scale is solid, not dashed. And the other photo....FL400 pretty sure the current CRZ Level...dashed when arrow is displayed. Now this photo: Also FL400 and pretty sure the current CRZ level...solid without arrow. Actually, you are right, I thought you meant the line on the VD indicating the vertical path. Apologies for the misunderstanding 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now