Pete Dowson

Please let me know. First make sure the DLL is okay by re-downloading it. Also, if there is an FSUIPC.LOG file produced, let me see it. Also try adding "InitDelay=10" to the [General] section of the FSUIPC.INI file (this will be in the Modules folder -- if there isn't one, just make a small Text file in Notepad containing just [General] InitDelay=10 and save it as "FSUIPC.INI" in the Modules folder.) Let me know, whatever, please. Regards, Pete

All I can think of is reading the real axis using the appropriate EPL command and then set it to the POV or Soft Axis. f you do this in a loop with a delay it should work, I think. (My memory of EPIC matters is disappearing fast I'm afraid :? ). Regards, Pete

Sorry, no I haven't. Are there no messages? What actually happens? Is the an FSUIPC.LOG or FSUIPC.INI file created in the Modules folder? Which version of FSUIPC did you install? Do you have any other add-ons in your FS2004 installation? In case your copy of FSUIPC.DLL is corrupted you should re-download it and check again. Really, until you register it or run some program which interfaces to it, it is doing nothing much at all. If you have something installed which uses it then maybe that is causing the problem. Try deleting the FS9.CFG file to make FS generate a new one (you'll have to reset all the FS options if you do this). Also temporarily remove any other third-party DLLs installed in the Modules folder, if you have add-ons installed. Regards, Pete

I think the granularity is 100 fpm, and I don't see any way to change it. Sorry. Regards, Pete

No sorry. It does really sound like a sound problem (sorry, no pun intended). Try using DXDiag and reducing the DirectX sound acceleration one notch, then two. I have heard this gives smoother frame rates in FS too as it spends less time filling up the sound cards buffers. Regards, Pete

No. I think that is defined in the AIR file. It may be overridable in the AIRCRAFT.CFG file. Creep up to 5000 feet? Use the afterburners for take off and point the nose to the sky on rotation! It will reach 5000 feet before you know it! :D 100 fpm is the default? Surely not? Even a Cessna defaults to several hundred feet per minute. I know nothing which defaults to 100 feet per minute -- that's only a little over 18" per second! I can go up stairs faster than that and I'm 60 years old with no jets attached! :) Anyway, the V/S you need will be completely different at different altitudes. You should not leave it (cannot leave it!) to any "default", you have to set it using the V/S setting for the A/P. Regards, Pete

Actually I could get round both those problems simply by watching for changes in the FS standby frequencies and copying changes to the PFC display. The only part I wouldn't want to do is the reverse -- have the PFC controls manipulate the FS standby and swap operation. As you may have noticed, on the PFC avionics it is much more efficient and responsive to adjust the standby then swap, rather than adjust the main frequency directly -- try the latter on one of the NAV's when the standby display shows the radial to see what I mean. The reason for this difference is that the standby frequencies are currently totally contained within the PFC driver, but for changing in-use frequencies each increment and decrement has to be passed on to FS. Provided you don't display or use the FS radio stack on screen, if PFC copies change FS standby values to the PFC avionics, that would meet the need, wouldn't it? If so I'll add it to the list. Regards, Pete

[quote name="Frank.O What about this one' date=' Pete?

No bug that I've heard of. The only one so far was a problem in versions 3.00 and 3.01 of FSUIPC with names containing accented characters (all fixed long ago). And, so far at least, there's only been one mistake I know from SimMarket, and that was issuing two FSUIPC keys to someone instead of one FSUIPC and one WideFS. Maybe they got your request mixed up, but it would be most unusual. The emailed details themselves are generated by program so should be free from error (famous last words :D ), or at least self-consistent. In ALL the other instances of user problems it has been incorrect data entry. Your name, email and Key must all be exact to the character. Computers are stupid, they believe what you tell them. Try cutting and pasting from the SimMarket email if you are not sure. There's no change in keys for different versions and will not be till at least version 4, which won't happen till FS2006, earliest. :) --- unless something drastic happens which forces me to change the system, of course. :shock: Good. glad it is sorted. BTW it is "SimMarket" not "SimWare", just in case this confuses other readers. SimWare are a well known flight-Sim add-on dealer operating out of Belgium (I think), and is quite distinct from SimFlight and SimMarket. Regards, Pete

Not a problem. That's what this forum is for. Regards, Pete

Yes. It will be a Beta version with a time limit anyway. Probably end November now. Just keep the numbers reasonably low please. Write to me at petedowson@btconnect.com and I'll send it by reply there. I'll have it ready over the weekend some time. Regards, Pete

If you are talking about FSUIPC version 3, yes. You can actually check these things by looking at the FSUIPC LOG. There's no free developer's key. I'd really hoped that developers would actually register FSUIPC, as I don't charge for either developer support nor all the work on the SDK. If you really don't want to register then you'll need an access key for your program. The access registration documentation in the FSUIPC SDK will tell you all about that. Correct. But if you want your program to be used by other, non-registered, folks then it will need the key. Yes. If it is free ware (or you make a small charge merely to cover distribution costs, for instance) then the key would be free. If you want an interim key (one with a time limit on) whilst you are developing and before you've decided about free/payware status, let me know. You'll need to send an email to my standard email address -- see the details in the Freeware Keys "sticky" above. But please read the registration document first. The two methods are alternatives. The manual entry facility was only to allow older programs or modules or gauges to be registered without making program changes. It is better for the user if the registration is done automatically by the program. Regards, Pete

Once I've done them, they're in, unless I'm suspecting problems, which in this case I'm not. However, I've no schedule for 3.12 at present. Would you like an interim Beta version to test with? Regards, Pete

WideFS is no longer freeware, and you cannot use Version 5 WideFS or earlier with FSUIPC 3 or later. You need WideFS 6 and it is not free. Sorry. Regards, Pete

Ah, yes. Enrico is a whole generation and a half younger than I! :) Yes. Regards, Pete

With only WideClient on the client PC, you've got nothing to run on WideFS. You've got everything on the Server! There's no point in running WideFS in that case. You could install all the following programs on the Client instead, and save the Server taking a lot of processor and memory from FS: ActiveSky wxRE, Squawkbox, ServInfo, Roger Wilco and maybe also RWTS, but I don't know what that is. If you moved all this it would be a good idea to have your Internet connection for ActiveSky, SB and RW on the client too, not via the Server which will put more load on the Network needlessly. Yes, well obviously then you need to install SB and Servinfo on the Client. You install programs on the machines on which you want them to run. This is normal practice with computers. :D This is presumably because you told WideClient to load and run Servinfo on the Client from the client's C: disk, and you forgot to install it there? There's no way WideClient can run a program which isn't available. Windows error 2 is "file not found". Regards, Pete

Ah, wellI can't keep doing this stuff forever. There'll be other and better alternatives one day, surely? Maybe I need a young apprentice to train up? :lol: Thank you very much! You've made my day :D :D Regards, Pete

Which website? I'll go look and confirm or deny! :wink: I worked for large corporations till the first PCs arrived. I started with a Commodore Pet 2001 and a little later an Apple II. I wrote a word processor called "Wordcraft" which sold well enough for me to leave the 'big corporation', and I've not worked for anyone else since then (about 1979). Along with two others I invented and named the "Dongle" -- my only regret is not having patented it back then! Oddly, when many software houses started using dongles we stopped and went to a registration system instead. :) Regards, Pete

Why must you reload FS9 because EPICMAPPER shuts down? This really is a problem for EPICMAPPER support. I do not know the program, sorry. Go to their support and show them the message. Maybe they have a fix already. If you think you have a WideFS problem, then please check the Logs. There will be both a WideServer.Log (in the FS Modules folder) and a WideClient.Log (in the folder from which you run WideClient). Whether these are relevant I have no idea. You don't say whether you are even running EPICMAPPER on a Client PC or not! Pete

Unless you are using FSMeteo or some other external program, the only Visibility options which are any use are those marked with ***. What is "most realistic" depends where you are. I live in and fly from England, and the default values I put in suit me fine. If I were you I'd just set the facilities to please yourself. Regards, Pete

You can re-program the PFC gear handle for something else in FSUIPC (assuming you are a registered user). Then it won't try to assert itself. Pete

The problem is that all of that code was written in FS2000 days when there was no COM2. I can add support for it, but it is a big job so I would need to schedule it for a quieter time. There's so much still to do in FSUIPC for FS2004 that I cannot see this happening before Christmas, I'm afraid. But it is on the list. Why? Surely, with a REAL stack you don't also display the FS panel stack? It is much more efficient for the PFC to keep and maintain its own standby frequencies, and these then apply to all FS aircraft including those without. I really would be very reluctant to reduce the PFC DLLs independence in that area. If there was good justification for it I would relent, but I don't see it really. The most I would consider is copying the PFC standby frequencies to the FS standbys, so they look the same if you were ever to look (why?). But changing the FS ones or using the FS "swap" button would then not update the PFC standby displays. If that is acceptable I'll add it to the list. Regards, Pete

Exceptional news! Thank you Pete. I'll be greatly looking forward to your next release. Actually I've decided to reverse the indication: 00 = ready to fly, FF = not ready. That way programs which use it to hold off before doing something won't be held off forever on previous versions of FSUIPC or FS. Regards, Pete

There's a picture somewhere? Where? Don't I look old? I've always looked old. I started going bald in my late twenties! :? Well, really the only change with the commercial side is that I charge for the additional facilities, the user facilities, not the actual interface into FSUIPC. That's free as it always was. I expect commercial developers to pay towards this mainly for the support and SDK they get, and for the right to publish their software with FSUIPC included. They negotiate with me about this. Looking at it like that the arrangement is almost identical to Adam Szofran's original FS5IPC and FS6IPC licences -- his offerings were free for users and feeware, but he charged the commercial guys. My change to "semi-payware" caused a ruckus purely because I was effectively generous enough not to charge anyone anything for four years, even though I was working full time on it. I didn't need the money then, so I didn't charge. Now I do, so I do. Microsoft is well aware of the "reverse engineering" which I and many others do. Take a look at some of the other excellent products -- scenery compilers, AI traffic developers, AFCAD, FSAssist and most of Lago's products. The list of programs using "reverse engineered" knowledge of FS innards is not quite endless, but there's a lot about. Some is out and out commercial, some is complete freeware, mine is a bit in-between. But the fact is that it all enriches the FS world and I'm sure Microsoft are pleased. No doubt if they had the staff and time and money to do it, they'd provide toolkits in a more timely fashion and with a depth of detail which would make them much more useful, but it isn't a commercial reality for them. And why, when there are so many folks doing this stuff for them? Regards, Pete

It didn't appear to. I was watching the list of windows in ProcExp whilst I loaded a flight. Do you want me to double-check? I have it working now for FS2004, but unfortunately there's no such code in FS2002 (so it isn't worth me looking at FS2000 either). So I've implemented it for FS2004 only. The BYTE at offset 0x3364 will be zero whilst things are loading, changing to 0xFF when the simulator is ready. Regards, Pete