-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
fsuipcv4.53 and VRINSIGHT jetpit
Pete Dowson replied to romi's topic in FSUIPC Support Pete Dowson Modules
It will be either because you purchased the wrong key -- one for FS9 when you have FSX, or vice versa, or because you are not following the instructions and entering everything (name, address, key) correctly.Use cut and paste if you cannot copy. Regards Pete -
Strange rudder issues in PMDG JS41
Pete Dowson replied to 1master's topic in FSUIPC Support Pete Dowson Modules
If it still does it without FSUIPC doing anything, it is obviously either a problem in your FS assignments or in the aircraft itself. That is NOT a default INI! Didn't you even bother to test it without assigning anything in FSUIPC? That's what I asked -- use a default INI first, not simply delete the IN and re-create it! :-( 0=0R,1,D,36,0,0,0 ... SteeringTiller=-14780,-32,224,14652/24 You assigned a steering tiller, not a rudder! If you are assigning the rudder in FS and a steering tiller in FSUIPC, then, whilst on the ground and less than 60 knots you will have two controls operating the rudder!!! If you wish to use the FSUIPC steering tiller you must assign the rudder in FSUIPC too, so it can switch from one to the other when needed. Please do read about these things before using them. Regards Pete -
They aren't so much "hot keys" as simply your current Key assignments, which you can access via the Options-Settings-Controls menu in FS. They merely assign keypresses to FS controls, just as you can do for Buttons and as you can do for a greater range of controls in FSUIPC. You "create" key assignments in the FS key assignments menu. You have access to all of the possible controls in FSUIPC, and additional ones created for you by FSUIPC. There are no FS or FSUIPC controls for individual sound settings because they are not exported by FS and no one has found a way to do it. I expect you would need to write a program to hook into the DirectSound calls. "Sound toggle" is simply one of the well known FS controls, all of which are listed in my FS controls lists and assignable in FSUIPC, and some of which are assignable in FS's assignments menu. There are none for separate sounds. Pete
-
I don't know why you are here in the FSUIPC, WideFS support Forum? Try the IYP support forum: http://www.itsyourplane.com/%5Cstartup.forums.asp Regards Pete
-
What "IYP Trial"? What is crashing? You don't say. The picture shows a problem in .NET Framework. Neither FS nor any of my programs use that package. I think you may be in the wrong place -- you need IYP Support. Maybe you need to install a compatible version of .NET framework? Regards Pete
-
Strange rudder issues in PMDG JS41
Pete Dowson replied to 1master's topic in FSUIPC Support Pete Dowson Modules
Sounds exactly like you have two assignments to the rudder, maybe one in FS and one in FSUIPC, or even two in either. Yaw damper isn't relevant. If it only happens with that one aircraft it is some specific assignment applying to that aircraft. You must be missing something. Try removing the FSUIPC INI file from the FS Modules folder before loading FS, so that FSUIPC defaults. If that fixes it, you have some setting, some assignment, in FSUIPC which is doing it. Regards Pete -
Of course. It isn't tied to any specific hardware, it is tied to you, the purchaser. Just re-enter your registration details exactly as you first did. Regards Pete
-
You'd have to read the plan which presumably contains the frequencies? Or else look them up in some database you'd need to find or build. There's no way I know to get them out of FS very easily. I think, for FSX, SimConnect has such facilities, but that would mean writing a proper program, not a Lua plug-in, to access SimConnect. Regards Pete
-
Really there is no need to reproduce the whole of the PM stuff here. The only part you needed to notice was: What's the "mask"? Where's that mentioned anywhere, and why 101? Just assign to the FSUIPC control "Offset word set" with offset 04F4 and a parameter of 100 + the value from the list for the switch you want. Sorry, I don't do tutorials, and I cannot undertake to support PM which is not even my program. For FSUIPC offset controls all you need to know is that a BYTE is 8 bits and is 1 byte long, a WORD is 16 bits and is 2 bytes long, a DWORD is 32 bits and is 4 bytes long. If you need to manipulate bits, remember that bit 0 is the lowest bit, worth 1, bit 1 is worth 2 and so on, doubling each time. I recommend you go to the MyCockpit PM forums for PM assistance. There are lots of cockpit builders there using PM: http://www.mycockpit.org/forums/forumdi27981&f=99 Regards Pete
-
But moving a module in and out of a folder is probably a lot simpler and faster than selecting an option in a menu, even assuming I could provide such an option without a re-write. Or, another way, would be to simply pull the plug out of the unit -- power or serial connection. If they are proper PFC axes then yes, of course. They are available for enabling and calibrating like any other axes in the flight controls and trims page. I'm rather surprised you've never looked? Regards Pete
-
MakeRwys - NTVDM CPU illegal instruction
Pete Dowson replied to northcape's topic in FSUIPC Support Pete Dowson Modules
Sorry, that is really really old and totally unsupported. I'm not surprised it crashes as I don't think it understands many new BGL formats. The current supported version is 4.41. Please ALWAYS check the Announcements here before reporting a problem, in case you are simply years out of date, as in this case. Thanks. Regards Pete -
There's no "trial mode" for the user facilities. You don't need to find them. The FSUIPC4 installer will do so if your FSX is installed correctly. Regards Pete
-
Increase rotation speed on Heading instrument
Pete Dowson replied to SE-LSU's topic in FSUIPC Support Pete Dowson Modules
Offset 3110 is only a way of sending FS or FSUIPC controls, those that you can program on buttons or keys in any case. There are offsets for the heading bug and the drift value (though I don't see why you'd possibly want a "fast" gyro drift adjuster -- you should never let it off by much in the first place!). you can of course adjust those how you like, maybe using the FSUIPC offset cyclic inc/dec controls -- but I don't think those operate via 3110 so you'd need to do it another way, like invoking a macro or using a virtual button suitable assigned. For the heading bug, FSUIPC provides two additional controls -- fast inc and fast dec, adjusting in 10 degree changes. Please see the list of added FSUIPC controls in the Advanced User's document. Pete -
FSUIPC offset for clock/timer/OAT/voltage
Pete Dowson replied to SE-LSU's topic in FSUIPC Support Pete Dowson Modules
There's no externally accessible clock/timer gauge controls. They only operate locally to the gauge. You might find it responds to L:var setting, or, just possibly, mouse macros. I'm not sure what you would manipulate with OAT and Voltage displays? Pete -
FSUIPC offset for ADF/RMI
Pete Dowson replied to SE-LSU's topic in FSUIPC Support Pete Dowson Modules
What aircraft, which gauge? I'm not sure what you mean by the rotating scale on any RMI. I don't know of one. Do you mean the ADF compass card? If so, that's offset 0C6C. The normal NAV1 and NAV2 "OBS" compass cards are 0C4E and 0C5E, respectively. Regards Pete -
Okay. Those lines shouldn't really be needed if both PCs are in the same workgroup, but that is more difficult I think if you use Win7's new Homegroup mechanism which is only designed for Networks in which all PCs are using Win7. They are Log files. The one with 0 on the end is the previous one, the one without is the current one. You have Explorer defaulted to hide file types from you where it thinks it knows what they mean. You can change that in the folder options in explorer. The names "workgroup" and "mshome" are presumably different workgroup names? You could change them to be the same on both PCs in Computer Properties. However, that shouldn't be needed now as you have the correct parameters added to the WideClient INI file. You have not said anything yet about it not running since you changed the INI file!. What are the symptoms? The same as before? The WideServer logs you are showing are incomplete -- FSX was not closed first -- but they show nothing being received from the Client. Did you run WideClient? If so, where is its Log, which would show whatever problems it is having? You only show part of the story and don't tell me what is wrong. Have you allowed access through the firewall, or disabled it? Regards Pete
-
FSUIPC Client DLL for .NET - Version 2.0
Pete Dowson replied to Paul Henty's topic in FSUIPC Client DLL for .NET
The A/P is generally part of the radio stack complex installed in light aircraft. The FS one looks like the Bendix King set. Of course A/P is extra expense, so it depends how much you pay for your aircraft, but the FS Bendix King radio stack has the A/P -- it's at the bottom of the stack in the radio window/gauge. Please use the Search facilities to search the offset documentation. It would be much faster for you and save us time too! No one remembers all of the offset values, it just isn't possible. We have to look them up too! Searching for "model" reveals offset 3500, which provides the ATC Model information from the Aircraft.CFG file. There's other ATC-type Identification strings in offsets from 3130 to 3160 and the full Title at 3D00. You'll need to look at those and see what it is you want. Please do make use of the reference information provided. It probably takes me as long to look these things up as would do for you, but i shouldn't need to do it for you. The offset tables in the documentation describe these things. The "type" is an FS indication -- you want the actual memory location in the FS code? Why? If you mean how does FS derive it, I don't know -- but it must be from the Aircraft.cfg file or the AIR file. One or the other. Pete -
FSUIPC Client DLL for .NET - Version 2.0
Pete Dowson replied to Paul Henty's topic in FSUIPC Client DLL for .NET
Please do NOT use the data in FSInterrogate as the reference for offset use. The data module for that is not maintained, and it does not explain things. It is merely a tool, not a reference. Use the offset tables in the documentation provided, where they are much more fully explained and which are maintained. Of course. Because they all have autopilots. Try the glider. If you don't want any of those aircraft to have an autopilot you have to change the AIRCRAFT.CFG file. Regards Pete -
Freeware add-ons don't see FS2004 now
Pete Dowson replied to jparpin's topic in FSUIPC Support Pete Dowson Modules
If this is regarding a 2010 registration for FSUIPC3, didn't you receive my email on the subject? I don't think I've missed anyone. I've sent notices about what is needed to all 2010 FSUIPC3 or WideFS6 registrations so far. Let me seeyes, I sent yours at 22:41 GMT on Sunday 3rd Jan. Maybe it is in your Spam folder? Regards Pete -
They shouldn't do. I believe they only provide inputs when moved -- unless they jitter, but then a reasonable centre zone should prevent that. Anyway, if any do you merely have to uncheck it in the appropriate Options tab. No. Why have the module installed if it is supposed to discard all of its inputs? You can, however, reassign them in FSUIPC. If the rudder and aileron trim built into your console are directly wired to affect the readings from those axes, and not feed any data to the program over the interface, then obviously they cannot be handled inthe PC. There are such facilities in the PFC module, as you will see if you look at the options or documentation* -- I use them on my PFC 737NG cockpit -- but I cannot work miracles. If they are merely local to the unit, you would have to have your unit modified by PFC, if that is possible, if you wanted those controls to feed into FS (or, indeed, X-plane). (* See the section headed "Flight Controls and Trims/Steering Pages") I am sorry, but that answer is rather meaningless. The latest you saw? I've had folks saying that using very old versions simply because thery'd never noticed a later one. And for FS9 or FSX? (they are different versions). Please always give version numbers -- that is what they are for, to identify versions. Regards Pete
-
MakeRwys - NTVDM CPU illegal instruction
Pete Dowson replied to northcape's topic in FSUIPC Support Pete Dowson Modules
Strange. Never had a crash in that in its life, well over 10 years. What version are you trying? It must be some sort of weird BGL structure not seen before. Maybe I could identify it if you could ZIP the "runways.txt" file from the FS folder, send it to me at pertedowson@btconnect.com please. The only other possibility is a memory error. Are you confident your PCs memory is all sound? Strange looking error report. Isn't there something between IP and OP, giving the address? Without an address it is a bit difficult. Regards Pete -
All of it? most won't be influencing anything unless you actually press/change switches or move things. keep controls centred or parked and they do nothing. Or disable the axes in the Quadrants and Flight controls section. Or simply remove the PFC DLL from the modules folder. Their anti-ice may not be one related to anything in FS. You could try programming the switch in FSUIPC instead if you know how to do it. what PFC.DLL version are you using? Sorry, I don't have anything for X-Plane. Regards Pete
-
FSUIPC Client DLL for .NET - Version 2.0
Pete Dowson replied to Paul Henty's topic in FSUIPC Client DLL for .NET
I didn't spot that, but if you don't add 0.5 before the division, won't "floor" still round down, not to the nearest integer as he seems to want? Pete -
FSUIPC Client DLL for .NET - Version 2.0
Pete Dowson replied to Paul Henty's topic in FSUIPC Client DLL for .NET
By using the "floor" of the value divided by 10, you are rounding DOWN. If you want to round to the nearest integer (120.6 as 121) you have to add 0.5 first. I don't know VB or whatever language you are using, but in C it would be dmespdval = (int) ((vor1dmespd.Value + 0.5)/ 10); Regards Pete -
Saitek Panels own driver
Pete Dowson replied to mdenadal's topic in FSUIPC Support Pete Dowson Modules
You can interface to FSUIPC like any other FSUIPC application. You need the FSUIPC SDK. To provide facilities so you can assign functions to the buttons and switches in FSUIPC's option dialogue you can set and clear bits in the virtual buttons offsets, those starting at offset 3340. You have 288 bits at your disposal, enough to indicate the state of 288 switches or buttons (or individual multiway positions). They are seen in the FSUIPC options as joysticks 64 to 72 inclusive, 32 buttons on each. Regards Pete