Popular Content

Showing content with the highest reputation since 02/24/2017 in all areas

  1. 2 points
    Actually, I think all you need to do, when I provide a "fixed" version, is restore your previous INI file, with the ID numbers in their original assignment, and FSUIPC should then enforce that in the Registry. That's part of the change and the part that doesn't work. The non-registry way of finding the GUIDs seems to be working okay, so FSUIPC is no longer dependent on locating IDs in the registry. Still working on better code and testing ... Pete
  2. 1 point
    The screenshots on the sales site were made from an early version of the airport with the tower in the wrong position. It has since been moved to the correct position, on the opposite side of the runway, near the cargo center.
  3. 1 point
    Hi, you declare normally only once the Offset you want to use outside the function, global, like you would do with global variables. Have a look into the manual / examples that comes with the DLL, that will really help a lot to avoid mistakes. Thomas
  4. 1 point
    Hi, you can use it on the FS PC or on a Client PC that runs WideClient. Thomas
  5. 1 point
    Dear friends, I'm sorry to tell you that I'm suffering from cardiac arrhythmias since some months, and up to now have no diagnosis of the reasons nor any therapy but to keep calm and avoid any load. I hoped this to get fixed since long...So please understand that I cannot do support as I did the last 20 years - I hope to get better in a while and than to get back here.
  6. 1 point
    Well, FSUIPC would change them itself, so they must have been ones you changed to suit the helicopter. Maybe at the time you hadn't defined or enabled the profile separately for it? Well, in that case, they weren't FSUIPC settings at all, because the INI file contains ALL of your settings -- unless you have st "UseProfiles=Files" so your profile settings are in separate files in the Profiles subfolder -- but I see you have not done that in any case. Therefore ALL of your settings are held in that one file, no where else, and unless you changed them nothing else should. It sounds more likely that you have controllers still also enabled in P3D and these are interfering. Either that, or something is being loaded by your Helicopter add-on which is still running and interfering even after you change aircarft. Is that possible? Does it install its own DLL or have some EXE or Lua plug-in running as well as the normal aircraft Gauges etc? The fact you fixed things by uninstalling it does suggest as much. Yes, they are ALL there, no where else. There is absolutely no way FSUIPC would know any different from what it sees in that when it loads. Since you don't say anything specific about what actually changed I cannot advise any further. Incidentally, you should always check that you are using an up to date and supported version of FSUIPC before coming here for support. You are on 4.961. the current supported version is 4.964. Please update before returning. Pete
  7. 1 point
  8. 1 point
    Yes you can do it that way. Make sure you follow the steps precisely and make sure you have the latest one. 1.3 or something. I honestly stopped using my Saitek throttle quads earlier today. And I stopped using the reverser buttons on them years ago as I found them just to sloppy and always triggering just from taxiing. So what I did was setup one button on my joystick to enable that plugin and then ran the throttles up. If you wish todo it that way it is not described in the readme but its easy todo. Select the button you want to use in the Button assignment table. Select for FS Action. Scroll down to LuaToggle ThrottleManager. Make sure you select the Toggle one. There are like 9-10 options. Set it to parameter 1 click okay and exit FlightSim. Open up FSUIPC.ini and find the entry that looks like this. 54=PA,8,CL3:T,1 -{LuaToggle ThrottleManager}- the ,1 at the end is the parameter. Copy paste that line 2 more times and change the parameter to 2 and then 3. The parameter assigns the engine. Should look something like this when your done. 54=PA,8,CL3:T,1 -{LuaToggle ThrottleManager}- 55=PA,8,CL3:T,2 -{LuaToggle ThrottleManager}- 56=PA,8,CL3:T,3 -{LuaToggle ThrottleManager}- Open fs. Press that button you should hear a ding. If you don't something isn't setup right. All done. I have it setup on my 777, ifly 747, pmdg 747, md-11 and works fine on all of them and more convienent than a seperate axis for the reverser. Now you should be able to setup a spoiler axis and a flap axis on your quadrants. since you freed up 3 axis assignments.
  9. 1 point
  10. 1 point
    I had to capture this because previous attempts to land at runways 8 and 35 at KPHL resulted in air collisions. Hooray for Tower!3D Pro........ RickyJ
  11. 1 point
    I have at last found a way to get the correct device GUIDs without recourse to using Joystick IDs which may or may not be found correctly in the Registry. The problem with the registry method of locating the correct GUIDs to properly identify a device is that, since Windows 8 at least, the joystick ID number, the only sure way I had of locating the GUID, was not always being set. The Saitek devices seem to have been notorious for that, but this may only be because they are the most prevalent. Either the HELP provided on the MSDN websites has improved, or, more likely, my skills and patience in searching have improved, because I have now found I can get hold of the GUIDs by using DirectX enumeration, after all. It is the DirectX enumeration which provides the Joystick scan list logged by FSUIPC during initialisation, as opposed to the Registry method used to produce the [JoyNames] section in the INI file. This change is not subtle, though to most users it is hidden 'behind the scenes'. The only overt change is the logging, now, of the GUID, in the scan list. The change actually really makes FSUIPC independent of the joystick ID method of tying them up, the one limiting the number of devices to 16 numbered 0-15. So, now, really the JoyLetters are just as much identification as the numbers, and if it were not for existing installations everywhere still not using JoyLetters I could dispense with the numbers altogether. But that's just wishful thinking. It could also mean that the number of devices handled could be increased beyond 16 (though if single letters are used it would be limited to 26, or 36 with numbers 0-9 as well. However, such a change would mean a major restructuring of so much in FSUIPC that I am not willing to risk it. If I were only 20 years younger I might be braver and also be willing to spend more time on it! So, the change offered now is effectively just a more reliable way of identifying joystick devices, without folks having to resort to re-installations or setting IDs via JoyIDs. The problem for me, before release, is to prove my code changes. I don't have many devices (just 2) and the ones I have aren't used much except for basic tests. My cokcpit has no regular devices, everything being handled via specific drivers for PFC and so forth. Hence I need some volunteers please to test this update on their system, one preferably with several joystick devices and a good number of assignments to them, possibly in Profiles. If you are willing, please first make a safe copy of your Modules folder so you can easily revert should things not work out, then download version.4963b_TEST and copy the DLL into the active Modules folder. Feedback here, please, with INI files and LOGs if there's anything wrong noticed. Thanks & Regards Pete Dowson
  12. 1 point
    It's good to see the main directory naming convention is back (the exclamation point is back). I can now takeoff from KPHL runway 26. The bluish tint and labeling of the taxiways is pleasing to the senses. The higher camera view lets you see the planes better, mostly noticeable at KJFK. This makes up a little, but not much for more camera zoom. Although a lot of the commands do not have drop-downs, I have been able to create a text file and do a copy/paste. The added pushback step keeps you more busy. The added "CALLSIGN, RUNWAY 9L CLEARED FOR TAKEOFF UPON REACHING ALTITUDE 004 THOUSAND CONTACT DEPARTURE" eliminates the penalty hit for forgetting to send the aircraft to departure. Although it did take a little getting used to just seeing the "T" after takeoff. Seeing the shadows of the passengers as they walk down jet bridge at night. The boats sailing on San Diego Bay and the seagulls flying around at St. Thomas, I am lucky I have not had a bird strike yet. I am sure I have missed a lot more details. So much more to explore and discover. Here's to the team for their long hours and dedication to get the release out before the holidays. And to Nyerges and BMT for keeping up with the pace. And I have not encountered a stuck or twirling plane yet. Maybe the Leprechaun will bring me a monitor for St. Patrick's day. RickyJ More cool stuff......... You can change runways at will, so you never have to land, just keep them circling, I haven't run out of fuel yet. At KSAN, you can now specify your exit,like B8 or B9 or B10, but make sure you have at least 10nm between arriving aircraft before you attempt a departure, especially if you specify B10 as an exit. If you give the taxi path when you give the "PUSHBACK" command, all you have to do is give the "CONTINUE TAXI" when the plane is ready. A real handy command "LINE UP AND WAIT BEHIND NEXT LANDING AIRCRAFT" Pilots now can tell the difference between morning, day and evening.