nicotum

No need to excuse yourself Jan, software without bugs simply does not exists. By the way, the issue is reproducible, at least on my RIG.

I've searched the forum without results, so I hope this is not a duplicate report. When I insert a speed restriction I get an error: G64: error: Callback_Dref_Hooked_setDataf: cdu1_lsk_3R_OnWrite: [string "ixeg.733.fmc.legs.lua.ra1"]:950: attempt to index local 'altInput' (a boolean value) After the error is raised, it seems it can be ignored and the simulations seems not affected. The installation used is stock with only gizmo and the IXEG 737. Let me know if you need more info. Bye. Log.txt

You're welcome.

@tkyler Hi and thank you guys for the v1.3 release. I'm here with a small (I hope) request: I made a librain integration for the previous version and I'm adapting it to v1.3. Everything is working except for the avitab z-depth obj, as you can see from the attached images. Would it be possible to have a solid surface for the tablet where the avitab window is rendered, in order to mask correctly the librain surfaces? Thank you in any case.

You can obtain this behaviour with a repeated "press and release" action. Increasing the SECONDS_FOR_MAX_BRAKE_ACTION value, could help too.

Zibo and Toliss use their own breaking logic, but also expose the possibility to override it. D&P Brakes simply recognizes these planes and takes control of the brakes. With the IXEG this is not necessary and it is supported like any other plane. Note that you can customize the timings for the IXEG or any other aircraft. All is documented here.

Guys, you may want to consider to have a look at my free plugin "Differential and Progressive brakes for X-Plane". It's configurable on a per aircraft base. These are the docs.

Just updated to 1.1.7 and got my first CTD with the TBM900. Here are my logs. TBM900_Log.txt Log.txt

It's a beta bug confirmed by Austin.

I've compared the size of v1.08 objects with those from v1.06 and I've seen that a pair of objects are actually much bigger than before. Since you told that you worked on the poly reduction side, may I ask if this is expected? v1.08 objects/size: TBM900_cockpit.obj 3.426.939 objects\Instruments_1.obj 33.425.198 v1.06 objects/size: TBM900_cockpit.obj 762.358 objects\Instruments_1.obj 15.833.216

Is it sufficient to copy the aircraft folder or do we have to install another copy? How do we have to handle the license for the second copy? Do we have to re-activate it? Thank you in advance

Hi Steve, it seems that pressing 'b' and then 'v' is working too. Hope this helps.

Yes

Two approaches and two times it happened to me too.

Hi @tkyler, could you share with us these info or part of them? I'm fighting with PlaneMaker and the beta range in another aircraft (just for curiosity) mounting 2 PT6A-34. Thank you anyway.