Throttle problem

[Markeebo]

After installing the ADV addon, My throttles will not move after I have left-clicked them to get them out of the stops. The engines will TEMPORARILY spool up and then back off to idle when I move the throttle levers while never visually moving in the cockpit. Works fine if I uninstall and only Install the Phantom and TP.

I have checked to make sure that the AXES are set up ONLY in FSUIPC so there is no interference from the P3D controls setup. I'll be happy to provide any other info requested.

Any ideas would be most welcome.

P3D v3.4.22.19868
FSUIPC v 4.962
TacPack v1.4.3.4

Markeebo

[JonathanBleeker]

Odd. I never tested it with FSUIPC only but will try that here. What event are you passing through FSUIPC for the throttles?

[Markeebo]

Odd. I never tested it with FSUIPC only but will try that here. What event are you passing through FSUIPC for the throttles?

Just Throttle 1 and 2. Pretty simple.

All controllers turned off in P3D and I then allow FSUIPC to manage both the axes and the calibration. Cold and Dark or Already running yield the same results. Throttle levers dont move. Engines spool up then immediately down again.

I have a comrade who is having the EXACT same issue.

Markeebo

EDIT: I went thru the controllers/buttons dialogs in P3D to make sure there were no competing Controllers/buttons interfering with the throttle movements. Its especially strange since it was fine before I installed the ADV mod. I cant seem to get the GPU start to blow any air either, but I am thinking that this might have something to do with the throttles so I'm holding off starting a new thread until this gets addressed.

[Alvaro]

What happens if throttle axes are managed by p3d instead of FSUIPC?. Do they work?

[Markeebo]

What happens if throttle axes are managed by p3d instead of FSUIPC?. Do they work?

Yes. Deleted the calibration and AXES assignments and added them into P3D and they're fine. Just hate to have to delete all of the other assignments for the rest of the aircraft to accommodate just one. hopefully there is a work around for it.

@JonathanBleeker, Specific FSUIPC control was Axis Throttle 1 Set. Same for 2

Mark

[Krazycolin]

Sorry but no. If the issue is not with our product (and it's not) then you'll have to recalibrate or make a specific profile for it.

Sorry.

[Markeebo]

Well thanks for the help

[Jim_Tenn]

Having the same issue. Only way I have managed to get it to work is to remove FSUIPC and go through and set the controls entirely in P3d. Did not have the same issue with the base F-4E which works just fine with FSUIPC in conjunction with MVAMS. Guess the Advanced model will be shelved until a work around is figured out. Too much of a hassle to set up just to fly one specific model.

[JonathanBleeker]

I find this odd as FSUIPC should only be passing the event through to the sim and my code should be intercepting it. I will contact Pete Dawson once I have checked things out this side.

[Markeebo]

Having the same issue. Only way I have managed to get it to work is to remove FSUIPC and go through and set the controls entirely in P3d. Did not have the same issue with the base F-4E which works just fine with FSUIPC in conjunction with MVAMS. Guess the Advanced model will be shelved until a work around is figured out. Too much of a hassle to set up just to fly one specific model.

Same here. Uninstalled the Phantom. Reinstalled the latest plus TP sans ADV. All works perfectly now.

[Firebird]

Same issue here. Everything worked normally with every other variant of the F-4E until I purchased the ADV version. Now, no throttle movement. Also using FSUIPC. Since every other version of the F-4E worked with FSUIPC, and this is an upgrade of the same aircraft, I believe the expectation is that it should work as advertised after the update as well. Just to shrug it off and say it is not your problem after you charged additional money for it and do not state in a disclaimer that it may not function, makes me wonder about other future Milvis offerings. FSUIPC has been a staple of all versions of MSFS from the beginning to get functionality of the peripherals. How could this not be tested using this format? When I purchased the T-38, FSUIPC worked. When I purchased the advanced version, it worked as well. My expectation when I purchased the F-4E Advanced is that it would work as well. If it is not going to be fixed, I think I would like to request a refund for the advanced addon as I need the use of FSUIPC much more than I need this module.

[JonathanBleeker]

Read the post I made....You aren't being brushed off entirely. Technically it is not our problem but I said I would be checking it out anyway.

[JonathanBleeker]

Ok I removed axis assignments from P3D and put them through FSUIPC and everything worked fine here. Please send a screenshot of your FSUIPC axis calibration screen so I can try duplicating here. Also I would suggest taking this up with Pete Dawson.

[Firebird]

Thanks JB, will work on it later when I get home. The statement I made was not directed at you as I read your post about checking it out and was heartened that the developer was involved. It was directed at the person who said it was not their problem so NO. I have a friend who also turned off the P3d axis this morning and said his worked as well, so a uninstall/reinstall or even redoing all of the axis inputs from the previous F-4 may work. I will reply here if I can get it running, but if others do, I should be able to as well.

Mike

[Firebird]

OK, I have completely uninstalled and reinstalled the Milviz F-4E up through ADV (including Tacpack). I have deleted profile specific profiles in FSUIPC, tried every possible combination of Throttle selection (Direct using Throttle1 and Throttle2 as well as Axis Throttle1 and Throttle2) to no avail as the Warthog throttles do not move the aircraft throttles. What I have learned is that somehow the F-4E Advanced update seems to select its own throttle somehow, and it always defaults to Throttle (no number). At first, I found it was attached to my F-16 cockpit throttle, so I deleted the profile in FSUIPC and unplugged the TM Cougar from my computer (just removing the axis did not help, it just stopped working totally when I did that), uninstalled the F-4 and reinstalled it. That resolved the issue of the Cougar. I then assigned the Axis's (using direct to FSUIPC Config, Throttle1 and 2) again and found that it had now assigned the Throttle to my "microstick" on the Warthog. I deleted the profile in FSUIPC again and built it using the Pass through FS, Axis_THrottle1 and 2, with same result. I do not see any axis assignments for the microstick in FSUIPC Config, but it sure moves the "Throttle" on page 1 or 2 of the Calibration tab. At Midnight I gave up, but this has to be something within the ADV update as the standard F-4E w/Tacpack works as it is supposed to, as do all of my other Aircraft, including the T-38 ADV. One last thing. Within FSUIPC Config, it does show the correct axis assigned to the Throttle1 and Throttle2 (both variants), it just ignores them as though there is a conflict. I will continue to troubleshoot this as time permits. It is funny how it works for some and not others. Is it possible that it searches the P3D controls and assigns even though the section is unselected?