Pete Dowson

You mean something different happens when that aircraft just happens to be the one which is loaded? If so, what is different? When you say you have a problem, what IS the actual problem? Can you describe it please. Pete

Oh, good. Well done. I'll need to work out why it is doing what it is doing with that device. The registry entries for it would be very handy so I can determine the best way to eliminate it without affecting other devices. Does this keypad produce button presses or axis inputs for you, or is it really a keyboard? If the latter that it appears to be mis-classified by its IUdentifiers, as I don't scan for keyboards. Regards Pete

Oh, one thing you could do for me. Can you run RegEdit (from the Start button) and go to HKCU\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0000&PID_0111\ and see if there is a "Calibration" section in there and if so what it contains in the way of keys and data fields? Or even simpler, Export that key to a file and paste its contents here. Dodn't double click the exported file, rename it as a text file first. Thanks, Pete

I think one of those is causing the hang when interrogated. Do that logging as in my last post, please, and then perhaps try disconnecting all those and see if that allows FSX to run okay. If so, connect them back one at a time, each time going into fSUIPC options to see if that works or hangs. Pete

How does this relate to a thread title of "No", and identically posted twice? (I've deleted the other). Axis detection in that tab has nothing whatsoever to do with any specific aircraft, it only shows whatever axes are operating on joystick devices connected to your PC and working. Pete

There is logging of the device scanning actions already built in. Please re-instate your KEY file so you're registered again, then edit the INI file as follows: In the [General] section, add: Debug=Please LogExtras=x200000 Then run FSX again and show me the FSUIPC4.LOG. Pete

Okay. Good. Then its looking like either a sound device or a game device (joystick or something). What do you have in these areas? Okay. If it does it in Windowed mode then it is probably related to the same hardware things -- in that case it must be joystick devices, because I suspect I probably rescan those when you enter the options even if you aren't registered. (I'll check that, because if I do I should change that). I'm looking now for ways of narrowing it down. Meanwhile, can you tell me what is connected? What devices does it show in Windows' Game Controllers, for example? Pete

Okay. So it looks to be hardware related. But if you have made changes to FSUIPC settings in the past, could you paste in your normal INI file file i can see if there's anything there to eliminate? I'll work out a way to narrow it down a bit more. That's ALWAYS a function of the video driver. You'll need to make sure you are using a good one. The default installed by Windows is no good. You need the sapecific one for your make of video card from AMD or nVidia asite, or try Guru3D.com, they've got loads. The dialogue mode is bog-standard Windows. You can prtove it is a driver problem by changing FSX into Windowed mode before calling up the menu. it will then work okay. There's no difference in FSX/FSUIPC for dialogues in the different modes, except that the FSX screen itslf does blank for all dialogues, as you will know. Pete

I had a bit of a job getting it accceptable, I must admit. I first adjusted the view zooms so that what could be seen matched what you should see based on the angle of vision, from one side of the screen to the other. I did that by using top-down view to start with to get the aircraft the right distance from a building (e.g terminal) so that the angle from both sides of the building to the aircraft's nose was the same as my seated viewing angle onto the complete screen width. Then, in normal forward view adjusted the zoom till the building just filled the width on screen. Repeated that for each of my EZCA views (forward, 60 degree left/right, and 120 degree left/right). The distortion at the sides was then very noticeable on uprights when close up (like when taxiing or parking at airports). So I minimised that to just about acceptable by pointing the views slightly upwards and changing the projected image to a rhombus shape a but wider at the top than the bottom (or is it vice vera? I get confused). I also needed to get the horizon in the right place from my cockpit view (a little below eye level). All these things interact, of course so it took a whiile! The screen is actually a 4:3 aspect screen and I'm projecting 16:9 (1920x1080p), so there's room to move the whole picture up and down a bit. Regards Pete

I moved your support question to the Support Forum, so it can be dealt with. You posted by mistake to the FAQ subforum! There's only one correct way for any user, registered or not. just run the installer. Don't uninstall anything. There is an Installation guide in the ZIP, that tells you what to do. It isn't very long! Running the installer is only a matter of executing the Installer EXE provided, preferably "as administrator", as it tells you. Regards Pete

It takes quite a long time for FSX to sort itself out first time on a completely fresh system. Please check the Modules folder, see if there's an FSUIPC4.LOG file. If so, show it to me. Regards Pete

Sorry, but it simply cannot be anything to do with FSUIPC because it really does nothing unless you ask it to, and will simply not be aware of you using those options unless you have programmed it to intercept them and do something. Furthermore the only difference between 4.90 and "the last version" is that there is no Digital Signature and therefore no Digital Signature check. This was merely a check during loading which is now bypassed. Regards Pete

For most folks persistence eventually paid off. You only need to get it running once and it then stays okay (till the next update, anyway). Pete

Strange requirement. The aircraft flight control ranges are designed by the aircraft designer to allow the aircraft to be flown correctly. Limiting the range which can be set by the pilot seems to indicate that the aircraft designer got it all wrong. Have you looked into correcting that, by perhaps changing the control effectiveness coefficients in the aircraft you have problems with? e.g. elevator_effectiveness = 1.0 aileron_effectiveness = 1.0 rudder_effectiveness = 1.0 elevator_trim_effectiveness = 1.0 aileron_trim_effectiveness = 1.0 rudder_trim_effectiveness = 1.0 Or even altering the limits, like these: elevator_up_limit = 22.5 //Degrees elevator_down_limit = 19.5 //Degrees If it must be with the inputs rather than the results, then one way you could do that is to first calibrate normally, in FSUIPC, then edit the values stored in the calibration lines in the INI file. For example, my throttle calibrates like this: Throttle1=-16355,-2080,1152,16340 and changing this to Throttle1=-32710,-2080,1152,32680 limits its effect, in both directions,to half what it was, simply because FSUIPC is fooled into believing that its imput range far exceeds the needed one. If you are also assigning in FSUIPC, not just calibrating, then an alternative which I've never tried but which should work, is to calibrate as normal, but then edit the axis assignment line in the INI to scale down the input. Axis scaling is covered in the advanced users guide. If you wanted to half the effectiveness you'd scale by adding ,*0.5 to the end of the axis assignment line. [LATER] I see Andy got in first with one of my suggestions! Thanks Andy! Regards Pete

Okay. I don't know if it will help, and please don't let it put you off, but here's a Lua plug-in I did for a Cockpitsonic 737 overhead Electric Metering Panel (EMP). It's just a test program, displaying switch changes on a Lua window and displaying test patterms on the metering display. Sorry about the lack of comments (I tend to find code desribes itself better than my inane comments would), but at least it does use all the things you might need -- opening the device, reading, interpreting and writing. You may also find the HidScanner program useful -- in the Lua thread within the Download Links subforum. dev, rd, wrf, wr, init = com.openhid("Cockpitsonic", "EMP", 0) if dev == 0 then ipc.log("Could not open HID") ipc.exit() end displaymax = 20 str2nums = string.char(0xff,0x02,0xd7,0x30,0xd0,0x45,0xc8,0x08,0xd3,0x00,0xc0, 0x7f,0x82,0x57,0xb0,0x50,0xc5,0x48,0x88,0x53,0x80,0x40, 0xff,0x02,0xd7,0x30,0xd0,0x45,0xc8,0x08,0xd3,0x00,0xc0) str3nums = string.char(0xfe,0x11,0xba,0x85,0x82,0x2b,0x42,0x41,0x9a,0x01,0x02, 0xff,0x10,0xbb,0x84,0x83,0x2a,0x43,0x40,0x9b,0x00,0x03, 0xfe,0x11,0xba,0x85,0x82,0x2b,0x42,0x41,0x9a,0x01,0x02) -- clear down the display ipc.lineDisplay("", 0) ipc.log("rd = " .. rd .. " wrf = " .. wrf .. " wr = " .. wr) com.write(dev, string.char(1,0), 2) com.write(dev, string.char(2,0xff,0xff,0xff,0xff,0xff,0xff), wr) com.write(dev, string.char(3,0xff,0xff,0xff,0xff,0xff,0xff), wr) n2 = 1 n3 = 2 brite = 240 doinit = init and (string.byte(init,1) ~= 0) if doinit then prev1 = 255 - string.byte(init,2) prev2 = 255 - string.byte(init,3) prev3 = 255 - string.byte(init,4) else prev1 = 0xff prev2 = 0xff prev3 = 0xff end while 1 do ipc.sleep(500) while doinit or (com.test(dev) ~= 0) do if doinit then str = init doinit = false else str = com.read(dev,rd,rd) end -- decode val0 = string.byte(str,1) if (val0 == 1) then val1 = string.byte(str,2) val1ch = logic.Xor(val1, prev1) prev1 = val1 if val1ch ~= 0 then if logic.And(val1ch, 1) ~= 0 then if logic.And(val1, 1) ~= 0 then ipc.lineDisplay("Battery Master On", -displaymax) else ipc.lineDisplay("Battery Master Off", -displaymax) end end if logic.And(val1ch, 2) ~= 0 then if logic.And(val1, 2) ~= 0 then ipc.lineDisplay("Cab/Util On", -displaymax) else ipc.lineDisplay("Cab/Util Off", -displaymax) end end if logic.And(val1ch, 8) ~= 0 then if logic.And(val1, 8) ~= 0 then ipc.lineDisplay("Maint released", -displaymax) else ipc.lineDisplay("Maint pressed", -displaymax) end end end val2 = string.byte(str,3) val2ch = logic.Xor(val2, prev2) prev2 = val2 if val2ch ~= 0 then if logic.And(val2, 1) == 0 then ipc.lineDisplay("AC Select = Stby Pwr", -displaymax) elseif logic.And(val2, 2) == 0 then ipc.lineDisplay("AC Select = Grd Pwr", -displaymax) elseif logic.And(val2, 4) == 0 then ipc.lineDisplay("AC Select = Gen1", -displaymax) elseif logic.And(val2, 8) == 0 then ipc.lineDisplay("AC Select = APU Gen", -displaymax) elseif logic.And(val2, 16) == 0 then ipc.lineDisplay("AC Select = ???", -displaymax) elseif logic.And(val2, 32) == 0 then ipc.lineDisplay("AC Select = Test", -displaymax) elseif logic.And(val2, 64) == 0 then ipc.lineDisplay("AC Select = Inv", -displaymax) elseif logic.And(val2, 128) == 0 then ipc.lineDisplay("AC Select = Gen2", -displaymax) end end val3 = string.byte(str,4) val3ch = logic.Xor(val3, prev3) prev3 = val3 if val3ch ~= 0 then if logic.And(val3, 1) == 0 then ipc.lineDisplay("DC Select = Stby Pwr", -displaymax) elseif logic.And(val3, 2) == 0 then ipc.lineDisplay("DC Select = Bat Bus", -displaymax) elseif logic.And(val3, 4) == 0 then ipc.lineDisplay("DC Select = Bat", -displaymax) elseif logic.And(val3, 8) == 0 then ipc.lineDisplay("DC Select = Aux Bat", -displaymax) elseif logic.And(val3, 16) == 0 then ipc.lineDisplay("DC Select = Test", -displaymax) elseif logic.And(val3, 32) == 0 then ipc.lineDisplay("DC Select = TR3", -displaymax) elseif logic.And(val3, 64) == 0 then ipc.lineDisplay("DC Select = TR2", -displaymax) elseif logic.And(val3, 128) == 0 then ipc.lineDisplay("DC Select = TR1", -displaymax) end end end end com.write(dev, string.char(1,brite), wr) brite = brite - 16 if brite < 0 then brite = 240 end com.write(dev, string.char(3) .. string.sub(str2nums, n2, n2+5), wr) n2 = n2 + 1 if n2 > 22 then n2 = 1 end com.write(dev, string.char(2) .. string.sub(str3nums, n3, n3+5), wr) n3 = n3 + 1 if n3 > 22 then n3 = 1 end end [/CODE] Good luck! Pete

If the problem is indeed a screwed up SimConnect installation, I suspect that may be the only way. As I said, that's what I had to do. I did try all sorts of things first, to no avail. I think on Windows XP I could have sorted it out manually by Registry editing, but on Windows 7 it was way too complicated. I desperately wanted to be able to do it, because if I could have done it manually I could have written a program to do it too, and offered that for downloading for others in similar predicaments! I assume you referred to that FAQ thread and tried everythnig suggested there, not just by me but by others too? Regards Pete

If you run a Windows emulation on the Mac I suppose it might work. There's is nothing really non-standard about anything WideClient does, but it would obviously depend on the fidelity of the emulation. However, as far as I was aware the later versions of Squawkbox don't use FSUIPC at all, so I don't see the point. WideFS only provides a Networked FSUIPC interface after all -- unless you are only thinking of the facility to send PTT and PVT calls via the SB Roger Wilco standard messaging system -- but that also only applies to Windows in any case. Regards Pete

Sorry, what sort of explanation? I don't see what I could say which would help in any way. What would you like it to say? You said in your original posting: But this was not the case it seemed. You had a LAN firewall set up in your Router!? I've not heard of such before -- normally the router firewall facilities are designed to control traffic from the WAN, the Ethernet, not within your own local Network. Additionally, the symptoms shown in the Logs you supplied indicated that Server Broadcasts were not seen by the Client. If you had added the ServerIPAddr and Protocol parameters to the Client INI file, as suggested, then the fact that the traffic must have been blocked somewhere would have come to light. Anyway, I'm glad you sorted out. I would certainly never have thought of a router blockage. ;-) Pete Regards Pete

This is actually a mistake. It tends to make a mess of SimConnect, which doesn't get properly uninstalled and therefore doesn't get re-installed correctly. I tested this to see what was going on, and the way the Registry stuff handles side-by-side libraries like SimConnect turned out to be a nightmare. The only way i got things working again was to reinstall Windows from scratch, then FSX etc. You might just be able to get around that if you have a Windows restore point dating back to a time before you started uninstalling. If you didn't run FSX between each stage then that could be a further reason for problems. Okay. This is actually better, and now more like the standard SimConnect glitch, as described at length in the FAQ subforum thread "FSX fails to run after FSUIPC4 first installed". Please check that. If there is a Windows error log entry for that crash, I'd be interested in what it contains. But going by the previous reports it doesn't help much. The crash occurs before FSUIPC is actually running. The only other way of getting possibly useful information is with a SimConnect log -- there's a FAQ thread on how to get one of those too. But, again, this usually shows FSX crashing just whilst SimConnect is processing the entries in the DLL.XML telling it what to load. Regards Pete

Before you re-installed, did you uninstall at all? If so i think that wrecks Simconnect quite badly. When you reinstalled, did you run FSX before each stage -- i.e. after the base install, then after SP1, then after SP2, before adding anything else? I think you need to. Are you still trying to use the FSUIPC loader? If so don't. I don't really think it actually helps. It was only ever a "just in case...". To remove it, delete it from the Modules folder and re-run the FSUIPC4 Installer. Are there any other add-ons installed at all? Pete

In Documents/Flight Simulator X Files, alongside your saved flights. you DO have some flights, don't you? Pete

You shouldn't really need to use the Loader. its really only for getting around timing clashes with other Add-Ons. but I've not so far learned of any real benefits even then. It's a sort of experiment. The crash data shows it deep inside FSX itself, so simconnect is the likely problem. There are only two things I know of causing crashes at tha stage: 1. Logbook.bin corruption. Try renaming it (I think that's in the same folder as your FSX.CFG). 2. Probably more likely, a bad WX file being loaded as default. Try, moving all of the .WX files out of the light Simulator X folder in your documents. The former should affect FSX whether FSUIPC is loaded or not. The latter tends to be more obvious when FSUIPC is loaded becausde it is constantly asking SimConnect for weather data. Pete

By "new DLL" I assume you mean the FSUIPC_Loader? i'm sure this is a Simconnect problem, but do you have any actaul crash details? Check the Windows ogs in the Event Viewer. Without details its impossible to know what is going on, and the problems are really so rare. That's really rather drastic and tends, mostly, to get SimConnect into a real mess, especially on Win Vista, Win7 or Win8. I found I needed to reinstall Winsows as well because I tried that once to see what the problem might be. That does seem to show that it's hanging inside SimConnect itself. Regards Pete