Pete Dowson

For scrolling text you mean? I am emulating the same thing as the FS display, so it takes the scroll speed and display time from that, or at least I adjusted it to match as well as I could. Is it adjustable? I could make the scroll speed in AdvDisplay adjustable I suppose. Please clarify exactly what it is that is too fast and tell me how much slower you need it. If it is for ATIS messages, those are pretty long and the scroll speed is supposed to be timed so that the speech and text almost match. Best to make a bigger window to give more time to read it all. If it isn't the scroll speed, but only the time on display before being cleared or replaced, then I'm afraid that is completely under the caller's control. Regards, Pete

Can you show me the FSUIPC Log please? Which Tabs are there showing? What does it say about your registration on the first (About) options page? If all the other Tabs are there, then your registration is okay. There's really only one reason the Joysticks tab might not be there, and that is that FSUIPC cannot find the correct Joystick reading routines in CONTROLS.DLL, so could you right-click on the Controls.DLL (in the Modules folder), select "Properties" then "Version" and read the Version number please. One other (unlikely?) possibility is that it is there, but, as it is the right-most tab, its just not visible on your screen. In case this is it, could you tell me your screen resolution and Windows font size (normal, large, or have you set something specific?). If you cannot figure these out, maybe you could take a picture (ALT + PrtScr when the FSUIPC options have focus, then paste into the Windows Paint program and save as a BitMap). Thanks. Regards, Pete

At the end? Was it still in the [General] section? Otherwise it would have done nothing. Ouch. The only thing you can do there is report it to Microsoft. Sorry, there's nothing I can do with that. Even the little change with InitDelay=0 only changes timings slightly, nothing else, and I've found that doesn't work in all circumstances either. I'm hoping Microsoft will see fit to update something sometime, whether it's in DX9 or FS itself, I don't know, but I have certainly proven here that it isn't FSUIPC or any of my modules which are responsible. Just minor changes in timing affects it, and almost any of the modules can do that, as can a change in video driver, which was an earlier theory. Since it happens without any add-on modules, or with just certain ones (here, for instance, with *only* Lago's ViMaCore2004, or my AdvDisplay, or my PFC or my FSUIPC), and with a variety of different video card types, the only common factors left are DX9 and FS itself. When I managed to be able to reliably reproduce the black screen problem here, I was quite pleased because it afforded me the opportunity to do a detailed investigation. And it was doing that which I learned that, even making FSUIPC do nothing (i.e. cutting out all the code EXCEPT subclassing the FS window and doing nothing in there either) and making no difference, it was nothing I could correct. When I found the same with only the other modules I mentioned present, the common factor being the delayed subclass operation, I tried cutting that delay out, and with success -- but only in the sequence I was using. Since then I found a different sequence which still gives the black screen, and this time with no add-in modules too. Still, some improvement is better than nothing, so I will re-issue FSUIPC with "InitDelay" defaulting to 0, and also versions of AdvDisplay and PFC with no delayed subclass. But I will not (cannot) guarantee that it will be better I'm afraid. Just that it might be and is on at least mine and several other folks' systems. Regards, Pete

Does it only do it when WideClient has focus? Otherwise it won't even see you press scroll lock. Do you have the parameter set in your WideClient PC to transmit keys to the Server? ("SendKeyPresses=Yes"). If so, then any non=system key presses seen by WideClient (assuming it has focus) will certainly be sent to FS. However, "scroll lock" doesn't put my FS into Pause mode -- do you have that key re-programmed in FS or FSUIPC? If none of these things apply, then it is something to do with whatever program you are using on the Client. If must be picking up the key and setting Pause through the normal FSUIPC interface. You can check that by Logging IPC Writes in FSUIPC and seeing if something is writing to the Pause control (offset 0262). If so this certainly won't be WideFS of its own volition, it doesn't write anything that applications don't request. Regards, Pete

Unless the wind has suddenly changed direction that should not be possible whilst in the air, as the whole aircraft is moving with the air mass. I would give up Flight Simulator and try another program if I thought it was really that bad. There must surely be some other explanation for what you are experiencing. Pete

Do you mean the randomizer in FSUIPC? You had it on? Or is this something in ActiveWeather? The probability system for the random events in FSUIPC hasn't changed since FS2000 days. I've rarely if ever seen icing being set to more than 2, and it is usually 1 or 0. And no one has mentioned any such problem in the three or four yers it's been there. Certainly, it wouldn't be much of a randomiser if you didn't rarely get a 4. But you are implying you get it quite often. :? Regards, Pete

How come? Freeware has free access. I provide the keys free, by return, upon application. There would be no justification whatsoever, if that is what I did. I would have no leg to stand on. It is evident that you haven't actually bothered to read much of what I've published about this. Perhaps you would care to peruse the documentation, such as that in the Announcements and stickies in this Forum, and maybe look at some of the threads below in which this misunderstanding has been argued at length. I have no wish to ignore or delete messages which show legitimate concerns, and will gladly answer any such so that any others in doubt will also gain from the clarification. If you wish free keys for any of your freeware works, merely apply to me at petedowson@btconnect.com as so many others have done already. I will send you a full guide with details of what I need to make the keys. Regards, Pete

On a sudden change of wind direction, yet, but that's a passing thing, unless he's talking about a situation like a tornado or whirlwind, which would have the arcraft spinning for sure! Strange. Most all videos I've see of cross-wind landings at Kai-Tek where certainly crabbed. Regards, Pete

How odd. I've just discovered another way to make the video drivers give me that black screen, and that's by trying to change into full screen mode from a very small windowed screen, rather than, as I was before, a maximised or reasonably big screen. Obviously it is a timing problem in the relationship between FS. DX9 and video drivers, and all I'm doing messing with the Init delay is moving some times about. I don't think there's currently a real fix. Maybe different drivers help (they change the timings). Maybe, one day, we'll get a new version of DX9 which won't exhibit the problem. Regards, Pete

Ah, wind shear is something else. But that would mainly give a sudden change in airspeed, sometimes fatally so, more than a weather vaning, though obviously a light plane would get swung about a bit. But if it survived it, it would settle down again. Pete

Sorry, then. I've got no other theories. Maybe there's a bug in FS2004 where is doesn't realise the pitot heat is on? Have you checked whether there is icing set for the clouds? Can you tell me how "intense" it is? (I.e. what's the "icing" value shown by WeatherSet2?). I still think it must be something to do with that. I know of no other mechanism for a wrong airspeed reading, and since it seems to be associated with clouds it must have somerthing to do with icing, surely? Maybe FS2004 likes the Anti-Ice to be turned on too. did you try that? Regards, Pete

Right. That's probably why I've never seen them -- the lessons are written in ABL, and interpreted by the ABL script interpreter. I didn't know you could save and resume these -- you couldn't with the older APL based "adventures" and lessons. I'll change AutoSave to delete the old copies of these when it deletes the FLT and WX files. Thanks for telling me. Regards, Pete

Because I've never heard of any .ABL files being saved, and do nothing to delete any old ones. Can you tell me more? Why were ABL files being saved in any case? I only know about .FLT and .WX files. If .ABL files are also produced in certain circumstances then I can certainly change the program to delete those too, but I have never heard of them and no one else has reported this at all. Are they to do with pilot training exercises or something like that? You should understand that AutoSave does not actualy save any files itself, it only calls the routine in FS to do this, the same routine that you could call by using the Save Flight menu (or the ; key). If that saves new files in some circumstances then I need to know so I can delete them after the set number. Regards, Pete

Sounds exactly like icing. Switch on your pitot heat! I never leave the ground without it, neither should you! Regards, Pete

There's no such thing as weathervaning in the air. When flying, your aircraft is in the moving air. If there is a sidewind, you will drift to one side, but you never get blown around to face into wind, as there is no "pivot" operating as there is on the ground. You and the air mass are simply moving relative to the ground, but your nose is pointing where you tell it to, and your propellers or jets are pulling you though the air in that direction. Ignore the gound for now. That is sweeping by in another direction! :) To compensate for a cross-wind you can either crab to the runway -- i.e. turn towards the wind enough so that you stay in line with the extended runway centreline, or you can try fling "croos-controlled" -- that it you head towards the runway, but use the ailerons to turn into wind (dip the windward wing) and use OPPOSITE rudder to stop you actually turning as a result. Most airliner pilots seem to use crabbing, rather than risk any chance of a wing strike or one of the jet engine pods hitting ground. The strain then is placed on the landing gear, unless he can straighten up just before touch down. Some crabbed landings I've seen videos of at Kai Tek are frightening! Looks like the landing gear would be torn straight off at some of the touchdown angles! Both techiniques are possible in a light aircraft, and fun to practice. In fact, when my eyes were good enough for me to fly for real, the cross-controlled approach was really the most 'fun' in a Cessna 150. :) I don't think any of this is really any different in FS2004, by the way. Maybe a touch more realistic, if anything. Regards, Pete

The multiplayer interface is completely separate to the WideFS link, and it sounds like it is that part which you are having trouble with. I know that the multiplayer interface changed in FS between FS2002 and FS2004, but how you deal with that I have no idea I'm afraid. I don't use Multiplayer or Squawkbox. There are some SB and MP users who do pop in here now and then, so I hope they see your message and can help, but otherwise you may do better in a Squawkbox support place. Is there one? Sorry not to be able to help. Regards, Pete

I don't think you can limit the range of winds like that. As for how FS's dialogues work, I to find them quite confusing, but then I've not tried any of their "Help" text. Doesn't it explain anything there? Weathervaning still happens in FS2004, though I find it is much reduced compared to FS2002 and FS200 where it was ridiculous. In a light aircraft like the Cessna 172 or 182 any winds over a few knots have a noticeable affect. I think it isn't far of reality now though, compatring it with my experiences in a real Cessna 150 trainer years ago. With any winds over 10-15 knots it was a devil of a job to steer straight on the ground. Well I certainly thought that, and still do, but I gave in to requests for it and spent many hours trying to make one work, without success. I just can't get into the parts of FS2004 I would need to to implement it. Sorry. I may have another go when I get time, but I couldn't afford to let everything else slide. Regards, Pete

Doesn't my explanation a couple of messages up cover it, then? Pete

Great! Thanks for letting me know. I'll make a proper release tomorrow, probably, but it will be the same as the one you have. Regards, Pete

So, how come you got "windows say autosave.dll is not compatible with fs2004" before? I need a constent story please. :( Without any more information I'm afraid I cannot progress this any further. It works fine on Win2000 Pro here, and there is really nothing which is Windows dependent until it actualy wants to save something in any case. I did ask for your FS2004 version and build. Can you not find it? (Help-About). Als i asked for the exact title text in FS when it is ready to fly. Can you not tell me that either? Also, if you can get some sort of dump, like DrWatson (*see FSUIPC documentation "If FS crashes ..." near the end) then I can take a look, but there is really nothing in AutoSave to crash FS. Version 1.41 is not compatible with FS2004. You should get a warning from FS telling you so. If you don't, then there is something odd. Sorry, unless you want to give me more details I cannot progress this any further. Regards, Pete

Yes, as I said originally, the problems most definitely seem realted to video drivers. However, I was surprised when I upgraded my motherboard and processor. Using the exact same video drivers I went from not being able to reproduce the problem at all, no matter what I did, to being able to reproduce it at will, by using a specific sequence of actions. So, although it is a driver (+ DX9) issue, it is a timing problem too I think -- my fast processor allowed me to replicate the problem. The benefit of that was that it did allow me to make adjustments in some of my modules to make that timing "better" again! :) Thanks for the feedback! Regards, Pete

In that case I can only think it's the aircraft model itself. Evidently no amount of "fiddling" the throttle input would do the job for you. I suppose you made sure you were heavy enough? Full tanks? Perhaps there are some parameters in the AIRCRAFT.CFG file which you can change which will help, but this is not an area I know enough about to advise on, I'm afraid. Hopefully you can get it sorted if you can find some asircraft modelling experts to chat about it with. Sorry I'm no use here. Good luck, Pete

(1) No, no other reports. (2) All the changes in 3.06 are listed in the History document, and in the IMPORTANT announcement in this Forum. Maybe you had wind smoothing enabled. That does nothing when on the ground, it only tackles the wind once you take off. It only affects the global wind, which, if you were using a weather theme or downloaded weather wouldn't actually have any visible affect. It shouldn't cause stutters (and doesn't here), but it is certainly a possibility. The weather stuff is rather finicky. The change in 3.06 was to default the smoothing action off for FS's own weather (it's only enabled now via the FS weather change checkbox in the Technical page). Regards, Pete

Thanks. I don't think it was an SHFolder missing problem in any caseI get the main folder from that, but add "Flight Simulator Files" to the end. I now think this is only correct for English language versions of FS2004. In the version of AutoSave I sent I obtain the final folder name from FS's own "Language.DLL", so it should now work. When and if you confirm this, I will make a new release. It also affects the FSUIPC facility to load Flights under control from an external program, so when I know AutoSave is okay I will make the same changes to FSUIPC. Thanks & Regards, Pete

No. It only stops YOU moving them. It cannot control where FS puts them. I think what you are seeing is a general complaint with FS2004. I don't think there's an answer. Sorry, what's a "version through PFC"? Regards, Pete