Pete Dowson

Ok, glad it is sorted. Thanks for letting me know! Pete

Any settings will do, to taste. My cockpit Pc isn't on at present -- no time to enable the cockpit til tomorrow, or maybe monday (7 PCs are involved and a full 737-800 cockpit). I use FSUIPC wind smoothing, but I currently don't suppress or enable anything else -- as far as I remember, that is! I don't remember, sorry. Ask me again on Monday when i get my cockpit back on. Regards Pete

Strange. The non-DWC mode is actually setting weather very much like FSX normal settings. DWC is very different. I use AS2012 which is set for DWC by default. I use RC and AS2012 in DWC mode. For over a year now FSUIPC has worked in conjunction with ASE and AS2012 to provide correct destination weather -- FSUIPC gets it direct from ASE/AS2012 when the latter is running in DWC mode. There's been a lot of chat about all this on the RC support forum. Additionally programs like Aivlasoft's EFB can get the weather direct from ASE/AS2012. There is really no longer any reason NOT to use DWC. Regards Pete

By "standard mode" do you mean you aren't using DWC? (Direct Wind Control)/ Hmm. FSUIPC cannot differentiate where the weather gets set from. I don't understand that. Unless you are using DWC -- I've not checked to see if "Global" mode (as used by DWC) is overriding things. Pete

You posted the same message as three separate threads all within minutes of each other! I've merged them into one thread. Please don't do that again. I'm afraid I don't know the answer. But you must surely have a super computer running at 10's of GHz, because each time I undock a window the frame rate almost halves! Pete

I don't know of any aircraft in FS which have radios which are NOT accessible via standard FS controls and therefore also via FSUIPC, which allows assignments to any FS controls in any case. Why do you think there would be any problems? Sorry, I don't understand this part. What is a "com nav radio Airbus"? That seems too many words joined together without any direct connection. Pete

No, you did not mislead me -- this is why i suggested sending the AP Heading Hold control twice, rapidly, because that would set the heasding bug to your current heading and flick the A/{ on and off so quickly it wouldn't do anything (oh, except just possibly sound the disconnect warning. I don't know if doing it rapidly can avoid that or not). Okay, have fun! Pete

It is working fine here. Tested with weather set via FS's menus. When winds are 10-15 you'll only see small changes in any case unless you change FSX.CFG values to make more extreme shifts. I tested with 25 gusting to 50 and ir was varying rapidly up and down mostly between 27 and 47. It would only occasionally reach the extremes because it follows a normal or poisson distribution. Er , turbulence wasn't on the agenda last time and you actually specifically said So, are you saying there was turbulence too and by suppressing it you got correct gusts? I'm now confused about what you are doing and why your tests now are so different from before? Please clarify. [LATER] Ignoring the confusion at present with turbulence, I've done a comparison of the wind gust behaviour with FSUIPC smoothing enabled and without, and there is a difference in the rapidity of the changes. FS's normal gusting appears to be more like severe turbulence, and the changes are drastic and rapid. Gusts aren't really like like in real life, the speed goes up and down but not immediately by 5 orr 10 knots as I see it doing here. I think the way it is constrained by FSUIPC's smoothing is more realistic. At present I'm not sure where the difference arises in the code, except that it appears to be a deliberate implementation. The code is now six years old and is very complex and mostly forgotten, and I'm not sure that I want to fiddle with it very much. There are lots of implications about how it interacts with the innards of FSX in various places. [LATER STILL] Things are becoming clearer as the fog of memory loss slowly lifts! :smile:. I refer you to this section in the FSUIPC Advanced User's Guide: I've highlighted the relevant bits in red. I think it sounds like you want wind gusting to change more rapidly, so you need to try reducing the final value of the four in the TurbulenceDivisor parameter. The parameters set here by default are those arrived at after much experimentation, and testing by experienced pilots, in order to try to achieve the most realistic effects. I know that PMDG add-on aircraft users had to reduce these effects by around 50% because they were too severe for their autopilots to overcome. I think you are the first person who actually wants to increase the effects, or at least one of them! ;-) Pete

Well, I'll assume it's the lack of a proper video driver. Certainly, with all sliders to the left I get 2-5 fps at best with default scenery and aircraft. I know it's only a 2 Ghz processor, but on Vista (the previous operating system on this lap top, the one it came with), I was getting 15 fps with sliders reasonably high and using the full 1920 x 1080 resolution! Not till drivers have caught up, at least. The nVidia Win7 drivers refuse to install -- they may well work if they would install, but the installer simply says "not supported" and terminates. But at least I'm sure that there is no inherent problem in the joysticks interface. I think something has become screwed up on your setup. I hope you get it resolved when installing the release version. Regards Pete

Okay. FSX and Acceleration and FSUIPC all installed. Performance, with everything at minimum, and running at a very low resolution, is abysmal -- 5 fps most of the time, down to 1-2 at night. Useless. How much of that is due to the bad video drivers and how much to Win8's apparent inappropriateness on this PC I've no idea. But when I've done proving to myself that there's nothing needing changing in FSUIPC, I'll probably reformat and go back to Win7 64 so that i can install some drivers. Anyway, I let FSX install all it wanted, including (it said) DirectX 9.0C in the RTM FSX, and an update from the Acceleration disk. I've not gone and hunted for a later DirectX update yet -- I would have assumed that later components were not replaced by FSX installers in any case. Took a while to work out how to close down or restart the PC. I don't understand why this is hidden away in "Settings". What has powering down to do with Settings? It's the last place I'd look (and in fact did look there almost last!). I've connected a couple of joystick type devices and so far have had none of the problems you've reported. I'm just re-booting and trying again, then I'll look for a DX update. Pete

Which website is that? The only two sources of FSUIPC should be here, in the Download Links subforum, and the Schiratti page, which says it links to 3.999s but actually gets 3.999w. (I can change what the links obtain, as they point here, but not the text which only Mr. Schiratti changes. I'll remind him to update it, but it is never instant. So, I'd like to know where you are seeing 3.999g please! There should be nowhere you can get anything before 3.999w. Pete

It's up now. No, unless you really want gusts in upper winds. That was only a suggestion to see if the turbulence coontrol was interfering with the gusts computations, but now I worked out what is going on it is irrelevant, a separate and independent option. Regards Pete

Well, I'm stuck! I made a DVD with the ISO of the 64-bit Win8 I downloaded, but my lap top, with the Win8 32-bit preview on it, won't run the SetUp for a 64-bit version, and the damned disk doesn't boot! I was going to set it all up and test joystick connections here for you, with the "final" release, but i can't get past this stupid situation. How can they provide a non-bootable ISO build? WinZip opens the ISO file and it shows boot stuff on it, but evidently no cylinder 0 sector 0 bootstrap file (or wherever it goes these days)? Crazy. Looks like I need first to boot and install Win7-64 so I can run the Win8 64-bit setup! :sad: [LATER] Okay, I've done that ... but none of the proper drivers for my Lap Top's hardware will install under Windows 8! The video card is the main problem -- it is a full HD display (1920 x 1080) but the generic Win8 driver it installed only allows 1600x1200x16 max. The card is a GeForce Go 7400 but the nVidia drivers get as far only as saying Windows 8 isn't supported! I'll try installing FSX to see if it'll be happy with the crappy default Win8 driver, but I have doubts. Win8 doesn't even recognise that it's a WideScreen display, so round things are elliptical! Pete

I managed to fit in a series of tests today. I have found a flaw in the way FSUIPC's wind smoothing works, which would probably explain your observations.. What it currently does is smooth both wind speed and wind direction if either of them change. When gusts are present it seems there can be a small variation in the wind direction too, and this is causing both speed and direction to be smoothed! I haven't noticed this before, and I'm not sure why. but it isn't a good design, so i am changing it now to smooth speed and/or direction according to which one is exceeding the set change speeds. This will alllow gusts to vary the wind speed no matter what happens to the direction. Thank you very much for pointing this out. It is the first change in the Wind Smoothing for FSX in six years! I'm amazed it has taken so long! Please look out for version 4.855 which I shall upload to the Download Links subforum later today. Regards Pete

Try changing UpperWindGusts=No to 'Yes'. This defaults to No because gusty winds above the surface layer aren't realistic. Meanwhile, I've checked what FSUIPC4 does with the smoothing and it is certainly designed to allow the wind to vary between the base speed and the upper gust speed, unless "SuppressAllGusts" is set to 'Yes', and except in upper winds when "UppperWindGusts" is set to 'No'. And I must admit I've seen it vary so when on or near he ground. I'll run some tests, though, over the weekend. But so I can check with the weather conditions in which you are experiencing this problem, could you save the flight at the time, and Zip up the FLT, FSSAVE and WX files and send to me at petedowson@btconnect.com, please? Pete

I see you already asked in the correct place, and Paul Henty has replied. Please do not send the same message to multiple destinations. Pete

FSX has a checkbox to turn all controllers off. Use that. It sets the "joysticks=0" entry in the FSX.CFG. The Windows device controllers is a way in to the drivers, and a separate process. I don't understand why you'd think a process problem in FSX would apply system-wide? Pete

FSUIPC itself never touches the sound. It does offer sound facilities via Lua plug0ins, but nothing else. You need to look elsewhere. Pete

No, there's no such offset. Normally you'd just wind the A/P heading knob until the readout matches the compass heading, before pressing the A/P HDG mode select button. There is an FS control, assignable to key or button, to do it -- "AP HDG HOLD" -- but this also enables the hold. It's the same as setting the value then pressing the hold button. You could send it twice, to toggle the mode on then off immediately. If you must use offsets you can send any control via offset 3110. Or you can do it via a Lua plug-in, so hdg = ipc.readSW(0x582) -- Gets current TRUE heading, in same units as AP Hdg hdg = hdg - ipc.readSW(0x2A0) -- convert to MAGNETIC by subtracting Mag Var ipc.writeSW(0x7cc, hdg) -- write to the A/P Hdg bug[/CODE] Regards Pete

No idea I'm afraid. Obviously something has changed. WideFS itself doesn't change. I can't help further with no information. I need version numbers and Logs. There will be a WideServer log in the FS Modules folder and a WideClient log in the wideclient folder on the client. Paste both in a message here. That's always a good starting point -- that's why logs are produced! Regards Pete

There's nothing FSUIPC does about gusts, neither to generate nor prevent. I'd need a lot for information to investigate this, please - actual FSUIPC version number, and the INI file. Do you suppress FSUIPC's wind turbulence? If not, try it. You shouldn't need it in any case with ASE. Everyone says that, but it is meaningless. What is the latest? To most folks it's the last one they saw. I always need the actual version number, which isn't hard to find. It is on screen in the options, in the log, in the DLL properties. Pete ]

Yes, but with this one you didn't add that logging line I gave you, as I can see here: 405 LogOptions=20000000 00000001 [/CODE] I see you added it for the next log ... [CODE] 327 LogOptions=20000000 02000011 and when you forced a device rescan, these errors are certainly the cause of the problems: 110152 DirectInput8Create failed, return = 80040154 That error seems to be "class not registered", which would be related to the GUIDs and therefore the Registry. did you install Win8 clean, or as an upgrade from Win7? Maybe the registry is screwed up somewhat? The GUID for DX8 is 0xBF798030,0x483A,0x4DA2,0xAA,0x99,0x5D,0x64,0xED,0x36,0x97,0x00 but that appears to be a pre-defined fixed one. The GUIDs for the devices, which will also appear in the call which is failing, are those listed in your INI file. Do a search on the error number on the Internet. There are lots of suggestions for fixes, but few directly related to DirectX at all -- this was the only one I found which even mentioned it: http://www.free-codecs.com/guides/How_to_fix_Class_not_registered_or_80040154_error.htm FSX uses the same DirectX calls as FSUIPC4, so they should fail there too, to be consistent. FS doesn't re-scan devices for changes, whilst FSUIPC, by default, does. I do this because it enables you to change devices, add or remove them, without restarting FS. FS doesn't allow this at all. You can stop FSUIPC doing the auto-scanning on entry to the Options by changing AutoScanDevices=Yes to "No" in the INI. Then it will only re-scan if you click any of the "reload" buttons in the options. Same reason. Evidently Win8's version of DirectX does not like programs trying to close and re-open devices! crazy. You need to submit a bug report. Maybe it's even buggier than I just suggested? Or maybe it's because FS is opening the devices as well as FSUIPC? Have you disabled controllers completely in FS? I don't know if that stops it identifying them. Regards Pete

Ah, tthats a public evaluation version. i think the version I downloaded is the one which will be publically released, and as an MVP I get some free keys which are permanent, not temporary. As it says, on that Evaluation weeb page: Pete

I put the Preview edition on an otherwise seldom-used lap top to check it out. It took quite a bit of fiddling aound to get it as usable as Win7 (my opinion of course). Certainly FSUIPC worked okay on it, but everything was so slow as to be unusable. It's only a 2 GHz processor, but i expected more. The main problem was lack of drivers, eg, for video, then. Have they actually put the start button back? I had to download a program to fiddle that back in on the Preview. But FSUIPC isn't changing -- so what in your system is changing? Why is Win8 different on one day to another? And why should restarting a program make it run differently? There's nothing a program retains when it closes other than in its files, and FSUIPC's files are ONLY the INI and referenced macro and Lua files. What do you mean "no logging any more". You mean no closure, no end? So FSUIPC really does get unloaded or hung? The Logging is produced in the main thread, the same as the main thread of FSX, so if that thread hangs, so does FSX. But there is nothing you can do in the INI which will make it change from day to day or the start of FSX to the next restart. And nothing in a default INI either. For more information on what is going on with buttons and axes, add more logging options. Button logging, especially, but also add this to the [General] section of the INI: Debug=Please LogExtras=x200000 That'll make it log some of the details of the device scan it does when you go into the assignment options. I have downloaded the release version (I assume it is release) 64-bit, but not "Enterprise", and will make a DVD of the ISO. I have five keys for it so I will try it on that Lap Top I mentioned. Must be a huge change from the shabby preview editions, then. What is different in the "Enterprise" edition? I don't think I'm entitled to that as part of my MSDN/MVP membership. I'd assumed in any case most FS users would be using the standard edition. Regards Pete

Ugh! Why on Earth abandon Windows 7, the best operating system Microsoft ever produced, for something so inferior? At least wait for Windows 9. Win8 looks like another Vista fiasco to me. Is Win8 compatible with Win7 and before? Is there a Win7 compatibility mode you can set for FSX? I'm sure nothing you can do in an INI file will make a difference between Win7 and Win8. The differences must be in Windows. But evidently it is different. FSUIPC works okay in WinXP, Vista and Win7. So what's been messed up in Win8? And how can I possibly tell? I don't understand why you supply an INI file yet no Log at all. You say FSUIPC is 100% not working even with a default INI file? Or do you really mean that FSUIPC is working completely normally EXCEPT for assignments? If you assign in FSX and merely calibrate in FSUIPC, does that work? I'm afraid there's no way I'm going to be able to do anything with Win 8 for a while. I'll need to build a new PC -- I can't afford to compromise any of those I currently use for development. You'll need to do some process of elimination. Start simple. Try all avenues. Collect data. Use logging. Pete