Pete Dowson

The former. FSUIPC has always performed proportional braking its own way -- this dates from FS2000 where there were no proportional braking facilities in FS. And I prefer the slower release of pressure my algorithm gives. Seems more realistic. :wink: It takes either 65721 (BRAKES_RIGHT) or 66388 (AXIS_BRAKE_RIGHT_SET) for right brakes, and either 65720 (BRAKES_LEFT) or 66387 (AXIS_BRAKE_LEFT_SET) for left brakes. But it also takes 65588 (BRAKES) as both brakes and operates them together, so you could simply convert the 66387 input into 65588 and leave the rest to FSUIPC. That's probably what I would do. This isn't possible if you are using the gauge event interception, though, as it doesn't seem to allow changes, so your method would then be best. But I'm not sure at present if that interception occurs AFTER the control has been through the WM_COMMAND message process or before -- it would make a difference because you'd not want the right brake copy altered by FSUIPC calibration twice. You could calibrate only left, though, and leave the right, or both, so I suppose it is solvable. Experimentation would show the best way. The axis logging facilities in FSUIPC may help too -- they occur not in the WM_COMMAND stage but the gauge interception. Regards, Pete

The ordinary "brakes" control (BRAKES) would do that -- operating left and right brakes simultaneously, but unfortunately it isn't recognised by FS2004 as an axis control, only a button control (it's the '.' key). So the only way would mean a change to FSUIPC to allow a nominated axis, such as AXIS_BRAKE_LEFT to operate both left and right -- in the same way as I already map Throttle 1, and so on, to other engine throttles. This isn't difficult to do, but unfortunately you ask at a bad time. Just last week I managed to finish up a number of important changes and get FSUIPC 3.47 out. I now have less than a week to tidy up some other things before my wife and I go on holiday. I may be able to look at this in April if you've not found another solution by then. Ask Bob Church if he knows of a ready-made solution already available (http://www.stickworks.com). Otherwise, get back to me, say mid-April, please. Regards, Pete

I must admit I hadn't thought of that one. At least you can pronounce it, just. :D Pete

Well, I can see the trouble there being when you get to version B and so on. They'll all be different products that way. You'd need a name separate from the version. But I'm afraid that I am exactly the wrong person to advise on names. Look at my terrible examples: FSUIPC (derived from the earlier FS6IPC by having a "U" for "Universal" instead of a version number), and WideFS, just because the original was piggy-backed onto WidevieW! And the confusion that has caused over the years :? Best regards Pete

Sorry. No need to shout at me. :cry: Seems you really need to discuss this with Dave, then, not I? I'm sure he will be able to sort it out, perhaps with some logging. Regards, Pete

In that case it is probably only possible through offset 3110, where you can send any FS control and most of the add-on FSUIPC ones too. Well you can send FS keypresses via offset 3200, but I really wouldn't recommend that when all FS keypresses are re-assignable (i.e. 'S' may not be assigned that way), and they are all available as controls in any case. There's a complete list of FS2004 controls included in the FSUIPC.ZIP. You need the numeric equivalent. I think 'S' is normally assigned to "VIEW_MODE". You can find out via the FS CFG file -- assignments are in the [KEYBOARD_MAIN] section. Regards, Pete

There's probably something wrong with the user Key, then. The checking of user keys was tightened up some time ago. So far, all the cases where a program has worked with FSUIPC non-user registered but not registered have turned out to be due to bad user keys. I can check yours here. Rather than send me the log, please just Zip up your normal FSUIPC.KEY file and send it to me at petedowson@btconnect.com. Regards, Pete

Thanks for the clarification Dave! Seems that some folks are still using very old versions! Best regards, Pete

By "the box" I assume you mean the FSUIPC options dialogue, via the Modules-FSUIPC menu item? That is a standard Windows dialogue, handled entirely by standard Windows libraries, and the sizes are not set by my programming but by Windows. The only times I've known it to go wrong in the way you describe is when the two standard libraries needed for dialogues do not match. Mostly this seems to be due to drivers (usually video drivers) installing an older or incompatible version of COMCTL32.DLL. You will need to see if you can re-install the correct Windows version of that standard library. If installing more up to date (WinXP) video drivers doesn't accomplish this, then perhaps Katy Pluta over in the FS2004 Forum may be able to help. She is very knowledgeable about Windows and will undoubtedly be able to tell you how to proceed. Regards, Pete

I think Enrico said he was away from Wednesday, but I don't know if that means he won't be answering emails. He seems to answer them wherever he is, unlike me! (When I'm away I am totally disconnected! :wink: ). Regards, Pete

It's just that Enrico hasn't updated the words themselves for a couple of years or so. I'll drop him a line. Yes, that's it. It only happens once. Probably you didn't see it and it disappeared. I see this attempt is 1075 seconds into the FS session (18 minutes). It's a little out of date then. I released 3.47 last week. :wink: Regards Pete

I don't have a site, only this Forum. Do you mean Enrico Schiratti's page containing my software? Someone would need to write to him and point out a mistake if there is one. Can you be more specific about where you are reading what, please? I keep the lists of versions in this Forum up to date, and this would be the main definitive point of reference. See announcements near the top. Are you using a properly registered install of FSUIPC? If not, check the FSUIPC Log file -- I expect it will show that it's not an accredited program. That probably explains it then. Didn't you get a Message Box from FSUIPC too? Unregistered programs can only get certain information like version numbers. But the fact that they are not accredited will be logged, and the first such one used in an FS session should give rise to a Message Box telling you so (and a beep). If you are in full screen mode that message may be hiding behind it. It's per user. I don't like systems which restrict installation to one PC. Regards, Pete

I doubt that you have a spare axis to assign this, and really there is no point -- a rocker switch is as good and more realistic. The rocker control will simply be operating the normal trim up and trim down controls in FS. These won't be any point at all in attempting to use FSUIPC's elevator trim axis calibration in that case, none at all -- as you found out. There's no adjustment available in FS for the trim up and down controls, so no way really possible for a mere update to an FSUIPC version to change that. Try using the "home" and "end" keys on the keyboard and checking the trim action those provide. If that's comparable to the rocker on your yoke then that's correct. The only other possibility I can think of is that you've programmed the trim buttons in FSUIPC's buttons page as well as in the FS Options-Controls-Assignments dialogue, and so have a double action, which would certainly make it operate faster. You should only assign functions to switches and buttons in one place or the other, not both. Regards, Pete

If you have not assigned a trim axis in FS then there's no point in trying to use FSUIPC to calibrate it! What are you using for trim? If it's a button or lever you are using then the trim is an ordinary increment/decrement system in FS, the same as pressing the "Home" and "End" keys on the keyboard. They accelerate automatically if held. What instructions? There is no sensitivity adjustment in FSUIPC. If you have axes assigned in FS you can reduce sensitivity there. But it sounds like you aren't even using a trim axis. Regards, Pete

You omitted what is probably the most important part of the Log -- the few lines at the start. In particular the information about the Version number of FSUIPC. Please check the Recent Release Changes announcement at the top of the forum, and in particular change #20 in FSUIPC 3.47, which seems to cover this case exactly. Regards, Pete

It sounds like FDC is just wanting to grab so many slots from the start of the table then, instead of doing as documented and scanning down for the vacant entries. :( Regards, Pete

Check offset 3365 in the programmer's guide document. Pete

You don't get anything reading it. It's for writing, not reading. Regards Pete

Well, I've no expertise in that area, but it looks to me like it has got to be either a faulty device, or (possibly more likely) a bad driver! I've had trouble with FTDI drivers before -- they emulate a serial port on a USB link -- and they were fixed by downloading a more up to date version. The sympton was a dying device as well, it would work for so long then stop. I think the drivers supplied were Win98/Me really -- the same ones were fine on a machine running Win98SE. For WinXP I had to find newer drivers. Try http://www.ftdichip.com. Regards, Pete

I don't know ShowADV. Is that like the ShowText utility packaged with AdvDisplay? Is it running on the same PC as all those others? What has "not enough hot key slots" got to do with the sequence? there should certainly be enough slots for both Radar Contact and FDC! What "add-ons" other than those you list above? Sorry, you lost me there. Check the WideClient.Log and WideServer.Log files. See if there any errors reported. Have you made any changes to the WideFS INI files? I don't know all of those programs you mention, but you may need to change the ApplicationDelay -- it should be defaulting to 0, but this may enable one of your programs to monopolise the interface. Also, I think both Radar Contact and FDC need good use of the sound card. Don't they clash somewhat on the same PC? Regards, Pete

It's available in the Avsim library (http://www.avsim.com). Author is Joshua Robertson. The latest version is there now, filename realtime_159172.zip. Regards, Pete

There is an option in FS which says to use System time or Flight time. Check the Options menu. Mind you, some have said that doesn't work for them. It's been an option in FS for many versions now, but I must admit I use "FSRealTime" to control the FS time. Regards, Pete

What program is giving this "error code 43"? What do the makers say? Regards, Pete

That is doubtful given our past history. Pete

I would assume so also, but you should research your needs first before making any assumptions. Everything there is for developers is included in the FSUIPC SDK, see http://www.schiratti.com/dowson. There is only one "FSUIPC", not a commercial one and a free one. Programs need an access key to interface to it. This is all described in the Access Registration document inside the SDK. There is no fixed price -- see that document. Regards Pete