kaselite

Hello, i just ran into this myself. I have been practicing startup procedures on the ground and if you do them in colder weather (it started for me around OAT +2C with snow/rain/wind) then its not possible that take-off as you cant get the Airframe De-Ice to work right and the control surfaces seem to be limited. Starting is not the issue, that work all the time without problems. The (real world aircraft) have this limit: temperature limits Minimum temperature at start and takeoff : - 40°C (- 40°F). This looks like a lot of engerneeing (code) work to replicate (especially if you end up replicating all the different cold envilope characteristic). To me this is a bit of a fringe case as most people fly in warm weather (although XP12 should have better winter enviroment and it might be worth it). The solve for this is warmer weather OAT 2C to 5C works for me on the ground.

I discovered the issue (i think)... i have 1 x-aviation account per PC (prod, test 1, test 2) - each of the x-aviation accounts only work with the specific PC, i belive this is by design. I made a mistake when i ordered the G500 - i used the incorrect account (test 2, it should have been test 1). There is a possible bug in the installer. If you have two valid x-aviation accounts, the installer username / password only checks if its a valid x-avation user, it does not check if you have purchased the product you about to install. So in my case, i ran the installer, used my test 1 credentials, the software downloaded and installed but then of course, it would not validate teh G500 via Gizmo as its the wrong account. I have asked x-avation to move the G500 to the right account.

I do have multiple accounts, as i have several machines that need different licensing. Arrg

Hello, im having the same problem... i am installed in the root of c:\ however. Gizmo was working fine with the TBM 900.... Log attached. Log.txt

thank you, solved!

Hello Goran, i have a hardware-based autopilot interface. On the device each key is using 1 dataref. It works.... but not as smoothly as the virtual buttons. I ran a dataref monitoring tool, to see what datarefs used when each virtual key is pressed. I was surprised as i found that of then there is more than one for many of the buttons. I have a few questions: 1. When there are multiple datarefs, are these being issues by each key or is it a chain reaction from 1 initial dataref? 2. When there are multiple datarefs, are they required to make each function work correctly? 3. If #2 is true, are they issued all at once, or in a sequence? Im planning to run tests tomorrow, i am wondering if anyone has figured something out here. The commands from my monitoring tests: FLC sim/GPS/g1000n1_flc SPD sim/autopilot/knots_mach_toggle tbm900/actuators/ap/spd VS UP/DN tbm900/actuators/ap/nose_up tbm900/actuators/ap/nose_down VS sim/autopilot/vertical_speed sim/GPS/g1000n1_vs tbm900/actuators/ap/vs VNY sim/autopilot/vnav sim/GPS/g1000n1_vnv tbm900/actuators/ap/vnv ALT sim/autopilot/altitude_hold sim/GPS/g1000n1_alt tbm900/actuators/ap/alt YD sim/systems/yaw_damper_toggle tbm900/actuators/ap/yd AP sim/autopilot/autothrottle_off sim/autopilot/fdir_servos_toggle sim/autopilot/fdir_toggle sim/autopilot/servos_toggle sim/GPS/g1000n1_ap sim/GPS/g1000n1_fd tbm900/actuators/ap/ap BANK tbm900/actuators/ap/bank FD sim/autopilot/fdir_toggle sim/GPS/g1000n1_fd tbm900/actuators/ap/fd NAV tbm900/actuators/ap/nav APR sim/autopilot/glide_slope tbm900/actuators/ap/apr HDG sim/autopilot/heading sim/GPS/g1000n1_hdg tbm900/actuators/ap/hdg

Yes, that was the solution. thanks.

Thanks Goran, appreciated.

Hello Goran, QQ on this. I stopped using the TBM on the slave network machines (and used the Cessna instead)... i started using the TBM again as i built a better physical simulator and its nice to see the wing and window out the left and right view. Anyway... i have one problem that i cant get around. I originally thought it was the check box you mentioned above i.e. "Simulate blackout, redout, & hypoxia effects". That checkback is NOT selected. To recap, i have a master machine (front visuals) with two slaves (left and right visuals). Im using xplanes built in network mode. This all works great.... Whats happening is when i fly about 19,000 feet, the slave's pilots in the left and right machine seem run out of oxygen and they slump over in their seats. Of course, the plane is not pressurized ... so this makes sense but in in order for the simulator to work well, I would need to make sure they don’t do this! Is there any way to turn this off?

i have been flying this bird for some time, she is great, today, suddently, the master caution can not be cancelled. It reamains on constantly... CAS shows no errors, nor anywhere else in the mainternance hanger... created a new airframe... perhaps there is a real caution event, but i cant find it!

cool, thought it was something added to the model - i will find it in xplane

@Goran_M is there a way to turn off the hypoxia effect? - this would be the bare minimum needed to help with these types of setups. I cant figure out how to turn it off.

Its not RSG, its the model. Other aircraft work fine, its just this one that does not work... so it cant be xplane, RSG or anything else. Its just the TBM doing it. Thought about this... the other planes that work, are using standard g1000, so, its the changes to the G1000 in the TBM that are likely the issue.

After pressing CTRL+W (external view, no 3D cockpit), the G1000's that are in POP UP mode continuing to work but they no longer receive any input from my hardware devices (realsimgear G1000's). Other aircraft it works fine but not the 900 (like 172, C206).... any thoughts? i noticed there is another post on this, but no one answered. it would be very good to find a solution as running with a physical cockpit, you dont really want to see the virtual one, you really just want to look out the window...

Rick, i run three PCs (one front, two left, three right). What i do is run Cessna's on the left and right and the 900 on the center. Then i dont show any internal cockpit so monitors are only showing external views. This is a common approach to solve the problem you highlighted.