Pete Dowson

Not unless you've selected the option to lock the Windows in FSUIPC, no. FSUIPC doesn't have anything to do with the graphics. Why would you suspect so, just because everyone always blames FSUIPC for everything? More likely you have set the video driver dual screen mode up incorrectly for FS. I really don't know a lot about that. However, you should never have any such problem if you run FS in Windowed mode, rather than full screen, as all normal undocked Windows should be positionable wherever you like. Full screen mode restrictions are usually down to the video driver or its settings. Pete

I haven't used FS's ATC, so I need some clarification. also I'm not sure what you mean by "pressing" a rotary knob? When I had GF units you had rotary controls, which you could turn either way, or buttons or switches, which you pressed or toggled. What does pressing a rotary do? Is this an extra capability of some of the new units? With regard to the ATC stuff, how are you trying to do it? I'm aware of some ATC controls in the FS controls drop down. Don't they work? I think they are called ATC Menu 0 to 9. Right? You might not be aware of this, but FSX's (not FS9's, or before) ATC window actually intercepts keystrokes before FSUIPC can get them, so if you are trying to use those it won't work -- unless, that is, you use the latest Beta version of FSUIPC4 (from the FSX Downloads Announcement above), where I've found a way of getting the jump on that ATC window! ;-) Regards Pete

Don't need to. Please see the analysis I've done. I think you need to go to the FDC support forum now, as Dave suggested. Regards Pete

Understand. Do I still do the logging instructions above as well, or just try .236 and see what happens? Unless you find it slows things down too much (and I don't think it will), best to have the logging enabled so that if you do get something fishy happen you don't need to repro it. But don't send e stuff unless there is a problem, please! ;-) Assuming I've fixed what I think I've fixed, the only things left to resolve are the heading deviations in the PMDG 747 within turbulence (I've now reproduced this and got PMDG involved, so no need to send more on that), and the reported occasionally sudden large wind direction changes, which I've never been able to repro and make no sense to me so far. Regards Pete

Please get version 4.236 first. I *think* I've fixed a couple of things, at least. Pete

thanks. I can't make FSX crash with that either in SP1 or SP2. However, I'm pretty sure I've fixed it now in 4.236. Please look out for that in the FSX Downloads later today, and let me know if that fixes it. Thanks, Pete

Me too, there's an England friendly on (first one with our new italian manager). Anyway, here's the progress: 1. I've definitely found and fixed the problem which was causing the weird temperature layers listed with just a big negative number. It was a silly typo (a missing '(') in a mod for temperature and wind layers I did for 4.234. 2. I think (pretty sure) that this same problem would have been the cause of the spate of FSX crashes. There's a sort of 50:50 chance whether you get the wrongly numbered layers first or the crash. 3. I can repro problems with the PMDG heading hold during turbulence using the files you sent. After the short start of this scenario, the aircraft climbs out of the turbulent patch and all is well. So to test more I descended again, to 11,000 and also went into the Weather menu, Advanced, to make sure we had cloud there with 'moderate' turbulence. The winds were light, around 7-8 knots. Doing this you can see the A/P first making small adjustments to try to stay on track, but its adjustments actually aren't necessary, and instead of getting smaller, the drift gradually gets bigger -- in this case with the light winds it gets as far as 30+ degrees out. It gets into some sort of unstable state. The wind arrow on the ND is fluttering only very slightly. Maybe the A/P is reacting too strongly to small wind changes, and maybe too fast -- possibly it should average over a few frames. Anyway, the logging in FSUIPC shows that there's nothing I'm doing which is wrong here, but I have enough now to ask PMDG to take a look. Maybe it's something they can fix in the A/P or advise me of a way to avoid it. If neither then we shall probably have to just tell folks to suppress turbulence when flying PMDG. I'm sending your files with my notes to PMDG today. ========================= That just leaves the "FL390" problem where you were seeing violent changes of wind direction. I still don't understand that one, and I can't get anything to go wrong here with what you supplied. Maybe it only happens with ASX still connected and manipulating weather? Anyway, I'll will upload FSUIPC 4.236 soon, so for any further tests please use that. Maybe the "FL390" problem will show up in the fuller logging, when you do get a chance. Best Regards Pete

Okay. Thanks for the clarification. That makes more sense to me. I think I have just found the bug which is crashing 4.235 and it might well apply to 4.234 as well, and it also accounts for those reports I've received with WeatherSet2 showing weird negative numbers for temperature layers. So that I can be sure I've fixed it for SP1, do you think you can still find the saved flight which reproduces it easily (I can't afford 2 hours), ZIP up the FLT, FSSAVE and WX files and email to petedowson@btconnect.com, please? Otherwise please check 4.236 which I'll put up later today. Thanks! Pete

I know about a crash problem with 4.235. I'm searching for this now. But with all the tests on 4.234 no one else reported a crash. That is extremely puzzling -- it is more understandable with 4.235, I think I may have taken one risk too many. So can you please confirm you actually had an FSX crash with 4.234 please? If so I'm going to have a complete re-think. Oh, and by "failed to respond" you you mean a hang rather than an actual crash? No one has reported that -- only crashes. Are you trying to use the Wind Smoothing and/or Surface Wind Limit with FSX SP1? If so, do you have problems without these? Pete

Thanks! Got them. Regarding your covering message: But even with ASX off, would the weather set in FSX still have been from ASX? I am thinking that the weather patterns in which this happens are peculiar to the way ASX is generating them. Thanks! Yes, that should be useful. If I can see the problem here with these files I'll shoot them over to PMDG for their opinion. I can't see why in the log. I'll try to reproduce it. Else I'll need more logging -- more below on this. I think it must be down to one of the changes I made in 4.235. I really can't believe it is mere coincidence. I'll do a thorough check today and upload 4.236 this evening. Please look out for it. And could you change the "Extras" logging number to 67 instead of 65 please? In fact place these lines into the [General] section of the INI file: LogSimC=2DC8-2DE8,3470-3490,0580,2DF8 Debug=Please LogExtras=67 (i.e. change 65 to 67) LogWeather=Yes (this should be there already). I think I'll put a note to this effect in the Downloads announcement. I missed asking all in the 5 or so threads to do more logging. The logs will get huge, but it'll give me the data I need in case I can't repro these events. Not sure how I get to an "event log". This information you provided: Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: ntdll.dll Fault Module Version: 6.0.6000.16386 Fault Module Timestamp: 4549bdf8 Exception Code: c0000005 Exception Offset: 0006089e OS Version: 6.0.6000.2.0.0.256.1 Locale ID: 1033 simply says it was an access protection error, way down is a system module (ntdll.dll). I'll need to repro it here to get the stack so I can see who called what to get there. Thanks. I'll be back later. Regards Pete

Ouchthe worst king. I hate those! Ah, you aren't doing the smoothing logging and weather . Sorry, I see I forgot to ask for this so far in this thread. There are about 5 concurrent threads on this stuff, it is hard to keep track! Rather than post a lot of pix, try this: First edit the FSUIPC4.INI file, adding Debug=Please to the [General] section. In FSX, before you get to anything that from past experience you think might show a problem, save a flight, then go to FSUIPC's Logging tab and enable Weather logging AND enter the number '67' in the box for "Extras", below. This sets special debugging logging data on. Carry on the flight till the problem has definitely passed, then go back to the Logging and turn both off again (Extras to 0). Zip up the Log plus the saved FLT, WX, FSSave files and send to petedowson@btconnect.com, please. Don't need any wideFS logs. If the CTD is down to me it might be necessary to run with all this logging enabled anyway till we track it down. Regards Pete

I was thinking that if my diagnosis was correct, or close, it should be easy enough to put to the test by using any joystick axis in place of the user's B737.EXE and his hardware. Then you could do it to see. For this you'd need the latest interim version of FSUIPC3 -- 3.783 -- from the Other Downloads announcement. You also need a macro file. Create a little text file containing only this: [Macros] 1=To 0BDC=Cx02000BDC and save it into the FS9 Modules folder as, say "Axis.mcro". When you load FS9 (or if it is running, reload axis assignments, buttons or keys) that macro will also be loaded. Assign an axis in FSUIPC's Axis Assignments to the new control you'll now find in the "FS controls" drop down. It will be called Axis: To 0DBC (the filename of the macro file plus the name from the definition in the file). Then whatever values that axis comes up with will be written direct to that offset. Of course with most axes you'd get a range of anything from -16384 (which would look like 49152 in that offset) to +16384. But you should be able to test what FDC makes of it. If it doesn't cause the error then we'll know immediately it must be something else, and will have to search deeper. It might be a good idea too to go into FSUIPC's Logging tab and on the right-hand-side set Monitoring for offset 0DBC as a U32. If you check "FS display" below you will see the values real time on screen. Yes, that is indeed possible when using analogue flap controls. It will happen for analogue axes not equipped with detentes, or equipped but badly calibrated, or ones meant for a different number of detentes. The answer is to always round to the nearest good value. Well, I'm sorry, but I don't think you can really prevent it. If you wish to keep FDC like this then possibly it will simply remain incompatible with some hardware implementations. In this case maybe this user will be able to persuade who'sever hardware it is to change their driver and things will be quiet again, till the next time. Happens all the time here. Aren't you used to it yet? ;-) Regards Pete

Ouch! That's a really big ouch! You are also getting weather with far too many wind and temperature layers! I don't like the look of those at all. No logs or anything up to the point of the crashes? When you say "CTD" do you mean "crashes" or literally exactly what we used to mean -- crashes to desktop with no sign of anything left, no message, no window, no complaint from Windows? If there was a message or report, I need the information from it, please. The details like Module and Address, and of course type of error -- access violation or what? Regards Pete

My school-learned French is all but forgotten through lack of use these last 50 years, but it seems you are asking about using two images (copies?) of FS2004 with PMDG's 737 and cannot find out how to configure it? This is the Support Forum for FSUIPC and my other FS modules . Are you sure you don't really need the PMDG support forum, over on AVSIM I believe? In case it is what you are thinking, I don't think PMDG supports multiple FS2004 installations with one aircraft, in a multiplayer pilot / copilot manner. Its gauges and subsystems are all tied together within the one FS installation. Regards Pete

Of course! I'm not freezing the code yet, just preparing. Whilst a lot of things look good, the few remaining problems do seem to be associated with ASX's type of weather setting. I'm sure it's not a "fault" in ASX at all, it is just that it seems to be able to produce weather scenarios which are prone to the problems I might not have managed to solveyet. Yes, great. Thanks for all your efforts on this. Regards Pete

Thanks! Pleased it is looking so good now! I'm working on the dox updates, hoping to get a proper user release out this month! ;-) Pete

Thanks for the information, but I'm fairly sure this sort of thing has been discussed and resolved before now. Doesn#t it relate to jitter affecting the Fly-by-Wire in the Airbus? You don't mention whether you are using FS9 or FSX, but either way it might be worth your while trying the latest FSUIPC version as appropriate. See the FSX Downloads or Other Downloads Announcements above. Regards Pete

I tried to reproduce the wind direction swings without success. But in the process i spotted a couple of areas where I could improve things somewhat. So, please move on to version 4.235 for further tests. This is becoming a daily thing, isn't it? It's certainly a lot of work! Regards Pete

I tried to reproduce the wind direction swings without success. But in the process i spotted a couple of areas where I could improve things somewhat. So, please move on to version 4.235 for further tests. This is becoming a daily thing, isn't it? It's certainly a lot of work! Regards Pete

I tried to reproduce the wind direction swings without success. But in the process i spotted a couple of areas where I could improve things somewhat. So, please move on to version 4.235 for further tests. This is becoming a daily thing, isn't it? It's certainly a lot of work! Regards Pete

From initial analysis, it looks like you did not stop all other FSUIPC client programs -- you appear to have "pmdgOptions.DLL" running and confusing things somewhat. You need to remove add-on DLLs when isolating clients. Also, the Log you called "only b737exe" definitely has FDC running too! It adds its entry "Connect FDC" to the Modules menu, via FSUIPC. However, you didn't do the Connect, so I don't think it interfered too much. As far as I can see the problem must be that FDC cannot cope with unexpected values in offset 0BDC. This gives the Flaps setting, and it is both a control and a read-out to show where the flaps lever is. Normally the flaps lever will be moved from one notch to another, and the values written and read here will closely approximate the notch position. For a B737 there are 9 positions, and the range here is from 0 to 16383, so the increment between each notch is about 2048. Thus, notch 0 (flaps up) is 0, 1 is 2048, and so on. But these numbers are only approximate and may vary a little from the "correct" notch value. However, it is perfectly permissable for a program such as B737.EXE to write whatever values it likes here, within the range 0-16383, and it does seem to be doing just that. I think it is merely sending the AXIS value, ranged to 0-16k. Maybe you do some sort of calibration for the notches? I can't see anything wrong really with what B737.EXE is doing, I think it is a problem in FDC -- it appears to be making assumptions as to what is permitted in that offset, and it goes wrong if there's a value there it doesn't expect. If it wants to log, announce or otherwise act upon the selected flap setting, then it needs to round the value it reads to the nearest notch value. This is what FSUIPC does when you assign a non-notched axis to Flaps directly. If the authors of B737.EXE are amenable to changing their driver, they of course could do the rounding of the Axis value themselves, before writing to offset 0BDC. That would make their program more reliable too. But really FDC should check and adjust for permissable values in any case -- there may be other programs doing the same as B737.EXE, as writing a driver to directly set offsets from axis values is easy. In fact my EPIC module, EPICINFO.DLL, could be easily programmed, in one line in its parameter file, to do the same thing. So, I think this would be very easy for Dave March to fix. In case he is not following this thread any more perhaps you would relay my assessment to him? BTW it is good to know it is the same in FSUIPC4. I'd be rather concerned if it wasn't! FSUIPC4 is supposed to be compatible with FSUIPC3! ;-) Regards Pete

No no no! Dont' send it again!!! Please! The one with everything operating would be long. There are lots of things going on. Pete

Please, please ZIP files before sending them! These are all simple text files and zip up real small. I'm sure I asked you to Zip them? You just jammed up my email for 20 minutes! I don't see the point of that. I'll look at the logs after dinner (just been called by my better half!). Regards Pete

I wouldn't have thought that to be a problem. If FSX can generate the frames that fast it can certainly process the weather at the same rate. With 50-60 fps though those FSUIPC logs are going to be really big as some of the smoothing log entries are being done several times per frame. Maybe the act of logging will noticeably slow FSX somewhat too. Sounds good. I am getting a new FSX box built and am going for Vista 64 also. I'll only have FSX + outside scenery views on that -- everything else, panels included, are on Networked XP boxes. Regards Pete

Well, it does look exactly like most of the other SimConnect installation problems reported here. Let's see: Yes, the installation log shows that part working fine. Now we need to determine whether FSUIPC4 is actually being loaded by SimConnect or not. For that, please look in the FSX Modules folder and see if there is an FSUIPC4 Log file (not the Install log, another one). If there is, paste that here. In general doing things like that is a very bad idea, and likely to make matters worse not better. To start with, NEVER just delete an installed program, uninstall it instead. Also, after doing so, the additional folders to be deleted include several outside of the main FSX one -- there's one in your "My Documents", and, more importantly "C:\Documents and Settings\Haleem\Application Data\Microsoft\FSX". Additionally, it is not easy to delete SimConnect -- uninstalling won't do it. But if FSX is working okay apart from SimConnect, that is over-reacting in any case. If SimConnect isn't working we need first to find out whether it's just the SP1 or SP2 versions, or also the original RTM version. All three should be installed on your system and all these should work. First, let's find out if FSUIPC4 is even being loaded, and take it from there. Regards Pete