-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
P3D Ver 1.3 + FSUIPC 4.812 - Crash in Multiplayer
Pete Dowson replied to FSMP's topic in FSUIPC Support Pete Dowson Modules
Well, really, because L-M said the older LIB would still be okay, it shouldn't have made any difference. but then, without it, how is everything working well with the FSX SimConnect DLLs? It's weird. I'll try the method where I don't do the re-linking. It didn't make much difference before, but I've no other ideas. After that we're dependent on L-M help I think. [LATER] Here: FSUIPC4812e Pete -
P3D Ver 1.3 + FSUIPC 4.812 - Crash in Multiplayer
Pete Dowson replied to FSMP's topic in FSUIPC Support Pete Dowson Modules
Okay -- try SimConnectP3D.zip Pete -
P3D Ver 1.3 + FSUIPC 4.812 - Crash in Multiplayer
Pete Dowson replied to FSMP's topic in FSUIPC Support Pete Dowson Modules
With earlier versions of P3D their installer installed the ESP version of SimConnect I think. I'm surprised they withdrew that. Fixing it by removing SimConnectP3D.dll seems to suggest that there's some change in their static libraries between 1.2 and 1.3 that makes the 1.2 library incompatible with MultiPlayer mode. Odd, though, that it is okay with the FSX SP2 version. I'll build a version of SimConnectP3D.dll with the 1.3 static library for you to try. I'll try and get it posted tonight or in the morning, as I'm then away till Monday. Regards Pete -
Oh dear. You will get no support from me if you retreat to older versions. Why not try 4.812d as I asked? Am I wasting my time? Okay, thanks. I'm away till Monday in any case. Regards Pete
-
You cannot have a minimum value higher than a maximum value! Maybe it's a language problem? "Minimum" means "smallest" or "lowest". "Maximum" is the opposite -- highest. Also, with numbers, NEGATIVE numbers are LOWER than positive numbers (because 1 - (-1) is +2, for example, showing +1 is higher than -1). You can only calibrate with correct order, low to high, left to right in the display. Why post your axis assignments? That's nothing to do with calibrations! Pete
-
P3D Ver 1.3 + FSUIPC 4.812 - Crash in Multiplayer
Pete Dowson replied to FSMP's topic in FSUIPC Support Pete Dowson Modules
Odd, it didn't crash at all here, but I didn't try many times. In my case it was never paused when MP mode was entered. Does your log show ihe double re-connection? It shouldn't, now. BTW I've had to make another build for a different reason, so if you want to supply any specific data please use FSUIPC4812d Pete -
I've tried it here on a different system, with ASE, and there does seem to be a timing problem during initialisation. It always works (with AS2012) on my main cockpit system, but it appears to be failing to initialise the ASE/AS2012 link about 50% of the time on my lesser system. So, I've changed the way it initialises and checks for ASE/AS2012. Test version 4.812d, available via this link: FSUIPC4812d.zip makes it connect 100%. Perhaps you can try that first? Regards Pete
-
No. There's been no reports. The only mention was from a person who says that its been like that for him since September 2011, which was five months before 4.80, but he wouldn't even supply any logs or other information so I couldn't help him and he went off in a huff. I cannot support folks who go back to old versions so they better not come here. If I get no reports of errors or problems I cannot investigate. And I use FSUIPC 4.812 here with AS2012 and Radar Contact regularly and it works fine here. If you or any others want me to look at things I need information, logs, configuration. I would need to know how to reproduce the issue. Regards Pete
-
P3D Ver 1.3 + FSUIPC 4.812 - Crash in Multiplayer
Pete Dowson replied to FSMP's topic in FSUIPC Support Pete Dowson Modules
Please try 4.812c, from here: FSUIPC4812c. Thanks, Pete -
Okay. There is no Axis control input setting reverse. The AXIS_THROTTLEn_SET contorls have no reverse zone whatsoever -- -16384 is idle and everything above that to +16383 is forward thrust. Therefore it is something else doing it, possibly something in the NGX. I expect it would still occur if you didn't use FSUIPC as I think that's out of the equation. Pete
-
Since you have no axes at all assigned in FSUIPC except to the FSX "steering set" control, which FSUIPC doesn't process (because it has its own tiller control-- there was no FS steering control till FSX), FSUIPC is not at all involved. The calibration you've done for steering tiller there isn't going to be used because there's no input for it, unless it is coming from some LINDA action. So, sorry, you are asking the wrong person. What you are seeing and using is not FSUIPC itself. Regards Pete
-
Because you have the filter option checked for Throttle1 and not for Throttle2, that is why. All these things are described in the User Guide, and there ARE pictures too. I tohught you liked pictures? Why not look these things up? Why "non-axis" when i explicitly asked you to log axis events? Please do read the words I write, or this is going to take weeks. As it is I've got to go out soon, so it will probably take another day now. Then I'm away over the weekend, from Friday. So i saw. So how is it assigned? Obviously this reverse engagement is triggered by that, whatever it is. Have you asked PMDG support, since it is only happening with their aircraft? There is a section in the User Guide which tells you that. Why not use the documentation? If you don't want to use FSUIPC, just delete the FSUIPC4.DLL from the Modules folder. If, on the other hand you want to start again with all your settings, just delete the FSUIPC4.INI file. Pete
-
Saitek Yoke FSX response curve
Pete Dowson replied to airdragon1953's topic in FSUIPC Support Pete Dowson Modules
I don't understand what you means, really. It is faulty if, as you said, as you pass the 45 degree yoke position, it suddenly flips to the 180 degree position. There should be no such sudden change of input, it should be smooth from one pend to the other. Calibration is the process of matching a real world lever/axis numerical input range to a desired simulator one. That's what it is for. Just follow the numbered steps. I don't understand your continual need for some sort of assurance. The only difference between FSUIPC's calibration methods and those provided by game controller applets is that it is numerical and more precise. Regards Pete- 5 replies
-
- response calibrationyoke
- yoke responsiveness
-
(and 1 more)
Tagged with:
-
Saitek Yoke FSX response curve
Pete Dowson replied to airdragon1953's topic in FSUIPC Support Pete Dowson Modules
Sounds very much like a faulty yoke. There's not a lot you can do with a seriously faulty piece of hardware. But certainly try calibrating properly. There are numbered steps for that in the User Manual, in the chapter on calibration. just follow them. Pete- 5 replies
-
- response calibrationyoke
- yoke responsiveness
-
(and 1 more)
Tagged with:
-
A couple of oddities showing in that. the Profile being used for the 737 NGX has: UseAxisControlsForNRZ=No even though you changed this for default assignments (no profile). I think most NGX users find that they need this set to "Yes". The pictures you showed earlier was with an Axis section for one Profile but a Buttons section from a different profile, and NEITHER of them were from your main NGX profile "Twee motoren". In fact i cannot relate your INI file to the pictures you sent originally at all. Are you sure they are fromthe same FSX installation? Also you have filtering enabled for throttle 1 but not throttles 2. Why? I'd generally recommend no filtering at all. Axis event logging, check. Don't bother about console window -- I can't see your PC from here and I don't want a picture, but a log. Shutting down or starting up, whichever. And you haven't said WHEN exactly the reverser engages (what switch -- starter, fuel to idle, what?). Nor have you said how you operate the starters. Regards Pete
-
P3D Ver 1.3 + FSUIPC 4.812 - Crash in Multiplayer
Pete Dowson replied to FSMP's topic in FSUIPC Support Pete Dowson Modules
Yes, very helpful. Thanks! It certainly occurs when the SimConnect events stop arriving in FSUIPC for long enough. FSUIPC thinks it has stalled and attempts re-connection. The method used, which works in all FSX, ESP and previous P3D versions appears to be defeated by some change in 1.3 which i cannot fathom at present. I'm changing the way FSUIPC attempts to do that restart. Please look out for 4.815 which I'll be putting up in the Download Links subforum either later today, or more likely, tomorrow. [sEE EDIT BELOW] Meanwhile you might like to try changing this parameter in the FSUIPC4.INI file: SimConnectStallTime=1 That default value sets the limit before a stall is determined to 1 second. Try increasing it to a value which accommodates whatever the stall time is for the multiplayer switching. This is only a temporary measure to be sure that I'm tackling the correct problem. [EDIT] I've uploaded a test version, 4.812b. Here: FSUIPC4812b. Please try that and let me know. Regards Pete -
Is this with a default aircraft too, or only the PMDG NGX? It sounds very much as if you have dual assignments to the same throttle and one of them is not correctly calibrated, though why this is affecting things only when you start or shut down is a bit odd. When does it occur -- when you operate the fuel cutoff/idle levers (the start levers)? How are those assigned? How have you assigned reversers? I cannot advise without further information. Please show me your FSUIPC4.INI file, and also enable Axis logging in FSUIPC options and show me the part of the log where you start the engine. Pete
-
P3D Ver 1.3 + FSUIPC 4.812 - Crash in Multiplayer
Pete Dowson replied to FSMP's topic in FSUIPC Support Pete Dowson Modules
Thanks. I notice the code offsets were with 4.812. I'll see if I can locate them in my current build, but if not I may ask for you to supply again with a different build. (I MUST remember to save the compiler's MAP file for released builds! I used to do it regularly, but have fallen into bad ways! :-( ). Pete -
Ouch ouch ouch! So suspending all the Lua threads whilst the part otherwise avoided by AutoScanDevices=No doesn't stop something going on still. I can only think that LINDA or its Lua plug-ins start other threads which, of course, FSUIPC is not aware of and therefore cannot suspend. I don't think I've any other things i can try. Looks like the AutoScanDevices=No is here to stay for LINDA users, or at least those with the more complex setups. I suppose it isn't too disadvantageous -- it simply means you can't add or move devices whilst Linda and PMDG NGX are running, but you can otherwise by using the reload buttons. If i do think of anything else I'll add details here. Regards Pete
-
Well I've made changes in FSUIPC to add the Modules\DLL path to the "PATH" environment variable, instead of changing the search directory. I'm testing that today. Then folks shouldn't need to move any files around. The reason this did not occur to me before is that the DLL search directory list is local to a Process, so the FSUIPC action cannot possibly change the directories searched by RXPGN1AE.exe. It could only affect and RealityXP gauges or DLLs actually running inside FSX. The mention of RealityXP software being an EXE misled me quite siginificantly I'm afraid. The software must have parts inside FSX as well. I've uploaded a test version, 4.812b. Here: FSUIPC4812b. Please try that and let me know. That should work okay with the RealityXP stuff left as they were. Regards Pete
-
Aha! This implies that the search path for DLLs used by the FSX process is being explicitly set by something in RealityXP's software. Windows searches for DLLs in a number of places, in order, and as follows: The directory from which the application loaded. The directory specified by a call to "SetDllDirectory". The system directory. (Windows' "System32"). The 16-bit system directory. (Windows' "System"). The Windows directory. The directories that are listed in the PATH environment variable. FSUIPC changes number 2 in order to let Lua plug-ins find any DLLs they need. Those DLLs go into the Modules\DLL folder in FSX. This change is listed in the FSUIPC History as follows: So, there are a number of possible soltions to this. 1. Move DLLs needed by RealityXP to its own folder, or 2. Move DLLs needed by RealityXP to the Modules\DLL folder (create this folder if necessary), or 3. Move DLLs needed by RealityXP to the Windows folder or to the Windows\System32 folder, or 4. Make the FSUIPC action in setting the DLL directory optional, or 5. Make FSUIPC add the path to the PATH environment variable instead of changing #2 in the list. I'll experiment with option 5. Meanwhile you have a number of alternatives to try. Okay? Regards Pete
-
P3D Ver 1.3 + FSUIPC 4.812 - Crash in Multiplayer
Pete Dowson replied to FSMP's topic in FSUIPC Support Pete Dowson Modules
I'm afraid i've no idea about how to use multiplayer or even what it does. I've never used it on any version of FS, and really don't have time at present to learn. This information: you have should be sufficient for LM to see what is going on. It is deep into someplace in P3D which FSUIPC is not at all involved with, so I wouldn't know what to do in any case. Regards Pete -
How can there be more detail than providing the window handle in the 3rd parameter with a user message defined for you to receive and then process the dispatch? It's as per Simconnect documentation. and as I stated. If you don't understand it then it may be best not to use it? What part is not to understand? Regards Pete
-
Okay. I managed to get back on the case today, and I've added code now to suspend Lua program execution temporarily whilst FSUIPC re-scans joystick devices. Basically this should eliminate the need to use the AutoScanDevices=No setting and will enable you to reload assignments in FSUIPC options without crashing. At least this is what I think. FSUIPC4812a Could you please test it for me and let me know? I've not released it yet, so just download FSUIPC 4.812a, change the AutoScanDevices=No line back to 'Yes', and see if the crash is still avoided. Thanks! Regards Pete