Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. Okay. The first test result with FSUIPC uncompressed got exactly the same problem. FSUIPC is simply not getting loaded, and it is never actually run. SimConnect crashes by calling it when it isn't there! It's looking like time to call in L-M support on this. Unfortunately I cannot repro it here at all, so can you guys please report the problems and what I've said about it. I'll look for the new thread there and add to it if needed. Pete
  2. Hmm. Another variation -- perhaps the opposite of most of the others. Curiouser and curiouser ... Has anyone here asked L-M to check this at all? If not I might have to, because it must be something they've changed. Pete
  3. Can you get reverse working for a default aircraft? I suspect the Aerosoft one only works with the "Throttle Decr" control (as instigated by the F2 keypress). But hopefully other Aerosoft users can chip in. Pete
  4. Offset 1F044 happens to be the address of the function called initially by SimConnect just after it loads FSUIPC4, so FSUIPC hasn't even started. In fact, if it is crashing there, it means that the loading of the DLL failed to happen, yet SimConnect is still trying to call the function where it would have been! This points to a problem in SimConnect or the DLL.XML file(s). Unless I can reproduce it here I can't really help further on that crash. Others here seem to be getting a hang instead, but I guess that might depend upon what rubbish was present to that address when execution is attempted, so maybe it's the same thing ... Hoping to be able to reproduce it, somehow ... [LATER] I'm wondering if something has been changed in SimConnect that somehow stops the auto-decompression of FSUIPC after Windows loads it. Maybe one or two volunteers here would test and uncompressed copy of the DLL for me, just to check this. Send me an email -- petedowson@btconnect.com. I don't want it to be made available generally for security reasons, but if this is the problem I'll need to look for a solution or ask L-M what's changed to do this. Pete
  5. Please see the other thread, nearby, on exactly the same topic. I posted another check to make there. Pete
  6. I cannot reproduce this problem here at all. I've found in the past that the order of loads in the DLL.XML file can be critical FSUIP4.DLL generally likes to be the last entry in the copy of DLL.XML in the AppData\Roaming folder -- excepting the Active Sky connect module (as_btstrp) which needs to come later. Reinstalling FSUIPC recopies the exact same DLL into the Modules folder but it does also check that it is still in the best place in the DLL.XML file and if not moves it. So when P3D won't run, check the DLL.XML and see if something has changed the order again. Also check that there is no entry for FSUIPC in the ProgramData folder version of DLL.XML. Pete
  7. Sorry, but that makes no sense. Reinstalling FSUIPC does nothing. It changes nothing. Replacing FSUIPC by the same FSUIPC makes the next load completely identical. I am using FSUIPC 4.959 with no troubles on P3D3.4 Hotfix 2 release. Can't you at least post the log file from the Modules folder after the hang? Pete
  8. Use JoyLetters and let it auto assign the letters. That's by far the easiest way. It sounds like you are changing the numbers in the wrong place, and the GUIDs are taking precedence. The joy letter system takes all the pain out of Yes, that is better if you want to select your own, more meaningful letters, as you have done. If you leave it on Auto it will assign A, B, C etc. Leaving it on Auto afterwards is good for when and if you add more devices and want it to continue to assign the next available letter, but if you are choosing your own, then set it to no and do the new assignments yourself. Pete
  9. Odd. I've never used that x.x.x.x format. I'll check to see what has happened. If correctly uses the x.xxx format for the Product Version below! [LATER] Well, I've just checked, and both File and Product versions are defined identically, so that's a complete mystery to me! [LATER STILL] Ok. Spotted it. Will be fixed next increment, whenever. Pete
  10. No. That cannot be true because I use TripleUse all the time with no such problem. This line in the Lua program explains why the release is ignored: event.button(joy, btn, 1, "buttonpress") The "1" parameter means "press". To have an event of release as well it would need to be 3, not 1. So, it sounds more likely related to the view control(s) you've assigned. Try using FSUIPC's logging to see what is going on. Pete
  11. Windows is supposed to merge blocks to provide such a block when requested. I'm not sure if that's something which has to be allowed by the request of by some system setting. Don't forget the memory address you see isn't the true one, it all goes via page tables which can change the used addresses without changing the "real" (hardware) ones. I think you can actually force Windows to do a memory "defrag", but I think that would cause pausing. Maybe that could be done as an add-on control, so you instigate it and hence expect the pause. The problem with monitoring the sizes of blocks and finding the largest is the processing time involved in doing so. I'd be worried about adversely affecting performance. However, I might look into it, as an option. Pete
  12. That sort of freeze is almost always due to driver problems -- nothing else has enough privilege to freeze or crash anything but that current process. For FSUIPC information you could see how far the FSUIPC log file got before the freeze occurred. Pete
  13. That log only shows a successful run with FSUIPC closing normally. What do you mean by "too many axes"? 1, 2, 3 ... 64? Are you sure it isn't just one specific controller who's driver is hanging? Try to isolate which action actually causes the problem. And please, when supplying a Log file, show the one applicable to the problem being reported. Pete
  14. I don't know of any limit. Do the programs which don't start truly don't start, or actually start and fail to connect? Do they all work if running Starter.exe directly? Why not start them all with WideClient rather than use Starter.exe? Pete
  15. Not all add-ons support Mouse Macros. In fact most do not. As the manual also says, that will only appear if it works, but there are more variations you can assign. That must be a function of the way that VC is coded, or an interaction with your video drivers. It is certainly nothing in FSUIPC. You already tested it by TAB and proved it will not work! Pete
  16. Just run the Installer again. You can only register there, when it gives you that option. There is a document about Installing and Registering included in the ZIP file. I strongly suggest you read that! Pete
  17. You need to write a short Lua plug-in, to read and check the aircraft name and use the ext.run function to run the program. Pete
  18. Yes. You'd need to assign the trim wheel to send its value to the Lua plug-in, which could be one already loaded and waiting on such an event -- loaded perhaps by an [Auto] entry in the INI file, or one loaded by the actual movement of the wheel (less efficient and maybe less responsive). In the former, and better, case, you'd send the value using the LuaValue control. The plug-in would check the AP status (read an offset) to determine what to do -- to send it to the trim axis in FS or not. To display it first you'd use any one of the display options provided in Lua. Pete
  19. MOVED TO SUPPORT FORUM -- THIS IS NOT A USER CONTRIBUTION! Events are NOT offsets! Events are actions, requests, or controls. Offsets are locations in memory which provide or accept data. You can send controls via offsets by writing control number and parameter to offset 0x3110. Please look it up in the Offsets Status list. Pete
  20. You seem extremely confused! Have you not even downloaded FSUIPC yet? There are links to the main download site on the SimMarket page where you purchase the registration. Or you can download it from the Download Links subforum above. FSUIPC is of course built into the installer. You just download FSUIPC4.zip. Instructions are inside the ZIP! There are just two documents and the Installer in the ZIP file. You have to download it like everyone else -- that's how you get FSUIPC and install it!!! Pete
  21. Er, I've never heard of "FSX Stream". Do you mean FSX-SE, the STEAM edition? "Stream" means an entirely different thing altogether -- when you don't actually have it installed on your PC but just get bits as needed off the Internet -- called "streaming", quite common with songs and videos. And if you mean FSX-SE, then, no you don't need any different version. As it clearly says in all the download places and in the documents, FSUIPC4 is for FSX, FSX-SE and Prepar3D. Pete
  22. Is that for increment or decrement? Whilst providing the control number as a string does work, it is less efficient than giving the number directly, as it saves a step in the work the Lua interpreter has to do. In other words, just ipc.control(84134, 327) would be better. Pete
  23. What is that link you added supposed to be for? Why is this rentitled "FSX Stream"? There is absolutely nothing related to streaming in FSUIPC, nor in FSX as far as I'm aware! Are you trying to pirate software? After downloading the current version of FSUIPC and running the Installer, as instructed in the included document, then it will run. It doesn't need "activating". If you want to use the user facilities, not just use it as an interface for some application program, then you need to buy a Registration. Again, details are included in the document supplied. Pete
  24. The list of controls at the end includes names, from which you need to find the one which sounds applicable to what you want to do. I think there'll only be one -- I think the difference between Increment and Decrement will be determined by the parameter, not the control number. The way the control number is defined is as a "base" or starting number + a decimal number. The starting number is defined at the start of the list. Just add the two numbers together. I don't have or use PMDG aircraft so I can't be more explicit, but take another look with what I jut said in mind and it should all come clear. (There are examples in User Contributions subforum for the 737NG I think.) I don't know what the parameters are for increment and decrement. I think the increment may be obtained with something simple like 0 or 1 as parameter, but decrement isn't something easy like 1 or -1. There are examples in other postings here, applicable to 737NGX or 777X -- they use the same parameters for these even if the control numbers are different. I think the parameters are based on the parameters the gauge itself would get from using the mouse (left click / right click), and those codes might be in the .h file too. If they are in 'hexadecimal', with maybe 8 digits, you can enter those in FSUIPC's parameter box by preceding them with an 'x' (eg 'x80000000'). And you might find more folks who can help more directly in the PMDG forum. Pete
×
×
  • 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.