Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. If your button is seen by FSUIPC in the Buttons & Keys assignments tab, then just do the appropriate assignment with the details I provided already. If your CPFlight H/W does not emulate a normal joystick, recognised by Windows as such, then you need to find out what drivers CPFlight provide for their hardware and see what facilities there are there. I'm afraid I can't help with that side of things. You may need CPFlight help. Pete
  2. All the runways files have runway altitude, not necessarily airport altitude. In the case of CYPZ they are all the same. so i can check my changes, do you know of a default airport where the runways have a different altitude to the airport? Okay. that makes more sense. Thank you! Of course it has probably expired by now in any case. 😞 Pete
  3. Possibly the other positions use button numbers 32 and upwards. FSUIPC only handles 32 buttons per controller. Check in Windows Game Controllers to see what buttons it shows (bear in mind that it might count from 1, so 1-32, whereas FSUIPC counts for 0, 0-31). If this is the case then the only way in FSUIPC would be to use virtual buttons, using the pLua plug-in HidDemo.lua, provided in your FSUIPC Documents folder, in the Lua examples ZIP. Pete
  4. Have you got the right airport ID there? My charts say CYPZ runways are at 2343 feet not 2351. Checking in MakeRwys I get 2342 feet. That's with default CYPZ. Looking into the raw data it would be 2342.39 feet. Please confirm so I can check. It does look relatively easy to make the change. Pete
  5. Only if you have a button continuously pressing and releasing, or you've assigned it to repeat and it is always pressed. Sorry, do you mean setting, clearing or toggling bit 7 in offset 5653? There are three separate IPC offset controls assignably in FSUIPC: Offset Byte SetBits Offset Byte Clrbits Offset Byte Togglebits Choose the appropriate one to assign. The parameter for bit 7 is 128 (2^7, or 2 multiplied by 2 6 times), and you enter the offset in the Offset field as x5653. Pete
  6. Hmm ... and you automate this using MakeRwys files? Otherwise, if it only the information you need to specific airports surely something like ADE would do? I'll take a look at the code. If it is a relatively trivial change i'll do it. But I hope the resulting files are acceptable to all existing users. I'll need to add a warning just in case. i don't want it as an option. BTW, whilst I have your attention, I did subscribe to FSAERODATA, but somehow I could never get updates. For a while you supplied me with a link by email, but that service dried up, so I have been using Herve Sors updates instead. Is the FSAERODATA service now fixed? Pete
  7. You need to also ebable Button/Key logging so we can see if any of that is due to buttons sticking. The log supplied is a continuation log, meaning you started a new one. This means that the vital information at startup is all missing. Please only start a New Log when you are starting a fresh test and the file is getting really big. but then supply both logs. I think that just defines the default key presses in FSX. Not sure what happens if you delete it. If you don't want FSX to process button presses or your controllers then just disable those in the FSX user interface options. However, let's see whether the problem is button presses first. Because of the missing part of the Log I can't tell if you are using a default aircraft or an addon. If an addon then test with a default aircraft because it might be to do with the addon. Pete
  8. Yes, that was what it was designed for. The Mouse Macro generation was added years later. You must be only referring to the User Guide, where there is indeed a Mouse Macros chapter. It is in the User Guide because mouse macros are automatically generated for you via mouse click interception. Because creating "normal" macros involved actually creating and editing files it is considered more advanced, and you'll find full coverage in the Advance User's manual. For FSUIPC5 this Chapter starts on page 36. Pete
  9. As it stands the only way would be to use macros or Lua plug-ins for this. In fact mscros are designed for just such a purpose -- having a sequence of commands/controls delivered with one invocation. Macros would be more efficient than Lua plug-ins in this case. Pete
  10. Copy and paste. Not only the 12-character key, but also the name and email. All three parts MUST be exactly correct! Pete
  11. It's a Windows error code -- anyone can look up Windows error codes! See here: https://docs.microsoft.com/en-us/windows/win32/debug/system-error-codes--500-999- Pete
  12. That happened because you didn't run MakeRunways "as administrator", as instructed in the documentation, see here (from Page 1): NOTE that you should run MakeRunways “as administrator”. This is especially true on Win10. The best way is to mark it needing admin privileges in its (or its shortcut) “Properties – Compatibility” settings (right click on the EXE or the shortcut). The Lorby program being used needs the increased privilege level so it can access the AppData and ProgramData folders. If you don't run MakeRunways "as administrator" then windows error 740 occurs because the Lorby program cannot then be run. Pete
  13. Only if you are using an ATC program and choose an airport for landing with far too short a runway for yor aircraft. It would just mean ATC couldn't tell you that you can't land there. Nothing else. it only changes the listings after all. Pete
  14. There's really nothing in FSUIPC which will change any visuals. Perhaps you need to ask PMDG why turning off the yaw damper restores the viisble pedal movement? They did suggest that after all. Maybe it's the way they've similated it? Pete
  15. The axis assignments tab shows what you assigned it to -- maybe a previous configuration? Just assign it to whatever you want it to be. Pete
  16. The PMDG commands tend to always use Mouse Codes for their operation. So what you would be looking for is the code for left button release. The mouse codes they use are listed before the list of added controls in their SDK's .h file. Pete
  17. MOVED FROM THE FAQ SUBFORUM! Please always post questions to the SUPPORT FORUM! I've no idea why you were referred here. What is "error 740"? What is reporting it? How is it related to Pro-aTC/X, which is an ATC program? Did you supply them the screenshot they requested? Pete P.S. If it is a Windows Error number, then read this (found by Googling "Windows system error". ERROR_ELEVATION_REQUIRED 740 (0x2E4) The requested operation requires elevation. Seems you need to run whatever you are running in Admin mode (right-click, run as administrator)
  18. Sorry, do you mean you operate your rudder pedals and this has the proper effect on the aircraft, but the picture on screen inside of the in-cockpit rudders aren't moving? If that's the case then it is a question for PMDG, as the graphics are theirs. Definitely a question for PMDG then. Pete
  19. Make sure you do copy and paste ALL THREE parts (name, email and key), not just the Key. If that doesn't work, then you need John to help as I don't have access to FSUIPC5 orders now that John is handling it. Pete
  20. Okay, good. I've been using AOMEI for quite a while now. Well, yes ... until they don't. but modern ones are more reliable, certainly. Vinyl record enthusiasts also enthuse about valvel amplifiers. Pete
  21. As did I. Mainframes with valves first of all, then discrete transisters, then , much later it seemed, integrated circuits -- minis by then. I'm sure I wasn't being nasty. I was only pointing out that you appear to be misinterpreting what Windows can do. There are built-in backup facilities which work well. You are in the wrong place here because this is support for FSUIPC and WideFs, not for Windows. I'm sorry, but I repeat, you need to seek help for Windows, whether online or in your own PC. Pete
  22. As Thomas pointed out, you are still using an out of date UNSUPPORTED version of FSUIPC. Please update as a first step. I assume these are your two Joysticks? Which is your "throttle". Looking through your settings, you have a mess, with a non-existent device 0 still assigned. I think it will be easier for you to start afresh. Delete the INI file and re-assign, but USE JOY LETTERS first, as noted by Thomas. When you have multiple controllers this allows FSUIPC to keep track of them properly. Pete
  23. You have something wrong. Show me you FSUIPC4.INI and i will then be able to check the assignments. Check also in FSx that you haave disabled all controllers. i seem to remember they are individually selectable. It does certainly sound like a double assignment to the aileron, from your second "throttle" joystick. Pete
  24. Please update to the current release (4.974). We cannot really support older versions. FSUIPC won't be doing anything different for ailerons for each aircraft, excepting via different profiles for each. is that what you have? if so, maybe you haven't calibrated the ailerons correctly in FSUIPC for your PMDG 747 profile? Pete
  25. Well, a "System" backup is the first thing one should do when everything is working. That can be done easily using the facilities provided in Windows (yes, and in Win10), or by third party applications. There's no point trying to "copy drive C". Even if you could, that is not a backup. There are ways to get a complete image of a drive, but that really is not necessary and in any case cannot be done without either third party software or linking the two drives together and using a copying device (I have one of these, used to make backups of my Yamaha Music Server disk). You are really trying to do the wrong things. It isn't Windows, it is you! To backup the system use the Windows back up facilities OR a third party application. You just keep repeating the same thing, that you cannot copy drive C. You shouldn't be trying to! Anyway, since your system is already in a mess there's no point in backing it up. A backup of a mess is still a mess! I think you are now in the wrong forum for help Try looking in AVSIM forums for those which might deal with computer messes, Sorry. 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.