Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. Ouch! It isn't you, it's me! There's a bug -- the indicator IDs in SetColour run from 1 whilst those in SetLight and ClearLight run from 0! You can see this by changing your SetLight to gfd.SetLight(GFWP6,0,0) I'm going to have to fix this. I'm not sure at present which one is wrong, but i've a feeling it must be "SetColour", because the SetLight and ClearLight facilities existed long before the WP6 and 'SetColour'. The convention in FSUIPC has always been to number from 0, but I must have been confused by the WP6 which numbers its indicators from 1. So, I'll change SetColour to also count from 0. I just hope it doesn't mess too many folks up! Fix will be in FSUIPC 4.761, 3.998t and Wideclient 6.92, later today. Thanks for finding this bug! [LATER] Okay, the revised versions are now available in the Download Links subforum. Regards Pete
  2. I'm afraid so. You seem to have missed this paragraph in the User Guide, which explains it all: It is not normally any sort of problem -- adding new axes is not a common thing to happen. Additionally, if you are using Profiles, surely you don't have all that many? Generally I would expect a profile for each main aircraft type -- jet, turbo, prop, helo, with maybe stunt/fighter and GA separated. You could simply copy the generic assignment and calibration lines into each of your few profile sections, in the INI file. Regards Pete
  3. Er, I'm now confused! I thought you said you'd adjusted the values to ones you were happy with? Why do you want to change now? I was only answering the question you asked about what RW turbulence was like. There's no point in doing anything with the turbulence values if you are going to suppress all turbulence. Pete
  4. Sorry, you've lost me. Do you have a specific question? When calibrating in FSUIPC don't use Filters unless you really do have bad or dirrty controls and/or a wonky power supply. If you are wanting no reverse zone on the throttles check that option, but also set UseAxisControlsForNRZ=Yes in the INI, as recommended in the manual for Wilco airbus. Pete
  5. The default values were arrived at by lots of testing and would be realistic values, but the PMDG aircraft are well known to be rather over-sensitive. You are lucky if you can leave the turbulence on at all. I think most PMDG users suppress it altogether, both in clouds and wind layers. Regards Pete
  6. FSX does do auto-assignments according to details it holds about devices. I think they are all in files called something like Devices.CFG. It matches devices by the name which appears on the USB connection. Maybe the device name is ambiguous or it got the wrong one, and did its auto-assignments based on the details it has in those CFG files. I always have all controllers disabled in FSX and assign everything in FSUIPC. I don't like auto-assignment at all I'm afraid. It can be very annoying. Regards Pete
  7. Odd. I use AVG as well without such a warning. Mind you mine isd the Free version. There is nothing wrong with WideClient.exe. The code is compressed and only expanded in memory when loaded. Any virus indicated is a spurious indication. It is also codesigned so you can check it hasn't been tampered with. Just right click on it and select Properties - Signature, select the signature entry for details and make sure it says it is okay. That confirms it can't have been changed. Regards Pete
  8. 4.731 has now been replaced over 20 times! You are way out of date! The current version is 4.759, and the standard download from any official site is at least 4.758. How did you ever manage to get FSUIPC in the first place? Go either to the usual www.schiratti.com/dowson site, or, even easier, the Download Links subforum here, in this Forum, which is where all my updates have been posted for years! Pete
  9. Nothing wrong with any of that, but you need to know that Wideclient 6.75 is out of date and unsupported. The oldest supported version is 6.86, but version 6.91 is available. Similarly the latest FSUIPC is 4.759. See the Download Links subforum for updates. There is no [user] section in FSUIPC4.INI because it doesn't do anything, it would be ignored. Programs started by FSUIPC via the [Programs] section are shutdown by parameters in the same line which starts them, like CLOSE and KILL. The WideServer "AutoShutdown" facility is part of the [WideServer] section, as are all Server parameters in FSUIPC4. I think this is because of two things: 1. The misplacement of the parameter in FSUIPC4.INI. 2. The use of "Run" and "Close" for your client apps. You must have missed the explanation of what "AutoShutdown=Apps" does. This bit is important: Set it to ‘Apps’ if you want WideServer to tell clients to close down only any “CloseReady” applications when FS is closed normally. You should use "RunReady" and "CloseReady" for that closing action. If you also want WideClient to close, so that Run and Close do the job, then you'd need to use "AutoShutdown=Yes". Note that, whilst FSUIPC does delay the FSX closing to some extent to allow time for WideServer to distribute the messages about clusure to all clients, it can happen that FSX closes so fast in any case that not all clients see this. I always assign a keypress, Ctrl+Shift+E, to activate the WideServer shutdown facility, before closing FSX. This always works, even with my 8 client PCs. Check the ShutdownHotKey and CloseAppsHotKey parameters. Regards Pete
  10. PMDG have always been consistent in refusing a cheap kit for interfacing to their products. They seem to feel that hardware makers would be getting a boost from the hard work and investment in PMDG, so they set a premium on the interface -- which some hardware makers have paid up. But not all, including PFC who I've done a lot of developments with (PFC are the makers of my 737NG cockpit). In my earlier days interfacing with some of PMDG's employees I tried to persuade them towards the view that an open interface benefits everyone, that they would sell more as a result. But it all fell on deaf ears I'm afraid. Regards Pete
  11. Sorry, no, not if none of the mouse macro or LVar methods work. I assume no one else has solved it -- so how do folks manage? Do they all use a mouse? A touch sensitive screen work work well too. maybe use an iPad with AirPlay to act as a second screen to accommodate an undocked CDU window. Only PMDG could do that, and they won't if the only way of getting into it is hacking their code, which I wouldn't do in any case. Sorry. Pete
  12. That's a serious defect, then, and most certainly needs at least a mention if not a full blown report on their support forum! Regards Pete
  13. Sorry, you've lost me entirely. I'm not a hardware guru, and I've no idea what 'ApphangB1" is. At first I read that as " "apfang" (as a name) then realised you meant App Hang. But what's "B1"? I've no idea how my DRAM is set up. I have 2000 ram running at 1866 I think. My mobo is an Asus, but a Maximus iV extreme, and was put together for me. I gave up building my own a few years ago. ;-). I haven't really had any freezes with this machine. I used to on my previous one (a water-cooled overclocked I7-980x system) and had to underclock the memory on that too. I doubt that anyone would think to post such stuff here -- maybe on a hardware forum, as on AVSIM? This support forum is really for FSUIPC and WideFS. Regards Pete
  14. Surely they've got keyboard short cuts for all of those, and the 12 LSK keys too -- usually F1-F12 on the CDU's I've seen. I just cannot believe they force people to use the mouse. Regards Pete
  15. FS2004 never had a steering tiller control, so there is no FS control number. FSUIPC supports a tiller using a separate calibration of the rudder, but you have then to assign both the rudder and tiller in FSUIPC, "direct" to calibration, and calibrate them separately. Why do you want a control nmber? If you need to operate via offsets you can use those in the range 3BA8-3BC4, and assign in the same way in FSUIPC. If you need to send control numbers instead then all FSUIPC's directly assignable axes have control numbers currently listed in the recent "Changes" document supplied in the updated ZIPs (see Download Links subforum). Regards Pete
  16. FSInn doesn't use FSUIPC and isn't supported here. I'm afraid I know nothing about it -- you'll need to go to their support. Incidentally, 4.70 is pretty old now. Current version for FSX is 4.758. See the Download Links subforum. Regards Pete
  17. Okay. I also get '9's showing as '0's if i treat the MCPPro like an MCP. I've done a load of extra testing and found that sending segment settings 00111111 (for '0') and 01101111 (for '9') both show as '0'. It looks like a bug in the GFDev.DLL module. (Segments are numbered 0 at top to 5, clockwise, and 6 for the centre cross one. Bits are 6543210). I checked back with older versions, right back to 2006, and they are all the same. I have reported this to Sandy, the current GFDev.DLL developer for rectification. Meanwhile, there are now easier ways to set the displays on all the GF devices -- in the current versions of FSUIPC and Wideclient I only use the newer methods for the MCPPro, because the other devices pre-dated the additional features in GFDev. Unfortunately I do not know whether they all work (I don't have all the devices), but I am building a revised version of FSUIPC to use the newer facilities and will post again here when I have a version you can try. [LATER] Okay. I got a reply from GoFlight, and it looks like it is a firmware issue -- some versions of the firmware work okay with the pattern for '9' I'm sending, others only produce a 9 if you leave the lower horizontal segment off. No matter. The latest version of the gfd library uses the normal strings instead of setting segments, and that should work with all the devices now. Choose from FSUIPC 4.759, FSUIPC 3.998s and Wideclient 6.91, all now available in the Download Links subforum. Regards Pete
  18. So that's the one you really want an LVar or mouse macro for. Hmm. shame, then. Don't PMDG provide a keyboard shortcut for it? Else they are forcing you to use the mouse, which isn't good. Regards Pete
  19. Well, you could be right. But whatever is going on, surely you need a keyboard to drive a CDU in any case. I think it has to. How else would you key in A-Z, 0-9, /, delete, clear, +. -, and the assorted function keys? Even Project Magenta's pilot and copilot CDUs use a normal keyboard. The PFC Boeing style CDUs in my cockpit have their own keyboard and screen and a mini-PC each. Even if there were it would be really clunky feeding each keyboard character in one Lua value at a time. Using a keyboard. That's why I was talking about focus. I assume you can use the PCs own keyboard once the CDU has focus, or do they force everyone to use the mouse to press each and every key? Regards Pete
  20. I found your query in the FAQ subforum, which is the repository for standard answers. I've moved it here, to the Support Forum, for proper handling. You mean that you assigned two commands to the same axis? That's one way of doing it, but it certainly isn't the best way by far. The facility for multiple assignments has applications in complex circumstances, but really that isn't one of them usually. If you are wanting only one mixture and one prop axis for any aircraft, no matter how many engines (up to the 4 supported by FS), you'd be better off using the same generic axis as FS would assign normally -- i.e. Axis mixture set and Axis propeller set, respectively. If you really did want to control only two engines, and use another pair of levers for the mixture and prop of the other two engines when using a 4 engined aircraft, then you are besy assigning one pair to engine 1 and the other to engine 2 controls, and then, in calibration, check the appropriate mapping option(s). FSUIPC can automatically map 1->12, 2->34 for 4 engines, and also handle 3-engines for you too. Hmm. Each control is sent separately, because they are, obviously, separate controls, but they should certainly move the levers almost simultaneously, within a fraction of a second of each other. If not there's something seriously overloading your PC. ON FS9 and before the controls are Windows messages, so are subject to normal Windows message queueing. On FSX they are calls to SimConnect, and may be subject to interception by other programs, particularly complex add-on aircraft. But I've never ever seen a separation which could possibly cause any "catastrophic failure" -- how does such a catastrophe occur? Please explain that. The only way, ever, that there will be absolutely simultaneous action is if you use the normal single generic controls, whether in FSUIPC or in FS directly. I assume you have a reason for assigning in FSUIPC rather than FS? Perhaps you need to excplain that too so I can understand what it is you are aiming to accomplish. Regards Pete
  21. As am I. So I don't understand why you get no cloud maps. Have you tried smaller areas? I think your 2 degrees x 2 degrees is too big -- bigger than the area FS populates with clouds in any case. Also try less altitude. Not sure that's worth doing in view of the above. As I said, i think the author of the RealityXP one hacked into FS for the information, not using any SimConnect facility. Most others I know just use local weather reports, taking samples by reading the interpolated weather over a matrix of lat/lon points. This was done with FS9 too, before any SimConnect. Regards Pete
  22. I've not seen anything like that either. Sorry, but I don't know how it is done. my guess would be that they are objects created in a specific position, like static ground vehicles, but with altitude, and self-orienting towards the user positin, somehow. If that's how it is done it'll be through clever scenery programming -- BGLs, so that's the place to look in the FS SDK, the scenery development area. Alternatively I suppose they could be AI aircraft set in position and frozen. Seems less likely though. Regards Pete
  23. FSX includes a screen grab option I seem to recall, it'll save static views for you. Programs like FRAPS can record the moving pictures for you. The different cockpit views are simply defined in the PANEL.CFG file, and in the Cameras definitions in other CF files. Multiple open 3D windows has been a built-in function of versions of FS going a way back. I don't think any of that is developed by cockpit developers. Regards Pete
  24. Did you run the installer "as administrator", as instructed? What version of FSUIPC? If not the latest (4.578) try that -- see the Download Links subforum. Check that there is an FSUIPC4.KEY file in the P3D Modules folder. If still problems with the latest version, please paste the FSUIPC4.LOG file here (not the KEY file though -- that's confidential). Regards Pete
  25. It certainly does set an engine fire in FSX. Don't know about FS9 though. Regards 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.