Blackbird Sims / Milviz Forum Archive

The aircraft do not want to lift off from ground, takeoff trim is pushed elevator is working. Speed increase beyond 145 kt and still glued on runway. Problem with throttle too, but after trying out some combinations, assign throttle 1 and 2 in P3D combined together with FSUIPC, (but not alone with either) I got it to work. Direct input is selected in P3D.

You using EZdock?

JonathanBleeker wrote: ↑

Wed Aug 28, 2019 6:39 am

You using EZdock?

I'am using EZCA V3

The ADV products are not compatible with Ezdok. Try to disable the fuselage shake option.

Actually, I do not understand why the throttle does not work, it has nothing to do with Ezdok (EZCA) as I can understand. Eileron, elevator, rudder and brakes are working properly. Setting the afterburner detent work intermittently, sometimes it works and sometimes it don't, but it does not remember the settings in MVAMS. Spent 3 hours just to figure out why. Does MVAMS has its own mapping for the Controls or does it use Windows default? In Windows Game Controller the Throttle shows up and works correctly. No problem with any other aircraft in P3D own mapping or in FSUIPC. I have tried both for the T-38, and switched off both as well but nothing works now.

I have not been able to try disabling EZCA to see if the aircrat still is glued on runway, last time it had 300kt on rwy, but still it did not lift off. Now I can not try since I do not have any throttle working.

I had both issues - i.e. power levers wouldn't move, and aircraft won't unstick normally on takeoff.

See my thread "VC throttles don't move" for details, but in summary:

I disable FSUIPC by moving the .dll for FSUIPC (in the P3D Modules folder) to a temporary location on the desktop when I want to fly the T-38.

I check to make sure the controls are in DirectInput mode in P3D.

After engine start, I push my hardware levers (I have two joysticks, and one of them has two throttles, which I use for each engine) - to the position where I want them to be for full Military power.

Then I click the item on the Milviz T-38 menu to set this as the Mil/Afterburner transition point.

I use EZCA/EZDOK V2. I have noticed that as long as I turn FUSELAGE SHAKES to OFF, I can enable - yes, that's can enable - other camera effects and shakes etc; and she will fly.

Note - I noticed that even with EZDOK set to "Globally Disable", if the fuselage shakes option was still on, the aircraft wouldn't unstick (even >200 knots).

znatusch wrote: ↑

Wed Aug 28, 2019 11:54 pm

I had both issues - i.e. power levers wouldn't move, and aircraft won't unstick normally on takeoff.

See my thread "VC throttles don't move" for details, but in summary:

I disable FSUIPC by moving the .dll for FSUIPC (in the P3D Modules folder) to a temporary location on the desktop when I want to fly the T-38.

I check to make sure the controls are in DirectInput mode in P3D.

After engine start, I push my hardware levers (I have two joysticks, and one of them has two throttles, which I use for each engine) - to the position where I want them to be for full Military power.

Then I click the item on the Milviz T-38 menu to set this as the Mil/Afterburner transition point.

I use EZCA/EZDOK V2. I have noticed that as long as I turn FUSELAGE SHAKES to OFF, I can enable - yes, that's can enable - other camera effects and shakes etc; and she will fly.

Note - I noticed that even with EZDOK set to "Globally Disable", if the fuselage shakes option was still on, the aircraft wouldn't unstick (even >200 knots).

You can use FSUIPC, your axis profile for the T-38 must just look like this:

[Axes.Jet_2_Stick_T-38]
RangeRepeatRate=10
0=3X,256,F,66388,0,0,0 -{ TO SIM: AXIS_RIGHT_BRAKE_SET }-
1=3Y,256,F,66387,0,0,0 -{ TO SIM: AXIS_LEFT_BRAKE_SET }-
2=3Z,256,F,65764,0,0,0 -{ TO SIM: AXIS_RUDDER_SET }-
3=4Z,256,F,66423,0,0,0 -{ TO SIM: AXIS_THROTTLE2_SET }-
4=4R,256,F,66420,0,0,0 -{ TO SIM: AXIS_THROTTLE1_SET }-
5=5X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }-
6=5Y,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }-

The important part is the TO SIM and AXIS events.

What's happening is your afterburner threshold has not be set. The MVAMS looks at your P3D controls config for your throttle assignments so it can read your throttle and set the afterburner threshold, but if those are missing as is the case with FSUIPC controls, you need to make sure your FSUIPC is configured properly, and then use the Set Afterburner Threshold from the Addons menu->Milviz T-38A.

And disabling EZDock will solve the glued to the runway problem.

JonathanBleeker wrote: ↑

Thu Aug 29, 2019 7:58 am

You can use FSUIPC, your axis profile for the T-38 must just look like this:

[Axes.Jet_2_Stick_T-38]
RangeRepeatRate=10
0=3X,256,F,66388,0,0,0 -{ TO SIM: AXIS_RIGHT_BRAKE_SET }-
1=3Y,256,F,66387,0,0,0 -{ TO SIM: AXIS_LEFT_BRAKE_SET }-
2=3Z,256,F,65764,0,0,0 -{ TO SIM: AXIS_RUDDER_SET }-
3=4Z,256,F,66423,0,0,0 -{ TO SIM: AXIS_THROTTLE2_SET }-
4=4R,256,F,66420,0,0,0 -{ TO SIM: AXIS_THROTTLE1_SET }-
5=5X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }-
6=5Y,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }-

The important part is the TO SIM and AXIS events.

What's happening is your afterburner threshold has not be set. The MVAMS looks at your P3D controls config for your throttle assignments so it can read your throttle and set the afterburner threshold, but if those are missing as is the case with FSUIPC controls, you need to make sure your FSUIPC is configured properly, and then use the Set Afterburner Threshold from the Addons menu->Milviz T-38A.

And disabling EZDock will solve the glued to the runway problem.

Thanks for this! I like to set the remaining slider on my other joystick for wheel brakes, so this looks like it should be possible.

JonathanBleeker wrote: ↑

Thu Aug 29, 2019 7:58 am

znatusch wrote: ↑

Wed Aug 28, 2019 11:54 pm

I had both issues - i.e. power levers wouldn't move, and aircraft won't unstick normally on takeoff.

See my thread "VC throttles don't move" for details, but in summary:

I disable FSUIPC by moving the .dll for FSUIPC (in the P3D Modules folder) to a temporary location on the desktop when I want to fly the T-38.

I check to make sure the controls are in DirectInput mode in P3D.

After engine start, I push my hardware levers (I have two joysticks, and one of them has two throttles, which I use for each engine) - to the position where I want them to be for full Military power.

Then I click the item on the Milviz T-38 menu to set this as the Mil/Afterburner transition point.

I use EZCA/EZDOK V2. I have noticed that as long as I turn FUSELAGE SHAKES to OFF, I can enable - yes, that's can enable - other camera effects and shakes etc; and she will fly.

Note - I noticed that even with EZDOK set to "Globally Disable", if the fuselage shakes option was still on, the aircraft wouldn't unstick (even >200 knots).

You can use FSUIPC, your axis profile for the T-38 must just look like this:

[Axes.Jet_2_Stick_T-38]
RangeRepeatRate=10
0=3X,256,F,66388,0,0,0 -{ TO SIM: AXIS_RIGHT_BRAKE_SET }-
1=3Y,256,F,66387,0,0,0 -{ TO SIM: AXIS_LEFT_BRAKE_SET }-
2=3Z,256,F,65764,0,0,0 -{ TO SIM: AXIS_RUDDER_SET }-
3=4Z,256,F,66423,0,0,0 -{ TO SIM: AXIS_THROTTLE2_SET }-
4=4R,256,F,66420,0,0,0 -{ TO SIM: AXIS_THROTTLE1_SET }-
5=5X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }-
6=5Y,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }-

The important part is the TO SIM and AXIS events.

What's happening is your afterburner threshold has not be set. The MVAMS looks at your P3D controls config for your throttle assignments so it can read your throttle and set the afterburner threshold, but if those are missing as is the case with FSUIPC controls, you need to make sure your FSUIPC is configured properly, and then use the Set Afterburner Threshold from the Addons menu->Milviz T-38A.

And disabling EZDock will solve the glued to the runway problem.

Ok, thanks!
This is how my FSUIPC looked like for the T-38.

[Axes.T-38]
RangeRepeatRate=10
0=2X,256,D,1,0,0,0 -{ DIRECT: Aileron }-
1=2Y,256,D,2,0,0,0 -{ DIRECT: Elevator }-
2=3Z,256,D,10,0,0,0 -{ DIRECT: Throttle2 }-
3=3R,256,D,9,0,0,0 -{ DIRECT: Throttle1 }-
4=4X,256,D,8,0,0,0 -{ DIRECT: RightBrake }-

Changed it to this:
Still no response from the throttle. Set the afternburner detent in P3D menu, one time P3D crashed back to desktop doing so.

[Axes.T-38]
RangeRepeatRate=10
0=3X,256,F,66388,0,0,0 -{ TO SIM: AXIS_RIGHT_BRAKE_SET }-
1=3Y,256,F,66387,0,0,0 -{ TO SIM: AXIS_LEFT_BRAKE_SET }-
2=3Z,256,F,65764,0,0,0 -{ TO SIM: AXIS_RUDDER_SET }-
3=4Z,256,F,66423,0,0,0 -{ TO SIM: AXIS_THROTTLE2_SET }-
4=4R,256,F,66420,0,0,0 -{ TO SIM: AXIS_THROTTLE1_SET }-
5=5X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }-
6=5Y,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }-

I just coppied the above, but I got dubble sets after configuring it in FSUPC, so I just made a new configuration that look like this, but still no throttle. I use Thrustmaster Worthog throttle.

[Profile.T-38]
1=T38A_ADV NATO
2=MilViz T-38A ADV TB7
3=MilViz T-38A ADV USAF
4=MilViz T-38A ADV TB2
5=MilViz T-38A ADV TB1

[Axes.T-38]
RangeRepeatRate=10
0=2X,256,F,65763,0,0,0 -{ TO SIM: AXIS_AILERONS_SET }-
1=2Y,256,F,65762,0,0,0 -{ TO SIM: AXIS_ELEVATOR_SET }-
2=3Z,256,F,66423,0,0,0 -{ TO SIM: AXIS_THROTTLE2_SET }-
3=3R,256,F,66420,0,0,0 -{ TO SIM: AXIS_THROTTLE1_SET }-
4=4X,256,F,66388,0,0,0 -{ TO SIM: AXIS_RIGHT_BRAKE_SET }-
5=4Y,256,F,66387,0,0,0 -{ TO SIM: AXIS_LEFT_BRAKE_SET }-
6=4Z,256,F,65764,0,0,0 -{ TO SIM: AXIS_RUDDER_SET }-

Changing on of the trottles to just throtles, I can least have both throttles moving.

3=3R,256,F,65765,0,0,0 -{ TO SIM: AXIS_THROTTLE_SET }-

Yeah DIRECT is not supported. Needs to be TO SIM and one of the AXIS events, and that D should be F, with adjustments to the output value range

JonathanBleeker wrote: ↑

Fri Aug 30, 2019 12:42 pm

Yeah DIRECT is not supported. Needs to be TO SIM and one of the AXIS events, and that D should be F, with adjustments to the output value range

Yes, I noticed. There is no way to get both throtle work idenpendently in configuring FSUIPC or in P3D, I have tried both. Brakes are stuck on brakes applied, when I use Aircraft specific in FSUIPC, it only works and can be released in general settings in FSUIPC. Uninstalled and reinstalled, Norton firewall and Antivirus off, same thing. NVAMS has to be closed before installing and updading aircraft. Disabling all effect in ESCA v3 does not work, aircraft is still stuck on runway.
Note. Everything is updated to the latest version, FSUIPC, T-38, P3D

Restarted P3D, now the brakes are stuck in general setting too

Update:

Uninstalled EZCA v3. Throttles works now with axis configured in P3D, but still the same problem using it with FSUIPC. Aircraft now leaves the runway, not glued to it anymore.

It would be nice to have the Milviz ADV to work with EZCA v3. This program is the best I have ever tried and the best in the market I believe, better than Chase Plane, ACCU Feel v.2 and EZCA v2, it really feels like you are flying in P3D, otherwise I prefer flying in X-plane or in DCS to get the right flight experiance and feeling.

Unfortunately we can't stop EZCA from writing to the velocities.

That said, you should be able to disable EZCA in your dll.xml by adding the <ManualLoad>true</ManualLoad> entry. Then it will ask on sim start if you want to load or not.

As for the throttles, can you post your FSUIPC profile?

JonathanBleeker wrote: ↑

Sat Aug 31, 2019 7:31 pm

Unfortunately we can't stop EZCA from writing to the velocities.

That's the problem. The only way to allow ezca work with our products is to integrate it in our code.

In the last times we've tried to enhance the cockpit physical experience by adding buffet and ground reaction effects. Unfortunately, the ADV complexity doesn't allow to add all the features included in ezca... Which, all in all, is a dedicated addon.

Unfortunately, EZCA and ADV will remain with a low - if any- degree of compatibility.