[Long loading time P3d 3.1 + FSUIPC4 4.949]

Hi Pete,

It took a long time, but I have identified the program eating the CPU cycles as the GoFlight bridge (GFDevP3d.exe).

I mean that without having this program started automatically (via the exe.xml), then the loading of the scenery is normal.

It is probably related to the high number of GoFlight devices as not all of them are recognised in the GoFlight config program (although they all light up at boot time). It seems that the new Intel USB 3 controller does not accept as many devices than before (I did not have this issue with my previous machine).

Thanks again and have a great holiday break.

Patrick.

 

 

Patrick, it is a known fact that GF doesn't work well with USB3. That's why before building my new system I researched the latest mobos for enough internal USB2.0 connectors. ASRock mobos usually still have 3 of them (internal connector can accommodate x2 USB ext.). So I added 3 external usb2.0 boards and used them for connecting hubs with my GF gear. 

 

Dirk.

[FSUIPC4.95 crashes P3Dv3.2]

 

It's the list of weather stations for weather set in SimConnect and for reporting weather on ATIS and the like It is an essential file which is regenerated automatically, and updated by web downloads.

 

 

No, but it will be used if there. Why remove it?

 

 

Only the last two might have fixed it, not the others. But without a log file from a problem load to look at there's no way I can tell!

 

Pete

 

 

Pete, which file exactly do you want me post? 

 

Which is p3d crash log file? Where is it?

 

Thanks,

Dirk.

[FSUIPC4.95 crashes P3Dv3.2]

Now, this is how I've fixed this crash at first P3D launch:

 

1. I ran SimConnect.msi installers from the redist folder

2. I removed SimConnectP3D3.dll folder (ver. 3.0.0.13948 from FSUIPC4.95 install)

3. I deleted *.wx files from Documents\Prepar3D v3 Files\ folder

4. I switched off wxstationlist.bin file in Weather folder

 

Only after that P3D launches seamless on the the first run after pc reboot.

 

Do I still need SimConnectP3D3.dll and wxstationlist.binfiles?

 

Thanks,

Dirk. 

[FSUIPC P3D Crash on Startup]

 

BTW why are you still using an old version of P3D? Best to keep up to date and bug fixes are on-going.

 

Prepar3D.exe version = 3.0.10.14945

 

Pete

 

Sorry Pete, I think I misinterpeted your post, you rather pointed to the old version of Prepar3D.exe that you found in Beavis's log, didn't you?

 

Dirk.

[FSUIPC4.95 crashes P3Dv3.2]

If I run all SimConnect.msi files in redist folder, do I need SimconnectP3D3.dll in Modules folder at all?

 

Thanks,

[FSUIPC4.95 crashes P3Dv3.2]

Luke,

 

I renamed wxstationlist.bin to wxstationlist.bin.off and removed all *.wx files in Documents\Prepar3D v3 Files folder. Rebooted my PC and launched P3D - still the same problem.

 

My FSUIPC version is 4.95 and Prepar3D.exe is:  

Prepar3D.exe version = 3.2.3.16769

 

Thanks,

Dirk.

 

PS: Don't I need wxstationlist.bin at all? Does it ever get regenerated?

[FSUIPC P3D Crash on Startup]

BTW why are you still using an old version of P3D? Best to keep up to date and bug fixes are on-going.

 

Prepar3D.exe version = 3.0.10.14945

 

Pete

 

 

Fehleroffset: 0x52b38300

 

 

I'm having a similar problem on the first launch of P3D with the freshly installed FSUIPC after each reboot of my PC as posted in this thread:  http://forum.simflight.com/topic/81463-fsuipc495-crashes-p3dv32/

 

Pete, please note the latest version of Prepar3D.exe version = 3.2.3.16769    not     "Prepar3D.exe version = 3.0.10.14945" 

 

And it's been there since 16-03-07. Can that be the key to my problem posted in my thread?

 

Thanks,

Dirk.

[FSUIPC4.95 crashes P3Dv3.2]

I'm having a weird problem with FSUIPC4.95 installation crashing my vanilla P3Dv3.2 in Win10 x64 on each first launch of P3D. It took me 4 days of research, multiple uninstalls and Acronis recover to pin this problem down to FSUIPC4.95 install. I would never imagine FSUIPC could to that to me.   ))

So, each time when I reboot my pc and launch P3D first time I hear some Win10 system chimes followed by Errpr: "Prepar3D exe has stopped working". I close the program and launch P3D again. Second launch produces only the chimes but no Errors and all seems to work OK after that, no matter how many launches I make. Soon as I reboot - the story repeats the same. Very weird.

 

If I edit FSUIPC entry in DLL.XML to Disabled>True< the problem is gone, no chimes no messages. Please help.

 

Thanks,

Dirk.

[Help with PMDG 777]

I'll try to answer myself by quoting this from GIT User Guide:

 

 

Mouse Click Events are available when a developer has created an aircraft gauge or gauges using the C++ programming language.

 

The gauges will have areas that respond to various types of mouse clicks and in turn trigger events or custom code to execute.

[Help with PMDG 777]

Alas, I fail to understand the difference yet. See, If I can use mouse click macros facility in FSUIPC to control most of the functions in iFly why do I necesserily need iFly2fsuipc.exe running in the background to be able to manipulate the same controls via FSUIPC? Any exe running in the background is such a nuisance, and there's nobody who's come up with a direct solution but iFly2fsuipc...

 

 

Thanks,

Dirk.

[Help with PMDG 777]

Yes, they added additional controls to the normal FS list, numbering them beyond those pre-assigned in FS. So they are "non-FS" controls in the sense that FS doesn't know those numbers, but they use the same mechanism, posting via message queues using Windows WM_COMMAND messages.

 

Pete

 

Thank you very much, Pete.

 

Dirk.

[Help with PMDG 777]

Actually most of the sub-systems in the NGX are dealt with by additional FS controls which PMDG added...

 

The SDK lists all the extra (non-FS) controls added to the normal FS range -- and accessed in FSUIPC by the <custom control> assignment and the control number -- as well as mapping all the read-outs so cockpit builders can show them on their hardware displays.

 

Are those "additional FS controls" by PMDG that you mentioned are the same "The SDK lists all the extra (non-FS) controls added to the normal FS range" in context?

 

Thanks,

Dirk. 

 

PS: In PMDG I use those controls with FSUIPC actually, just trying to get a general notion, thanks!

[Help with PMDG 777]

Pete, in case with iFly's 737ng, why does it need some iflytofsuipc.exe to talk to FSUIPC, whereas PMDG's 737ngx understands controls sent from FSUIPC directly? And the both use L:vars in their programming if I articulate it right (at all). Does this mean PMDG had coded their lvars so that they could be handled by FSUIPC directly and iFly had not? Sorry, if I'm having trouble even with the terminology.  

 

Thanks,

Dirk.

[Logging LVARs?]

All is clear, thanks.

 

Dirk.

[Logging LVARs?]

Assign a button/switch temporarily to the FSUIPC4-provided "List Local Panel Variables" or

words to that effect.

 

 

Paul, this is what I expected starting the thread. 

 

What exactly is "...or words to that effect".

 

Thanks,

Dirk.

[Logging LVARs?]

Is it possible to log LVARs used in a panel? I'd like to manupulated knobs and buttons in ORBX's Lancair IV-P with my hardware. I think they had used LVARs in the programming. If it is possible, could you please give me a single example of how to do that.

 

Much thanks,

Dirk.

[PMDG: How to assign "A/P disengage" to joystick button?]

 

If you are using profiles in FSUIPC you can have all the assignments for different profiles in separate INI files. This facility was added recently and is described in a new document installed in your FSUIPC Documents folder.

 

Pete

 

Which document, Pete? I was looking for "Profile" in both FSUIPC4 User Guide and FSUIPC4 for Advanced Users and couldn't find anything about separate ini files.

 

Thanks,

Dirk.

[Aerosoft MCP747 driver?]

Going through FSUIPC4 User Guide I've just found that FSUIPC4 can recognize inputs from Aerosoft MCP747. i bought this panel long long ago and I thought it didn't work with Win7 x64 + FSX + FSUIPC4. Can anybody point me to the link with the working driver if it exists (and now I guess so).

 

Thanks,

Dirk.

[PMDG: How to assign "A/P disengage" to joystick button?]

If you are using profiles in FSUIPC you can have all the assignments for different profiles in separate INI files. This facility was added recently and is described in a new document installed in your FSUIPC Documents folder.

 

Pete

 

Very interesting and can be very useful, I'll go through it.

 

Thanks,

Dirk.

[PMDG: How to assign "A/P disengage" to joystick button?]

Awesome, thank you. I'm surprised how I can play now with these numbers and lua expressions without any knowledge or understanding. I've never studied any basic programming,  can't write a single string or a logical expression, however during yesterday I managed to assign all my GF buttons and rotaries (8 panels) and some joystick buttons to internal pmdg737ngx functions from scratch just using the above information, and I did that in a few ways (fsuipc controls and lua files) for comparison. I just can see some similar patterns that I shuffle for my needs, is it what is called 'hacking'?

 

Is there any performance benefit of using Custom control facility in FSUIPC vs. properly written lua file with the same functionality? Lua is very convenient, as you can store all the controls in one file, and not buried in FSUIPC.ini that has already too much in itself and potentially can be modified over time by newer versions.

 

Thanks,

Dirk.

[PMDG: How to assign "A/P disengage" to joystick button?]

Now FSUIPC control for AP1 disconnect works properly with the following:

 

Value

<70636>

 

Parameter 536870912

 

I tried the above Parameter from the Linda's Lua for 737NGX (as suggested by Ian P). I have no idea where they took it from, but obviously it is not in PMDG's SDK docs.

 

Thanks,

Dirk. 

[PMDG: How to assign "A/P disengage" to joystick button?]

One more question, please:

 

Is it ok to have both Lua AXE (airbus) and Lua PMDG737 entries in [Auto] section of FSUIPC? Can it potentially affect performance or create any confusion as both lua files in Modules folder are read? Is it better to remove an unused lua from Modules folder?

 

Thanks,

Dirk.

[PMDG: How to assign "A/P disengage" to joystick button?]

Pete,

 

Unfortunately AP disc / AT disc logic doesn't work right via <custom control> assigned in FSUIPC as per my experiment above. To some reason it works only on the first instance: you press AP discon button, the warning goes off, you press AP discon again and it extinguishes. Then if you engage AP and press AP discon button again the warning goes off and extinguishes on its own without waiting for the second AP discon button press.

 

I checked the correct logic through internal PMDG key assignments and also with this lua:

 

 

-- PMDG737 lua --

 

function NGX_AP_soft_disconnect ()

 

    ipc.writeLvar('ngx_switch_1004_a', 100);

    ipc.control(65580, 536870912)

    ipc.sleep(150);

    ipc.writeLvar('ngx_switch_1004_a', 0);

 

    DspShow (" AP ", "soft")

 

end

 

event.button("B", 6, 1, "NGX_AP_soft_disconnect")

 

The latter two always wait for the second press on AP discon button. Same inconsistency shows up with ATHR disconnect.

 

Thanks,

Dirk. 

[PMDG: How to assign "A/P disengage" to joystick button?]

I really need an example of how to find a reference to the parameters (0 and 1) that I used rather instinctively in the above example either in PMDG_NGX_SDK.h or PMDG+737NGX_SDK+10FEB12.pdf documents. It will help me to understand how they are used in other more complex controls. Please give me an idea with this or similar.

 

Much thanks,

Dirk.

[PMDG: How to assign "A/P disengage" to joystick button?]

Great! 

 

In the first example (and I guess in case with AT too) you need to enter parameters as follows:

 

<70636>

Parameter 0

 

Control sent when button released

<70636>

Parameter 1

 

 

In this case the yoke disconnect logic will work right: the  red warning/alarm will light/sound then extinguish.

 

Thanks,

Dirk.