Jump to content
The simFlight Network Forums

Pete Dowson

  • Content count

  • Joined

  • Last visited

  • Days Won


Pete Dowson last won the day on February 1

Pete Dowson had the most liked content!

Community Reputation

180 Excellent

About Pete Dowson

  • Rank
    Advanced Member
  • Birthday 08/27/1943

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    Near Stoke-on-Trent, UK
  • Interests
    Flight Simming, Steam Railways, Travelling, Real / Craft Ale,, worldwide

Recent Profile Visitors

25,289 profile views
  1. Strange. They should be okay. Which P3D3, the last one, 3.4.something? I don't think I've got any addon-aircraft to use on that. Is there a default where it should work but doesn't? Mostly default aircraft don't support them. Pete
  2. How are you doing it with FSX and P3D? Just via SimConnect? I'm afraid I don't know a way with FS9. If it is possible with SimConnect in FSX then it could probably be hacked with FS9, but I'm afraid I no longer develop for FS9 at all. It is nearly 15 years old, after all! Pete
  3. WideFS support

    You don't need a blank page. Just reduce it to the title bar only if you want to see that it is connected, or you can edit the WideClient.INI faile and change the option for the Window there. You can have it minimised, or hidden as well as visible. Check the options for the Visible= parameter in the WideFS Technical guide (page 10). WideClient only detects buttons on standard Windows-compatible joystick type devices. If Windows detects it in its Game Controller app, then so will WideClient. Press and release button events are then transmitted to FSUIPC in the sim PC. So, where are you looking? You'll see them in the Buttons & Switches tab in FSUIPC Options, and that's where you assign them. Maybe you are thinking your existing assignments to the same device before you moved it would still apply, but that is not the case. The Joystick numbering a different for every PC. This is to enable multiple different functions to be assigned, maybe for Pilot and Co-pilot separately, for instance. it is the main advantage of having devices connected to client PCs. The buttons and switches, yes, but if it has displays then no, those aren't supported directly even in FSUIPC, let alone WideFS. You'd need a separate program, or possibly a Lua plug-in to WideClient. The Lua libraries support any HID device but you need to know a bit about programming or scripts. Pete
  4. It may well be something changed in 4.2 which upsets what PMDG does when collecting data for the files it creates. I know that PMDG have lodged some problem reports with L-M for 4.2 and I've seen some folks hang back with 4.1 whilst awaiting fixes. Either way I'm sure both PMDG and L-M are aware of the problems. Even so it could be worth posting to the PMDG forum. First, just prove to yourself that it isn't FSUIPC, which after all merely calls SimConnect -- one line of code -- to ask it to save the flight. So try it manually: press ; and enter a name for the flight, and see how long it takes before you are flyable again. Pete
  5. Yes. There are new facilities in 4.2 which I can take advantage of, but at present the facility L-M provided only seems to operate if the gauge/switch/knob concerned is actually on screen at the time. I'm seeing if I can work around that, but i think it might need more changes from L-M. Perhaps some folks have the cockpit visible on screen even when using a hardware one, so it will be useful in that case, so I will be implementing it either way. Not sure about timescale at present, but it will be withing weeks, not months. Mouse macros basically try to emulate what the mouse does, but only simple things. I'm not sure what you mean by "scrollup or down" though. The clicking on the left or right should be okay as they will be different "mousable zones". If the scrolling is by using the mousewheel, that might be possible but you need to find the correct mouse parameter to put in the macro manually. I really don't know -- FSUIPC merely calls the function it found with that parameter. It is probably a value derived from the same sort of mouse parameters used in PMDG aircraft "custom controls" and listed in their list of same. And they all appear to be related to Windows programming mouse codes. There might be one for "wheel up" and another for "wheel down" but I think not -- more likely "wheel has moved" with another parameter giving the amount (positive or negative for direction). I currently don't know how to get that part into the function. I think the P3D4 facilities provided are just for mouse button clicking, but i'll know more when I've investigated further. Pete
  6. Carb Heat Command

    Okay. Or you could od as real pilots and have a Check List, of course. ;-) I need one with my 737, otherwise there's always something I've forgotten! Pete
  7. That's good. Well, you probably need FeelThere support rather than FSUIPC support first, as you need to find a way to operate it with keystrokes or other means. If there are keyboard methods of adjusting it, then you can use those on your "knob". Or maybe they are using an FS control to control it -- use FSUIPC "event" logging (Logging tab) to see if any is logged when you operate it with the mouse. The only other possibility is using Local panel Variables ("L:Vars"). You can list all those for the curret panel by using the FSUIPC-assignable list LVar control. There's also a Lua plug-in provided in the Examples which will display them when they change. You can then see exactly what is being used and how, that way. If it is controllable by L:Var then you will be able to create a small FSUIPC macro to deal with it and assign that to act via your knob. Of course, since your knob is an axis it would be far tidier and easier if the panel knob was also an axis typre control (i.e. continuous) rather than a simple increment and decrement action. If there's a support forum covering this aircraft you'd do well to post there. Other users may have looked at this already, or you may even get help from FeelThere. Pete
  8. No, but the question about what the control knob you intend to use remains. i.e "If your "knob" on your USB game controller is recognised in Windows, and therefore flight sim, as a joystick axis, then you can have a continuous adjuster. If it is a digital encoder with, effectively, two button inputs, then it can operate with small increments or decrements to adjust the results." To put it bluntly, I don't know what your knob looks like to the PC, whether it can be seen by FS or FSUIPC. That's the first question now. But your clarification does raise another question too: do FeelThere provide a way to operate that control knob, or is it only a mouse controlled item? Pete
  9. Flight path angle is controlled by a combination of engine (thrust) control and elevator / elavator trim settings, and is a constant feedback process. Unless your aircraft is actually equipped to do this (and personally I don't know any that are -- autopilots control airspeed or descent speed, but normally not directly the FPA) then you'll need a sophisticated program to do it -- via feedback. Is that what you intend to write? This is of course irrespective of what input control mechanism you provide for the pilot. That is easier. If your "knob" on your USB game controller is recognised in Windows, and therefore flight sim, as a joystick axis, then you can have a continuous adjuster. If it is a digital encoder with, effectively, two button inputs, then it can operate with small icrements or descrements to adjust the results. Pete
  10. Flaps - Extend But Don't Retract

    Do you assign to the default FS/P3D flaps control (Axis Flaps Set), or Flaps set, or "direct to FSUIPC Calibration" flaps? I had mine set to the normal FS one, "Axis ...". Also it might be worth just monitoring that 1 byte offset 0xBFC, to see if it changes correctly from 0 to 8 or vice versa. You can Moniroe an offset by entering its details on the right-hand side of the FSUIPC Logging tab and selecting a display method or log below. Pete
  11. Flaps - Extend But Don't Retract

    Okay. I have a Saitek throttle quadrant which I use for testing. I assigned one of the axes to FS control "Axis Flaps Set" and used a direct copy of your calibration settings ... ... snd I have to say they worked perfectly here with the default FSX/FSX-SE 738. When you calibrated, were you doing this with the 737 throttle quadrant showing on screen? I'm not familiar with Sim-Avionics so I don't know even if its 737 has an on-screen cockpit you can see. But you need to do it for the model you are using -- they are not all the same. In particular, for instance, I know the axis values needed for the PMDG 737 flaps are different. And possibly Sim-Avionics has a different method enirely for flap positions? Any chance of you getting a default 737 to test with? I'm not sure if there is one for P3D unless you also have an FSX or FSX-SE installation. I'm also wondering if you might not get more joy from Sim-Avionics support? I use ProSim737 for my cockpit, but my quadrant is part of my original PFC 737 hardware cockpit, with shell, and its flap lever has built-in detentes, calibrated though my own PFC driver (PFCcom64.dll for P3D4). ProSim737 comes with its own 737 model, but no on-screen cockpit display so I can only check by the feedback on the flaps gauge, and of course the "notch" value available in offset 0BFC (one byte, 0-8, 0=up). Pete
  12. Flaps - Extend But Don't Retract

    The only odd thing I see there is the final setting, for flaps fully extended. Apart from the range allowed being verey small (16383 to 16384) the maximum calibrated value is 16380. However, apart from the fact that this should work in reverse, it looks okay. I'll try your exact settings here. Pete
  13. Cannot register FSUICP4...

    I understand that. That is why I said "I don't know what is going on with your system" -- because I don't. I can only tell you what FSUIPC can and cannot do. When strange things are happening on a users system I simply do not have enough information about everything else on that system to explain strange happenings. Well, it is a complicated sequence which should not be necessary and which I don't understand. Perhaps you understand something different from that word as you seem to be taking it as an insult! :-( Where on Earth is this coming from? Where did I ever say you were lying??? NO ONE IS BERATING YOU OR YOUR SYSTEM!! Please do read my replies a little more carefully, as you plainly are reading things which are just not there! I try my best to help, but I do not understand everything that may happen on everyone's systems. All I can say it what my own program does. Pete
  14. Carb Heat Command

    Thanks for the links. This, from one of them, seems to contradict the idea that it is a "bug", and it is from a contibutor whose opinions I value: Actually, it is not and never has been a 'bug' per se. Even fuel injected engines require an air source, and unless you have some way to heat the air intake, you can and will have ice formation. I'm not sure why you'd want the switch operated by gear up, but if you'd programmed this in the FSUIPC axis assignments using the range part on the right, why not simply reserve a small part of the area representing the movement towards "gear up" as an other zone which is assigned to the so-called Carb Heat switch? (i.e. have three zones instead of one or two). The control assigned to the 'H' key by default is actually known internally in FSX and P3D as "Anti ice toggle" (applicable to jets as well as props, like "Pitot heat toggle", which is Shift+H) and that's what you need to assign to. As it's a toggle you'd need that range applicable to both up and down passage through it. Pete
  15. Carb Heat Command

    I’m not at home at present but will send methods when I return, but meanwhile can you tell me what “the P3D fault” is? You seem to be assuming it is general knowledge and is not going to be corrected. It would be helpful if you could find where you read this advice, as it seems very strange to me. Pete