Jump to content
The simFlight Network Forums

MSFS Asobo Daher TBM930 locks FSUIPC


VBV234

Recommended Posts

Hi, 

Asobo Daher TBM 930 is the only plane with this problem.

PMDG 737-700, DA62, C172, Aerosoft Twin Otter work all fine.

When I load the Asobo Daher TBM930 in FSUIPC all menu items do no longer respond.

Also other Windows programs like LittleNavMap, file explorer, Internet browser do not respond to mouse clicks.

As soon as I go back to the main menu in MSFS I can use the FSUIPC menu options and the other programs again.

If I then select another plane, without leaving MSFS the problem does not occur.

FSUIPC version is 7.3.0

Linda file version is 4.1.5.289

MSFS version 1.27.21.0

Attached FSUIPC log Wile loading Daher TBM939

Please advise me what I can do.

Kind regards in advance 

Jacob.

FSUIPC7.log

Link to comment
Share on other sites

The log file you posted is useless to me as it is a continuation log - I always need to see a full log file, not a continuation one, so please never  use the New Log function when posting logs for support issues.

4 hours ago, VBV234 said:

FSUIPC version is 7.3.0

The latest and only supported version is 7.3.9, so please update and try again. You should always check that you are using the latest version before requesting support, as only the latest version (+ any betas) is ever supported.

John

Link to comment
Share on other sites

1 hour ago, VBV234 said:

I will check the forum how to create a new log, because I have no idea what I have to do other than the menu entry "New log".  

I am asking you NOT to create a new log - just don't use the 'New Log' menu entry, and just one log file will be created. The 'New Log' button closes the existing log file and starts a new one. As it says in the User guide:

Quote

New Log: this will close the current log file and start a new one. The current (latest) log file is always called
“FSUIPC7.LOG”, previous ones being renamed “FSUIPC7.n.LOG” where ‘n’ is a sequence number. Although
this will have a repeat of some of the initialisation data as the original, starting a New Log is not advised if you
intend to supply the log for support to help with a problem, as some vital information will by then be missing.

1 hour ago, VBV234 said:

Fsuipc version is 7.3.9, updated yesterday.

I have just release 7.3.10 - please update., This fixes an issue where presets assigned in the general Buttons and Axes sections were lost, as the preset file was loaded after these assignments, resulting in them not being found.

John

Link to comment
Share on other sites

Just tried the TBM930 and its working ok here (except that I can't seem to get the Throttle axis working....).
I also trued with the TBM improvement mod - FSUIPC7 still functioning normally by that mod is broken (half of the aircraft has disappeared!).

Try with Linda disabled (just temporarily rename your ipcReady.lua) - if FSUIPC7 functions normally then it will be an issue with Linda and should be reported to the Linda support forum.

John

Link to comment
Share on other sites

Hi John,

I followed your suggestion. ipcReady. lua renamed. Restarted everything. Problem is still there.

After going back to the menu I removed the TBM930 in the Linda GUI. Manually removed the folder ASOBO_TBM930 from LINDA-CFG folder Restarted. Problem the same.

Loaded an aircraft which I never loaded before so no FSUIPC assignments nor LINDA assignments. Everything OK

As the TBM930 is the only plane where this happens, I will live with it until I find time to reinstall FSUIPC and LINDA, as the reassignment will ask quite some time.

In the mean time thanks for your support.

Jacob 

Link to comment
Share on other sites

21 hours ago, VBV234 said:

When I load the Asobo Daher TBM930 in FSUIPC all menu items do no longer respond.

Also other Windows programs like LittleNavMap, file explorer, Internet browser do not respond to mouse clicks.

As soon as I go back to the main menu in MSFS I can use the FSUIPC menu options and the other programs again.

This is very strange. I cannot understand how anything can stop/prevent mouse interaction in all other programs except MSFS Also FSUIPC7 does nothing with the mouse at all - except receive input (button presses/releases) from it, of course.
As a final test, could you maybe rename your FSUIPC7.ini so that a new empty/default onw is created and try again to see if you get the same issue. If not, show me your (renamed) FSUIPC7.ini.

John

Link to comment
Share on other sites

Yes Sir,

 

That's it.

Daher TBM930 loaded and no issues any more with accessing FSUIPC interface nor other Windows programs. 

I attach the FSUIPC.iniTBM which is the renamed original as you mentioned.

Don't spend to much time on it, I can reassign and copy back the PMDG 737-700

Thanks for your help.

Jacob

 

BTW you stated

 I cannot understand how anything can stop/prevent mouse interaction in all other programs 

Indeed.

Work (in a simple way) with FSUIPC since FSX and have never seen it before.

FSUIPC7.iniTBM

Link to comment
Share on other sites

13 minutes ago, VBV234 said:

Don't spend to much time on it, I can reassign and copy back the PMDG 737-700

No need to do this....

First, your ini shows that you have two missing controllers:

Quote

F=<< MISSING JOYSTICK >>
E=<< MISSING JOYSTICK >>

There are no GUIDs associated with these, but you still have quite a few assignments those controllers - I suggest you clean-up your inii by removing them.

Restore the full ini and remove the TBM from its profile, i.e. change

Quote

[Profile.TBM930]
1=TBM 930 Asobo
2=TBM 930 01 Livery

to

Quote

[Profile.TBM930]
1=Not used

and see if you get the same issue.

Are you using a VRInsight device?

 

Link to comment
Share on other sites

Yes I'm using a VRInsight MCP model 1 Boeing.

Since MSFS I am no longer assigning in LINDA but everything in FSUIPC.

Only VRInsight MCP is assigned in LINDA.

Done as you suggested. Problem does not occur anymore.

I can use other programs and FSUIPS Assignment menu can be used.

Throttle Daher TBM930  does not react on assigned axis of Honeycomb Bravo

Jacob 

Link to comment
Share on other sites

10 minutes ago, VBV234 said:

Done as you suggested. Problem does not occur anymore.

It, then that indicates that something in your TBM profile is causing this issue.
I have just looked at your ini again and it is a bit of a mess....you have this a the top, that is not part of any section:

Quote


0=Saitek Pro Flight Rudder Pedals
0.GUID={FB245FC0-E5E4-11E9-8001-444553540000}
A=Saitek Pro Flight Rudder Pedals
A.GUID={FB245FC0-E5E4-11E9-8001-444553540000}
B=Pro Flight Cessna Trim Wheel
B.GUID={FB25E660-E5E4-11E9-8003-444553540000}
C=Saitek Pro Flight Yoke << MISSING JOYSTICK >>
C.GUID={FB260D70-E5E4-11E9-8006-444553540000}
D=Logitech RumblePad 2 USB
D.GUID={FB263480-E5E4-11E9-8008-444553540000}
E=Alpha Flight Controls
E.GUID={B7226050-FB11-11E9-8001-444553540000}
4=Alpha Flight Controls
4.GUID={B7226050-FB11-11E9-8001-444553540000}
F=Bravo Throttle Quadrant
F.GUID={FF705280-FAE8-11EB-8001-444553540000}
2=Bravo Throttle Quadrant
2.GUID={FF705280-FAE8-11EB-8001-444553540000}
3=Logitech RumblePad 2 USB
3.GUID={FB263480-E5E4-11E9-8008-444553540000}

That needs to be removed. This is the [JoyNames] section that is used, which indicates missing devices:

Quote

[JoyNames]
0=Saitek Pro Flight Rudder Pedals
0.GUID={FB245FC0-E5E4-11E9-8001-444553540000}
2=Bravo Throttle Quadrant
2.GUID={FF705280-FAE8-11EB-8001-444553540000}
4=Alpha Flight Controls
4.GUID={B7226050-FB11-11E9-8001-444553540000}
A=Saitek Pro Flight Rudder Pedals
A.GUID={FB245FC0-E5E4-11E9-8001-444553540000}
B=Bravo Throttle Quadrant
B.GUID={FF705280-FAE8-11EB-8001-444553540000}
C=Logitech RumblePad 2 USB
C.GUID={FB263480-E5E4-11E9-8008-444553540000}
D=Alpha Flight Controls
D.GUID={B7226050-FB11-11E9-8001-444553540000}

F=<< MISSING JOYSTICK >>
E=<< MISSING JOYSTICK >>
3=Logitech RumblePad 2 USB
3.GUID={FB263480-E5E4-11E9-8008-444553540000}
 

You still have many assignments to those missing devices, which presumably were previously your Homeycomb Alpha and Bravo.

I have tried to correct these issues for you in the attached ini, so could you please try this: FSUIPC7.ini

Note that there are still some axis duplications that can cause issues, so please review these:
1. Throttle an PropPitch axes assigned twice in Axes.TBM930 :

Quote

[Axes.TBM930]
RangeRepeatRate=10
0=AX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=AY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
2=AR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=BY,256,D,4,0,0,0    -{ DIRECT: Throttle }-
4=BZ,256,D,5,0,0,0    -{ DIRECT: PropPitch }-
5=BR,256,D,5,0,0,0    -{ DIRECT: PropPitch }-

6=BU,256,D,13,0,0,0    -{ DIRECT: Mixture1 }-
7=DX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
8=DY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
9=BX,256,D,4,0,0,0    -{ DIRECT: Throttle }-
 

2, Throttle1 axis assigned twice in [Axes.FBW 320 NEO]:

Quote

[Axes.FBW 320 NEO]
RangeRepeatRate=10
0=AX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=AY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
2=AR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=BX,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
4=BY,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
5=BR,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
6=DX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
7=DY,256,D,2,0,0,0    -{ DIRECT: Elevator }-

3. Throttle2 assigned twice in [Axes.CJ4]:

Quote

[Axes.CJ4]
RangeRepeatRate=10
0=AX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=AY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
2=AR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=BX,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
4=BY,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
5=BZ,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
6=BR,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
7=DX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
8=DY,256,D,2,0,0,0    -{ DIRECT: Elevator }-

4.  Rudder assigned twice in [Axes.Drone]:

Quote

[Axes.Drone]
RangeRepeatRate=10
0=AY,256,D,3,0,0,0    -{ DIRECT: Rudder }-
1=AR,256,D,3,0,0,0    -{ DIRECT: Rudder }-

2=BY,256,D,4,0,0,0    -{ DIRECT: Throttle }-
3=DX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
4=DY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
 

So, download that and and review and correct those axes assignments mentioned above, if needed, and then try the updated ini.

John

Link to comment
Share on other sites

Sorry, missed this one:

2 hours ago, VBV234 said:

Throttle Daher TBM930  does not react on assigned axis of Honeycomb Bravo

The throttle in the TBM930 has always been problematic...I think the throttle is/was working, when assigned correctly, but the animation of the throttle in the VC was broken, i.e.  it works but no the animation. I believe there was a dux if using the TBM improvement mod, possibly in conjunction with an XML file update. However, I am not sure if the current status, with or without the mod. In fact, I can't use the mod anymore as most of the aircraft isn't visible any more when using this!

Here are the references to this issue when previously reported, although I am not sure how relevant they are since SU10, but worth reviewiing:

 

 

 

 

John

Link to comment
Share on other sites

John,

I Started with the ini  you send me.

Deleted number of lines and reassigned some axes.

With the changed settings I was able to make a short flight.

After landing and switching off the engine the problem occurred again

Menus in FSUIPC not accessible en other windows programs did not react.

Back in the MSFS main menu everything worked again.

Reloaded the plane ... error occurred

Load another plan .... no problems.

After that I deleted the FSUIPC.ini and started all over.

I made most of the assignments for the TBM930 without any problem.

Throttle is assigned in the Honeycomb Bravo and works, but without animation in the cockpit.

Starting the engine according to the manual was also no problem

Finished the flight, switching off the engine is not going well. I have to look further in the assignments.

For me it is clear that continuing with this new ini is the easiest way.

I am convinced this way is less time consuming than debugging the old ini.

Another advantage is that everything is cleaned up and assigning in FSUIPC goes faster and faster after all these years 😀

Thank you very much for your effort.

Kind regards

Jacob

 

 

Link to comment
Share on other sites

Ok, thanks for the update, but I really have no idea what can be causing this:

1 hour ago, VBV234 said:

After landing and switching off the engine the problem occurred again

Menus in FSUIPC not accessible en other windows programs did not react.

Back in the MSFS main menu everything worked again.

Reloaded the plane ... error occurred

Load another plan .... no problems.

The only time I have seen such issues is due to logging, i.e. so much is written to the log that it can prevent UI interaction (due to resource hogging). Other than that, I cannot see how this can occur. Except if there is a resource locking issue somewhere, but if that is the case I would expect this to occur and have been reported a lot more often (this is the first time I have heard of such issues!).

1 hour ago, VBV234 said:

After that I deleted the FSUIPC.ini and started all over.

I made most of the assignments for the TBM930 without any problem.

Throttle is assigned in the Honeycomb Bravo and works, but without animation in the cockpit.

Starting the engine according to the manual was also no problem

Finished the flight, switching off the engine is not going well. I have to look further in the assignments.

For me it is clear that continuing with this new ini is the easiest way.

I am convinced this way is less time consuming than debugging the old ini.

Ok, makes sense. You can use the old ini to see what the original assignments were and duplicate/copy as needed. Would be interesting to see if this issue occurs again, and if so what assignment/ini file change provoked this....

John

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.