CJSouthern
-
Posts
127 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Latest X-Plane & Community News
Calendar
Downloads
Store
Posts posted by CJSouthern
-
-
Thanks Dan,
I'm currently discussing the issue with Richard @ Navigraph, and he's asked a couple of questions in the same area:
- Which XP Nav Specification expect the Hot Start TBM900 (XP11.50 below or XP11.50 above?)? That´s important because it depends which dataset you should use. I guess this can only be answered by the developer.
- Which is the exact path, from where the Hot Start TBM900 reads the data? /???
@Goran_M Just wondering if you're able to answer the above for me?
-
39 minutes ago, Goran_M said:
Correct. What you're seeing on the G1000 display is what would be seen on any aircraft, default or payware, that uses the default G1000 display.
Thanks for that. eMail sent. I copied the \custom data into a \default folder that I found with identical-looking files but - alas - that just crashed the sim. So at this stage I'll just have to wait to hear back from Laminar.
-
13 minutes ago, Goran_M said:
In that case, you might be better off sending an email off to Laminar and asking if something went wrong in an update. The TBM uses the default moving map and all navigation code for the displays. If the navdata isn't updating correctly, it is definitely something that they did.
Thanks. Just to confirm - if the TBM model is using up-to-date databases then the correct date of those will be reflected on the init screen of the MFD on power-up - Correct?
-
42 minutes ago, Goran_M said:
Thanks, I'd already read that thread several times, & it's not helping.
Basically XP Nav database IS updated according to both Navigraph and what I'm seeing on the 737-800 FMC (and verifying by way of checking file date stamps) - but the G1000 on the TBM and C172 don't appear to be using it because the correct SIDs aren't there (per the photos).
-
Just some follow-up photos of what I'm seeing; I ran the 737-800 aircraft in XP and was able to verify that the database is the current AIRAC cycle (expires 03 Dec 2020) - but I don't know enough about how to use a FMC to see what SIDs are available.
From what I can see so far it looks like Navigraph is downloading & updating XP just fine, but the G1000 equipped aircraft appear to be looking somewhere other than the X-Plane\custom\CIFP folder for their data.
I really need some help with this ... at the "brain about to explode" stage
-
I understand that the TBM 900 uses the same database as XP. I subscribed to Navigraph and updated XP - and was able to see that all the files in the ...\CIFP folder were dated as of a week or so ago - so I'm assuming that this has updated correctly.
However when I start the MFD on the TBM 900 it's still reporting that the databases are about 4 years old - and when I bring up the list of available departures from NZNS they aren't correct (eg last one should be a ZULU2 departure).
In MSFS when I do the same thing on the TBM 930 I see the correct list of departures although I'm not sure if it just shipped with a later database anyway (I'm struggling to find a way to verify database date on the MFD of any aircraft on either sim platform)
When I checked the C172-G1000 model under XP it also doesn't show the correct departure list for NZNS.
Can someone please give me a heads-up as to what I'm going wrong? The Navigraph FMS manager scans and finds XP - downloads about a 16MB file - then installes several thousand files - it's all looking just fine - it just doesn't appear to be giving me the right data.
-
13 minutes ago, Goran_M said:
That means your pressure vessel is damaged, and that can't be repaired. Make sure you dont make any tail strikes or when you load the TBM, make sure it doesn't "drop" on the tarmac.
I just had a look at that log - I think those items were all a result of a crash yesterday when I tried out the AI and it popped me into the air but with the engine shut down - then it caught fire when I tried to start it and I had a slow and agonising glide into the water. The current airframe doesn't appear to be showing any issues. Is there a way to determine if any component is sub-optimal without having to select each and every section and choose "access"?
-
16 minutes ago, Goran_M said:
Found a few things.
When in sim, check the maintenance manager and make sure nothing is broken. The TBM900_log.txt file is showing some things as failed or worn, and this may have an effect on the throttle.
If you find anything damaged or broken, repair them and try again.
I can check shortly, but I've had several crashes when it's gone absolutely crazy upon AP disconnection and have needed to create new airframes - and have seen that everything is "as new" after that - and I've had this issue all throughout several different airframes.
-
2 hours ago, Goran_M said:
Ah, hold up a minute. So am I right in assuming you're using the F5 and F6 keys by holding them down while in the different ranges, without letting them go when the power lever reaches it's limits?
If you press F5, while in the high idle range, to bring the power lever to the bottom of that range, but you keep the button pressed AFTER it reaches the high idle position, X-Plane will read that value as zero, instead of the mid point. So when you drag it over to low idle, because of the value X-Plane has recorded (zero), it will snap the power lever to cutoff. If you were to use hardware, and you brought the power lever back to high idle, you would need to bring the hardware throttle to about half way only. Bringing it back all the way will have the same effect if you were to then move the power lever to low idle. It would snap to cutoff.
So, in case I don't make any sense, if you're at full power, press the F5 key until you reach high idle. Then STOP. Don't keep the button pressed. Then drag the power lever over. It should stay at low idle. This will also work in reverse. Moving from START to low idle by pressing F6, do not keep it pressed longer than it takes for the power lever to reach low idle.
Hope this makes sense.
I don't normally use the F5 / F6 keys at all - but when I do 1 press will take it from low idle to high idle or vice-versa (depending on which key). Further presses will take it across into the normal range, but that's not what I'm doing; I can start the sim - not even touch the keyboard - and the throttle still "does the thing" we're seeing.
I've attached both of those log files - I started the sim - moved the throttle from cutoff to low idle then attempted to move it from low idle to high idle - noted that it cut across to flight idle then exited the sim with an alt+F4 - is that what you need?
-
4 hours ago, Goran_M said:
On top of giving GEEVEK's suggestion a try, you will have zero problems with a demo version of X-Plane. No serial numbers to enter. It's purely from a testing standpoint. To see if the TBM works in a bare demo version of X-Plane.
If you want to give it a try, here's the link.
To be honest, this is the first time I've come across such a problem, where the power lever snaps to certain positions, beyond the mouse input. I thought by disconnecting your hardware, the problem would stop, because there are no other inputs forcing the power lever to move beyond where you want it to move. But it definitely looks like something is forcing it to these positions.
Could you load the TBM, then shut down the sim, then send me your TBM900_log.txt file and the log.txt file, both found in your X-Plane root folder. I want to see what's going on in there.
I'll have a look when I get home tonight (in a few hours from now).
I don't think GEEVEK's post is going to help in that I can already control that aspect of throttle motion using the F5/F6 keys (default mapping) and I don't have any kind of analog throttle controller yet (unfortunately).
-
1 hour ago, Goran_M said:
Do you have any scripts or plugins like flywithlua that may be taking control of the power lever?
Can you try downloading a demo of X-Plane with no scenery and no plugins, then install the TBM in that version for a test?
(Don't worry about DRM. You can have multiple copies of the TBM installed on the same computer.)
No - no scrips or plugins. It's just a bog standard XP install followed by your TBM (I got sick of all the bugs in the MSFS TBM and jumped ship)
To be honest, I'm apprehensive about creating more problems for myself if I try downloading other copies (current installation is via Steam) - is it possible to have a stand-alone version of XP that's not going to give me conflicting registry entries (or similar) down the track? This issue isn't a particularly big deal as I wouldn't usually leave the aircraft in high idle anyway - and can do it via the keyboard if I need to; I'm just hoping for a "good fit" with the Bravo throttle quadrant when it arrives because I'm currently struggling badly with energy management in the aircraft - and throttle control is the cause of at least 2/3 of it.
-
7 hours ago, Goran_M said:
Something definitely wrong there. As a test, disconnect all your controller hardware, except the mouse. Load the TBM, and then try moving the power lever with the mouse.
Switched off keyboard - Switched off graphics tablet - unplugged Alpha Yoke - Started XP -> no change.
At one point during testing it did start working correctly for about 30 seconds - but then went back to it's old tricks without me doing anything else that I can remember (with the possible exception of a throttle level change). BTW I don't have a throttle attached (yet; Honeycomb Bravo due to ship to me shortly) so I map "Throttle up a bit" and "Throttle down a bit" to the white buttons on either side of the Honeycomb Alpha yoke (which works badly, but it does work) - but I'm not pressing these whilst I'm trying to get to high idle.
F5/F6 for mixture control moves between high/low idle just fine though.
-
11 hours ago, Goran_M said:
I'm guessing you're somehow clicking and dragging to the right, while also dragging diagonally down. Can you confirm?
Not that I'm aware of. I shot a quick video of what I'm seeing at my end - you should be able to see mouse movements from this.
-
10 minutes ago, Goran_M said:
It shouldn't be doing this. Make sure you don't have anything assigned to your mixture settings.
Only the default function keys (f5, f6 etc) which I'm not touching.
-
11 minutes ago, Goran_M said:
We do. You should see a mouse cursor (left-right) when hovering the mouse over the left side (I think) of the power lever.
Yes - but as soon as I move it to the right it jumps down to low idle - and as soon as I raise it to high idle it pops across to flight idle.
I can't get it to stay in high idle unless I use the keyboard.
-
1 hour ago, Goran_M said:
Set a key or button press to "Toggle Thrust Reverse". This will get the Power Lever into the beta range. The more you drag your hardware down, the more it goes into thrust reverse.
Ah - got it thanks. I already had the key assigned, but I was confused as to why it was going full reverse thrust (because I had the hardware at minimum when I activated it) (I guess you had to do it that way because you can't physically stop hardware at the point where it would have hit the lockout gate?)
Out of curiocity, why don't you allow high idle to be selected with the mouse? (only F5/F6 to select between high idle and low idle).
-
I've not had any luck finding out how to do this other than hitting the "\" key which immediately puts the aircraft into full reverse thrust.
What's the "secret" folks?
-
I've had this happen to me too; not sure if this is related of not but I started with a REALLY "hairy" takeoff (I think my trims weren't set) and I "saved" it by engaging the AP. Control was nominal through 10,000 feet. When I disconnected the AP at TOD to hand-fly it down the other side all hell broke loose similar to the above posts. I tried to re-engage the AP but it wouldn't re-engage.
-
Update: Sorted.
I had to start XP then reconfigure my Windows sound devices so that XP used the one device that I had - and then start the flight with the TBM.
Something that needs tweaking in the plugin for future perhaps?
Cheers,
-
Hi folks,
My Asus RTX3080 graphics card arrived. I've installed the card & latest driver - cranked up XP - and tried to start a flight with the TBM 900, but every time XP crashes back to the desktop.
If I select the C172 then all works as expected - so I'm assuming that it's a TMB 900 issue.
Log attached - would appreciate any help.
Many thanks.
-
Roger that thanks. Hopefully all will jump into life as it should when my RTX3080 arrives in (hopefully) about a month.
-
Ah - OK - thanks for that.
Does it do something a different way compared to the stock aircraft?
-
Thanks folks. If it is due to not having a "real" graphics card yet then not a problem - but if it's due to something else then it would be nice to be able to fly it in the meantime.
In comparison the C172 works just fine with my existing setup (albeit with all graphics options set to minimum).
-
If it helps, I've had a look through the log myself and found the following errors:
WARNING: extension missing proc glGetnTexImage. This is a problem with your video driver.
WARNING: extension missing proc glGetnUniformdv. This is a problem with your video driver.
WARNING: extension missing proc glGetnMapdv. This is a problem with your video driver.
WARNING: extension missing proc glGetnMapfv. This is a problem with your video driver.
WARNING: extension missing proc glGetnMapiv. This is a problem with your video driver.
WARNING: extension missing proc glGetnPixelMapfv. This is a problem with your video driver.
WARNING: extension missing proc glGetnPixelMapuiv. This is a problem with your video driver.
WARNING: extension missing proc glGetnPixelMapusv. This is a problem with your video driver.
WARNING: extension missing proc glGetnPolygonStipple. This is a problem with your video driver.
WARNING: extension missing proc glGetnColorTable. This is a problem with your video driver.
WARNING: extension missing proc glGetnConvolutionFilter. This is a problem with your video driver.
WARNING: extension missing proc glGetnSeparableFilter. This is a problem with your video driver.
WARNING: extension missing proc glGetnHistogram. This is a problem with your video driver.
WARNING: extension missing proc glGetnMinmax. This is a problem with your video driver.-- These also appear when I'm flying the 172 and it works as expected - so I'm guessing that they're not important?
0:00:49.022 W/ATC: Found overlapping airports with overlapping controller freqs at KCEA and KIAB!
0:00:49.022 W/ATC: Found overlapping airports with overlapping controller freqs at WSAC and WSSS!
0:00:49.022 W/ATC: Found overlapping airports with overlapping controller freqs at RJCJ and RJCC!
0:00:49.022 W/ATC: Found overlapping airports with overlapping controller freqs at RJDU and RJFU!
0:00:49.022 W/ATC: Found overlapping airports with overlapping controller freqs at RJDU and RJFU!
0:00:49.022 W/ATC: Found overlapping airports with overlapping controller freqs at WIPT and WIEE!
0:00:49.022 W/ATC: Found overlapping airports with overlapping controller freqs at VEVZ and VOVZ!
0:00:49.022 W/ATC: Found overlapping airports with overlapping controller freqs at KNSE and KNDZ!
0:00:49.022 W/ATC: Rewrote KAHN atc_ControllerRole_Del's freq: 133950 to 118000 for being in conflict!
0:00:49.022 W/ATC: Rewrote KCEA atc_ControllerRole_Twr's freq: 127250 to 118025 for being in conflict!
0:00:49.022 W/ATC: Rewrote WSAC atc_ControllerRole_Twr's freq: 118250 to 118000 for being in conflict!
0:00:49.022 W/ATC: Rewrote RJCJ atc_ControllerRole_Del's freq: 121900 to 118000 for being in conflict!
0:00:49.022 W/ATC: Rewrote RJDU atc_ControllerRole_Gnd's freq: 121600 to 118000 for being in conflict!
0:00:49.022 W/ATC: Rewrote RJDU atc_ControllerRole_Twr's freq: 122700 to 118025 for being in conflict!
0:00:49.022 W/ATC: Rewrote RJDU atc_ControllerRole_Twr's freq: 126200 to 118050 for being in conflict!
0:00:49.022 W/ATC: Rewrote RJDU atc_ControllerRole_Twr's freq: 118500 to 118075 for being in conflict!
0:00:49.022 W/ATC: Rewrote WIPT atc_ControllerRole_Twr's freq: 118300 to 118000 for being in conflict!
0:00:49.022 W/ATC: Rewrote VEVZ atc_ControllerRole_Twr's freq: 119700 to 118000 for being in conflict!
0:00:49.022 W/ATC: Rewrote KNSE atc_ControllerRole_Twr's freq: 121400 to 118000 for being in conflict!
-- Again, doesn't appear relevant2020-11-01 23:41:32 TBM900[helpers.c:1123]: Cannot open directory C:\Program Files (x86)\Steam\steamapps\common\X-Plane 11\\Output\TBM900\state: The system cannot find the path specified.
-- Was surprised to see "\\" in the path - relevant?
2020-11-01 23:41:33 TBM900[shader.c:429]: Cannot load shader C:\Program Files (x86)\Steam\steamapps\common\X-Plane 11\\Aircraft\X-Aviation\TBM-900\plugins\systems\data\librain\droplets.comp.glsl430: compile error: ERROR: 1:78: 'location qualifer' : the "location" qualifier cannot be used when a "binding" qualifier is also provided. Use "offset" instead
2020-11-01 23:41:33 TBM900[shader.c:151]: Error loading shader C:\Program Files (x86)\Steam\steamapps\common\X-Plane 11\\Aircraft\X-Aviation\TBM-900\plugins\systems\data\librain\droplets.comp.spv: SPIR-V shaders not supported and no fallback shader found.
-- Both well above my pay grade. Files are present at those locations though.
2020-11-01 23:41:33 TBM900[xplane.c:1543]: Systems plugin is disabling
-- Is this the key to the issue? Disabling because of the above 2 errors?
0:01:01.200 I/DSF: Warning for missing scenery file: -41+171
-- Irrelivant?
Hope this helps,
Cheers,
Colin
Updating Navigation Database - Having issues
in TBM 900
Posted · Edited by CJSouthern
OK - think I'm making some progress here;
1. I've found nav data in 2 places "custom" and "default". When I open up the NZNS file in both the one in the "custom" folder lists 14 unique SID procedure names - that correspond with 14 SIDs available to me in the sim whilst at NZNS. So it's looking like the sim is getting the correct data after all.
2. The init screen is still showing the databases as being about 4 years old - not sure why. @Goran_M
3. What initially lead me down the garden path was that I was looking for 3 SIDs that exist in the real world - but not in X-Plane - but do appear to exist in MSFS2020. Richard @ Navigraph explained to me that they're not in their dataset because they don't have end points; they basically end in an "turn left to go to this intersection or right to go to another one" - and the code can't cope with that; I'd assumed that the data wasn't current because they weren't there. When I asked about "how they were present in MSFS2020" he confirmed that indeed although they're there, they're just wrong in what they're pointing to. How this reconciles with the real world I have no idea (but will follow-up with an A320 captain friend to ask).