lanmancz

Hello, I'm watching the video and it's good news! One question - isn't the throttle manipulator for both levers a bit too small? I see this is other planes as well, the manipulator for both levers is too small and hard to find in VR, especially if you're on a approach and need only a small quick adjustment. Since 99% of the time we're going to be using both throttles it would be better I think if the center manipulator for both levers was much bigger covering most of the handle and single engine manipulators were only at the edges of each lever. Also I don't quite understand the wiggling thing - so the throttle does not move unless we "wiggle" it ? And then it snaps to some last point since AP was activated ? This is a bit odd. Or does it work normally and the wiggle is just something extra ? Otherwise it looks great. Thanks.

Hello, I'd like to report please that this is still happening (clouds in cockpit in VR) in SMP v4.9.3 in XP11.50b9 Vulkan. Tested in the TBM900 v1.1.12 Also it might be related that I see some cloud textures weirdly rotating with my view. Thanks.

Hello, how do you operate the throttle in TAXI/REVERSE range in VR please ? I understand you have to lift the thing under the throttle with your fingers IRL but how do you do it in VR pls ? Thank you.

Hello, yes I did both right after install since I wanted maximum performance for VR anyway. Performance is fine. Unfortunately the issue persists. Fingers crossed for the fix in the update. Thanks.

Hello, I recently purchased SMP4 to use in VR. It works pretty well but I noticed an issue when passing though clouds in VR - the clouds sometimes pass through the cockpit and directly into one or both of my eyes which is quite unpleasant. It's not constant but it happens often enough to be unpleasant while passing though clouds.

Hello, I've been flying the lovely TBM a lot lately (v1.18) and I get this message almost every flight. It's quite funny, there I am, cruising at 30000ft and being advised to open the door to get cooler All looks fine. My bleed is on, air conditioning is set to AUTO, fan speed max (I use max to get cooler faster after I switch to MAN mode), temp selector in the middle, air selector halfway between cabin & windshield, all looks fine. What I always do is to flip the AUTO mode into MAN for a few minutes (with the fan speed at max and temp selector in the middle) and the message goes away ... and then if I forget about it then after a while I actually get too cold so I flip it back to AUTO BTW: Speaking of warning messages - is there a way to disable the "low FPS" warning please? It's a bit annoying - I get it every time during a weather refresh (even with my 9900K), otherwise my FPS is fine but every time the weather is being recalculated I get the message (I'm currently using default weather + FSGRW). Would be nice to be able to just disable the FPS warning message but I don't want to disable all warning messages because I want to know if I'm doing something wrong with the ACF. Thanks.

Also in XP11.30 LR adds the configurable input curves to all axis - that should help quite a bit even on crappy rudder like the Saitek ones I have. I found that having correct rudder trim set and using rudder trim instead of pedals (unless a bigger correction is required) on takeoff helps too. I think the crappy consumer HW with no backpressure and jittery, short travel axes are the major source of the problems. Especially if you don't have pedals at all but a twist joystick or something like that. You can't realistically expect it to behave like the real thing because the HW is completely wrong, even if the modelling is perfect. But at least the curves should help, we'll see.

There are other things that don't get saved as well like the G1000 state is always in default configuration, but I'm pretty sure it used to save the G1000 state in the initial versions but then it kinda stopped working. Since I have no RL experience with G1000 I don't know how it should behave but it's just something I noticed.

I also use xEnviro (v1.07) and it works fine. You have to keep in mind that in xEnviro they model cloud turbulence and also clean air turbulence - you can meet those from time to time. I think there is a slider in the options that alows you to dial it down if you find it too strong. But anyway, for me the plane fly fine and I don't experice these issues at all. As someone pointed out it would be best to start testing by having a clean default unmoded Xplane install with only the TBM and see if the problem goes away. If not then it's something wrong with your setup.

Welcome. I actually just uploaded a new version that solves all the problems with the previous version (toggle commands, multipanel lights) by adding a custom LUA handling for the switches. All should now work fine. PS: Also for anyone who may not know this - xSaitekPanels has a button you can map to your joystick called "Xpanels FN button" (find it in your joystick configuration). What this button does is that it allows you to accelerate the various knobs by holding it (like ALT) and also access additional functions and parameters (like YD funcion on AP button on multipanel or ability to set COURSE for NAV1 and NAV2 on radio panel). It's a neat feature that not many people know is there in XsaitekPanels by default.

This might be an obvious thing but do you have all your axis correctly callibrated ?

Thanks. It's strange though. At the time I had almost 2h of fuel still. Something LR has to fix I guess. Or I don't uderstand the logic behind it. If what you say is correct then the circle should be 400+nm, not 20 and shrinking. Odd. Or do you have to set the reserve somewhere? I haven't noticed any such menu. I guess it would make sense if the reserve was by default something like 120 gal. But thanks anyway. I will look it up in the manual and perhaps then it will be clear. At least now I know what it's supposed to be

Hello, I have one more question please about the map mode - what is that striped circle please ? It grows and shrinks from random places and does weird things like that. I don't uderstand what it represents. What is it please ?

Btw speaking of pulse lights I noticed that they work even with crashbar down and no electricity. That seems odd.

Hello, just had my first CTD Here's the log : 2018-10-27 23:31:07 TBM900[except.c:171]: Caught EXCEPTION_ACCESS_VIOLATION Backtrace is: 0 00007FFE690ABCF0 C:\WINDOWS\System32\KERNELBASE.dll+ebcf0 () 1 00007FFE6D332717 C:\WINDOWS\SYSTEM32\ntdll.dll+a2717 () 2 00007FFE6D31AB36 C:\WINDOWS\SYSTEM32\ntdll.dll+8ab36 () 3 00007FFE6D32ED2D C:\WINDOWS\SYSTEM32\ntdll.dll+9ed2d () 4 00007FFE6D296C86 C:\WINDOWS\SYSTEM32\ntdll.dll+6c86 () 5 00007FFE6D32DC5E C:\WINDOWS\SYSTEM32\ntdll.dll+9dc5e () 6 00007FFE6C26F21E C:\WINDOWS\System32\msvcrt.dll+4f21e () 7 00007FFE6C26A300 C:\WINDOWS\System32\msvcrt.dll+4a300 () 8 00007FFE6C26A271 C:\WINDOWS\System32\msvcrt.dll+4a271 () 9 0000000081BCB8CB D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+13b8cb (log_impl_v+ab) 10 0000000081BCB9D8 D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+13b9d8 (log_impl+18) 11 0000000081B95720 D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+105720 (add_obst_cb+b90) 12 0000000081B99AAB D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+109aab (tile_loader+144b) 13 0000000081BB71A2 D:\X-Plane 11\Aircraft\X-Aviation\TBM-900\plugins\systems\win_x64\systems.xpl+1271a2 (worker+92) 14 00007FFE6A143034 C:\WINDOWS\System32\KERNEL32.DLL+13034 () 15 00007FFE6D301461 C:\WINDOWS\SYSTEM32\ntdll.dll+71461 () Log.txt GizmoLog.txt

Exactly, you're probably way too fast. I wait until I'm stabilized on the GS and about 3nm out of the airport, ias < 127, my TQ is ~20-25 at that point, select landing flaps, use the yoke to keep the GS, let the ias bleed off and stabilize at ~90 kts, trim it as neccesary, TQ at ~13-17 at this point, then let it bleed off to a touchdown speed of about 80-85, then throttle back, engage reverse and bob's your uncle I just did 10 touch and gos around my airport and it works well, you just can't go too fast. Anything above 100 kts is way too fast. PS: For people having issues with takeoff it is absolutely neccessary to use correct rudder trim for your weight. Also I found out that on the takeoff roll if I start veering out of the centerline I use the rudder trim to correct that. Pedals are usually counterproductive, at least with my Saitek

Works fine for me. Make sure you download the XP11 version and put it in "X-Plane 11\Output\FMS plans". Then go into Flight Plan on the MFD, use the small rotary to go into "Stored flight plans" (or something like that, I don't remember the exact name of that page ) and it should be right there. Select it, ENTER and you should have the plan loaded.

Hello, for anyone interested I've just published my map for xSaitekPanels : It works alright but has few limitation, read the description. I will fix the limitations once solutions become available.

Xsaitekpanels Configuration for HotStart TBM900 View File *** XSaitekPanels map for HotStart TBM900 for: - Multipanel - Radiopanel - Switchpanel *** Requirements: - XSaitekPanels - v2.75+ https://forums.x-plane.org/index.php?/files/file/14646-xsaitekpanels-linwinmac3264/ - FlyWithLUA for XP11 https://forums.x-plane.org/index.php?/files/file/38445-flywithlua-ng-next-generation-edition-for-x-plane-11-win-lin-mac/ *** Installation: Remove any existing TBM900 XSaitekPanels mappings. Copy "xsaitekpanels.ini" into TBM900 root folder. (ex. "[X-Plane]\Aircraft\X-Aviation\TBM-900\") Copy "acexsp_TBM900.lua" into FlyWithLUA Scripts folder. (ex. "[X-Plane]\Resources\plugins\FlyWithLua\Scripts\") *** Tested with TBM900 v1.08 *** Mapping: Multipanel: - ALT - Altitude dial - VS - Vertical speed - IAS - Speed dial - HDG - Heading dial - CRS - Captain's course dial - AT - Nothing - TRIM - MCP wheel - FLAPS - Flaps Autopilot: - AP - AP (YD) - HDG - HDG - NAV - NAV - IAS - FLC (SPD) - ALT - ALT - VS - VS - APR - APR - REV - VNAV Radiopanel: - All standard default mapping. Switchpanel: - STARTER - AUX BP - BAT - Battery - ALT - Generator - AVIONICS - AP Trims - FUEL - Fuel Sel - DE-ICE - Airframe de-ice - PITOT - Pitot & Static - COWL - Inertial separator - PANEL - Dimmer - BEACON - Pulse - NAV - Nav - STROBE - Strobe - TAXI - Taxi - LANDING - Landing *** Known issues & limitations: - None. All should work fine. Submitter lanmancz Submitted 10/27/2018 Category Plugins and Utilities  

The plane is amazing! Beautiful bird to fly

Hello, as you probably know it is possible to use the little range joystick to look around the map. I've noticed though that when you have the map in TRACK UP mode the joystick still moves the map according to the NSEW directions so when you're flying east your buttons are rotated and up button becomes left, left button becomes down etc, you know what I mean? Seems quite odd and confusing to me, especially when you fly at some random heading it scrolls the map in unintuitive directions. It that how it's supposed to work please ? edit: Also one little thing I noticed when messing around with the map is that when you open the flight plan it noticibly squashes the vertical direction - observe the range circle to see what I mean : Also when you move the map around with the joystick things start to fall out of alignment - like your aircraft is no longer displayed on the nav path. PS: These are not complaints, just observations Obviously none of these are big problems and I understand you guys now have bigger fish to fry I'm just messing with the aircraft.

So the aircraft remembers the last position, that's neat. Unfortunately when you change scenery (which may not have the same elevation as the old one) this causes a slight issue on load. During the initial release versions I disabled my ortho to help with the FPS. Now that the FPS is great in 1.07 I re-enabled my ortho which seems to have about 10ft difference in ground altitude at my airport (it's generated using custom height data) in comparison to default terrain. Unfortunately it seems the aircraft remembers the exact altitude it was left at during last shutdown so now on load it spawned about 10ft in the air, smacked into the ground and now everything is broken It would be nice to add some check that if the last flight completed with successful shutdown spawn it at current AGL 0 please so this does not happen when I buy new scenery for example. Thanks. It's not a huge deal of course but just something I noticed.

Hello, I also got a small suggestion please. This one is about throttle and reverse controls. I wonder if it would be possible to separate these into 2 axes (perhaps as an option?) - positive range would be controlled by throttle axis, beta/reverse range would be controlled by reverse axis. It would work on the same pickup principle like it already does when the physical axis goes into reverse range without lifting the beta lock a pickup indication appears on the right - this should prevent any conflicting inputs. In normal operation (throttle down, reverse up, and vice versa) it shouldn't be a problem anyway. My reason for asking this is that I, like many people, use saitek quandrant which is not that great really, but it's the only consumer grade throttle quadrant we got before we get into the expensive stuff like Goflight, etc. The thing is that as it is now it cuts our already low-res noisy axis into a half which makes the throttle quite twitchy and super sensitive to any adjustments. Controlling the throttle with precision is a real challenge on this setup. I reckon that allowing us to use separate axis for each range should help a lot as we'd have double the usable travel distance for each range than we got now. Also while I'm at it please in future add further commands to the plane. Ideally there should be 3 commands per each control element in cockpit - on,off,toggle. For 3 position switches it would be nice to get a command for each position. For buttons simple push command. I ask this because I'd like to create and share with others a map for XSaitekPanels but currently many controls only have toggle commands which do not work very well with physical ON/OFF switches for example (yes it works but if you leave the physical switch in opposite position it operates in reverse). Also it would be nice to publish any usable datarefs the plane might provide. I tried accessing (read-only) some I found with DataRefEditor (''tbm900/lights/ap/ap'' for example) but xplane instantly froze when I tried that so I guess that is not the correct way. Some documentation of that for cockpit builders would be nice. Thanks. BTW: Great job on this plane! It is really something I haven't yet seen in Xplane. The first evening when I bought it I was messing around with it and I was blown away that you guys even modelled the fuses, and they work too! Amazing!