Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
 View Profile  See their activity

  • Posts

    38,265

  • Joined

  • Days Won

    170

 Content Type 

Everything posted by Pete Dowson

  1. Pete Dowson
    What do you want me to say? You seem to have 3 good devices each with their own unique GUIDs: [JoyNames] AutoAssignLetters=No 0=CH PRO PEDALS USB 0.GUID={9825F3D0-47BB-11E7-8001-444553540000} 2=Mad Catz Pro Flight Throttle Quadrant 2.GUID={98261AE0-47BB-11E7-8003-444553540000} 3=CH FLIGHT SIM YOKE USB 3.GUID={982641F0-47BB-11E7-8008-444553540000} Isn't that what you wanted? Pete
  2. Pete Dowson
    No, it actually wasn't connected, though it might well have been had PMDG recompiled the 32-bit 17 year old library code they were using to access FSUIPC, because the facility that would have invoked uses that flag. That P3D fix is important for those wanting to use the FSUIPC mapped offsets to the PMDG variables, as that P3D facility is used for that. Pete
  3. Pete Dowson
    Not received yet. Perhaps it had a prohibited attachment filetype? Okay. I'll re-enable the offset reception for that. Not sure whether to do so for the 747 and 737 too. I might ask PMDG. H However, I would be a little worried about enabling it at this time because there is a knowwn bug in P3D4 with the Client Data request being made. I think tht might be fixed in the next P3D4 update, so I'll hang fire till that is available if you don't mind. I don't want a further host of complaints that FSUIPC5 causes PMDG aircraft to stop working! Pete
  4. Pete Dowson
    But there are no Joysticks listed at all! So FSUIPC couldn't read any -- and thre Log shows there were none detected. That's rather odd, but usually one way to force a rescan is to go into the FSUIPC Options and using the "Reload" button in the Buttons or Axes tabs. Unfortunately the FSUIPC5.Joyscan.csv file is missing. That's always needed. No need for HidScanner.log every time. But in this case, going by the Log, the scan file would have been effectively empty. The current version of FSUIPC5 is 5.101m and is working well for all other folks posting here. Pete
  5. Pete Dowson
    That is not what the offset is designated for. It was for VAS -- Virtual Address Space -- not actual memory! That would be something else altogether. I might consider adding another offset which provides the memory space currently used by P3D4 (which can exceed actual memory), but I'd need to investigare that and I really have no time at present. Ask again in about a month. Oh, and 8Gb is not enough if you plan to add much in the way of add-ons. Performance will start dropping off it it has to use paging to disk. Pete
  6. Pete Dowson
    That's Enrico Schiratti's "Dowson" page, not mine. It features the same links as the SimMarket purchase pages -- which all point back here. This Forum and its subforums are the only ones I control. The text on the Schiratti page is often out of date. It really needs re-designing anyway. Pete
  7. Pete Dowson
    No. no need. Just look at it. If it is full of SimConnect related errors then it is the same as for everyone else. How it then doesn't affect the flight is then a mystery. Maybe it's some differencein the SimConnect.xml file(s). Can you search for these? Is there one in the ProSim folder? There might be one in you user AppData folder for P3d4. If you can check, and maybe show any such and where they are it might help others. It could be something to do with the method used by the SimConnect library to communicate. Do you know if you have all SimConnect versions installed, or only the FSX SP2 one? (The FSUIPC4 Install log will show what is installed). Pete
  8. Pete Dowson
    What is the "main page"? Updates are in the Download Links subforum, as always. Pete
  9. Pete Dowson
    That would be best. Thank you! Pete
  10. Pete Dowson
    "new" LUA download? The Lua stuff installed for you in your FSUIPC Documents folder is the latest. There's no point in downloading anything else, you already have it. LUA doesn't change for P3D4. Pete
  11. Pete Dowson
    Good. And you have ProSim737.exe running on the same PC as P3D4? That would be double puzzlinf. i have RTM, SP1 and SP2/ACC versions installed, yet I still get ProSim's EXE failing. Have you checked the Prosim737.exe log file? Pete
  12. Pete Dowson
    I'm surprised the Real handles start at 5. That is weirdly coincident, and might be a clue ... Varying large values are what I would expect. So leaving it till I return on Tueday 20th June is okay? Pete
  13. Pete Dowson
    Er, FSUIPC recognises what as being a joystick? If all those devices are the old COM port style ones then FSUIPC will NOT see them as joysticks because they don't register in Windows as such devices! What PFC control panel? Have you installed PFCcom64.dll into the Modules folder? If your devices are USB devices then they are either seen by Windows as joysticks (as you say for at least one of them), or you need PFChid64.dll, not the COM DLL! Perhas you need PFChid64.dll You never need a true COM port these days. If your devices are COM devices there would have been an appropriate port driver supplied with them. I cannot support you if you stay with 5.101g. There' been no change which will upset what you have with that. You do not supply enough information, as you didn't before!vLike WHAT DLL 's are you using? Pete
  14. Pete Dowson
    Apparently (and I didn't know this til earlier) ProSim737.EXE uses Simconnect and is bound to the FSX RTM (note RTM, the very first!) Managed SimConnect build. It seems this is not compatible with P3D4. I don't know why, but not no doubt ProSim's authors will check and report in due course, though last time I looked they appeared to be pretty well writing P3D4 off until "August/September" when thery hoped to have converted the whole project to Simconnect (?). I normally run the ProSim EXE on a Networked PC, but that PC crashed before I went on holiday three weeks ago, and I've yet to install its replacement. When I do, I will be trying it over the Network in my normal way, with the hope that this method works. I know that other SimConnect-using applications do work with P3D4 this way, so there's a good chance. As it is you need to post pleas for a fix on the ProSim forums, because I am pretty sure the ProSimMCP interface (which does use FSUIPC5) is okay with the recent updates to FSUIPC5. Pete
  15. Pete Dowson
    Yes, it is ALWAYS like that and has been ever since I've been logging the calls. There is one "malloc" which is still being used after that count is measured. Pete
  16. Pete Dowson
    That is extremely odd. It implies other handles are occupying the intervening 5 slots, I'll look to see what logging already exists for this, or else I will add something. The code for the slot allocation is really very simple. "event.VRIread" does NOT register any handles. The handle you use there is the one from the com.open. I think you must mean that the VRIread call is somehow getting a different handle internally to the one you acually supply. Bwfore I look at your logs can you please tell me where I see the handle for each log entry? I did look before, because you said you included it, but I didn't recognise anything as being a handle. I'm afraid I am tied up this evening so it will be Sunday morning before I investigate this. Pete
  17. Pete Dowson
    Currently All the PMDG offset facilities are disabled, pendind information on the layouts. If you can send me the SDK'd .h file (petedowson@btconnect.com) and, even better, compare the tables of values in that with the previous version, then I'll be able to re-enable it. What "alloc/free count" is that? Pete
  18. Pete Dowson
    Well, you don't see it it my source either, do you? Thought: maybe it's some build flag added by VS2015 because of some option I've set, one perhaps not used in VS2010? I'll have to google it and see. Yes, please. petedowson@btconnect.com. Thanks, Pete
  19. Pete Dowson
    What on Earth is "FitObjData"? You have all the source in the ZIP. There's nothing else goes into the build of the ZIP, so I don't understand any missing flag. Do you see anything there? Are you sure it isn't in your source? I have no utilities which examine LIB files. I can do DLLs and EXEs, both 32- and 54-bit ones, using different utilities: PExplorer (32-bit only), PEBrowse64 (64-bit only), but no equivalent for LIB files. Pete
  20. Pete Dowson
    Well, that would be excellent, as then if there is a problem I can run it in debugging mode! Thanks! Pete
  21. Pete Dowson
    You must install the main release, 5.10 first, using the Installer. Then just replace the FSUIPC5.DLL module with the update. The changes since 5.10 are documented in the Download Links subforum. This is always the way with TEST releases, of which there have been 12 in 10 days! The full Changes document will be provided with the next full Installer update, 5.101, early next week. Ah, for WideFS registration? Sorry, yes, that question is actually being answered on request, here, at present, until the next main release, 5.102. Here's what you need to do: In the P3D4 Modules file, find and open FSUIPC5.KEY with an ordinary text editor like Notepad. Do not double click on the file, becase REG files change your Registry! If there are any WideFS lines already there, remove them and add these lines with your registration details, as follows: NameForWideFS=your registered name WideFSAddress=your registered email WideFS=your registration key I'll put this detail in a sticky thread at the top of the Forum. Pete
  22. Pete Dowson
    Yes. A "ModuleUser64.lib" is done but untested. I won't have time to make a test DLL for it until I get back off a short vacation in about 10 days time. But I'd be delighted if you'd please try it and let me know (before I go, on Wednesday). The changed are relatively trivial. You'll need the latest FSUIPC interim update (FSUIPC 5.101m, just released). I will be building a new full release of FSUIPC (5.102) for Monday or Tuesday, latest. Link to download LIB and all the source: ModuleUser64.zip Pete
  23. Pete Dowson
    That wasn't a good idea. Should have only uninstalled the joystick devices. Some wireless devices work fine with later versions of Windows out of the box, some need their own drivers installed. You'd probably need to find those (the pair would have come with a disk) or go to their website. Good. Pete
  24. Pete Dowson
    FSUIPC5 is now already up to version 5.101k which you can get from the Download Links subforum above. It is a busy time and it is being developed all the time. You are unlikely to get many addons working with 5.10. If your PDC Quadrant needed the PFChid.DLL on earlier 32-bits sims, it needs PFChid64.DLL for P3D4, because 32-bit DLLs will not run in a 64 bit process! Please do keep an eye on the Download Links subforum. Both FSUIPC and P3D4 are still being developed and there will be frequet changes. Now you confuse me. If the throttle quadrant is a genuine USB device then it will either work directly with simulators, or it will need PFChid64.DLL, On the other hand if it is one of the original serial port devices from PFC it will need PFCcom64.dll instead. Don't you know what you've got? Did you not get ANY information about the PFC stuff you have? Have you never used it before? I cannot support the hardware myself. I support my programs. Pete
  25. Pete Dowson
    And .. where is the log please? Those lnes were so that it would log more about what it saw in the Registry! That was the point. Sorry if I wasn't clear. Which part of "what was listed" there? Some of that is specific to a particular device makers, ones with VID_06A3 or VID_0738. The 06A3 is Saitek. (your 6 listed Quadrants are all VID_06A3). Your CH devices have VID_068E. 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.