spokes2112

Is it registered for full use? Did you check previous registrations on install? Without a valid registration that's all you'll get. http://secure.simmarket.com/pete-dowson-fsuipc4.phtml

Try copying the .key files from your FSX install over to P3D/modules & reinstall, selecting the same as before.

When you uninstalled P3D did you inadvertently remove the FSUIPC4.key file? If you have a backup, copy it over to P3D/modules then reinstall a full installer version of FSUIPC. Then when the popup window shows for registration select "Check Current Registration". If you do not have a backup of the .key file check you account at, or contact SimMarket support for a replacement. Then reinstall as described above.

Pete is on vacation for a while, hopefully this will help. Why it works without FSUIPC is confusing, normally "flooding" of panel describes what's happening & Pete provided a fix starting from v4.93. Maybe that fix is keeping the AB doors from working correctly. Look for "TimeForSelect=" in your fsuipc.ini file (defaults to 2) also refer to this setting on pg.8 "FSUIPC 4 for Advanced Users". Maybe try a setting of zero to disable the function.

Yes a typo. OOOPS! Not enough coffee yet. UTC-5 :oops: Roman

Hi Pete, 4.945 tested out just fine... Thank You! Roman

Pete, Sounds great! Will keep an eye out for the next release. Thank You Very Much! Roman

Pete, Yes. Nothing else really jumps out as being needed. ( a waste of 6 bits :-( ) Just checked (FSUIPC Logging) & the 32FC increment doesn't work on my side (4.949p) when using the reload user aircraft control (C66512) with the same .air file & aircraft name. We are checking for aircraft.cfg changes while in flight and being logged which need an aircraft reload to take effect. No need for flight loading (3F02) as our logging cannot start until ready for flight, if the flight fails for any reason it must be restarted and re-logged. Roman

With airport names it is defaulted off when FS starts, it's state does not get saved in a flight file or the sim config. For both, when the program starts logging a flight we would get the state of the bits/byte in FSUIPC, then store them for a comparison. As the flight goes on, continue to query the FSUIPC offset bits/byte to see if they changed compared to our saved bits/byte. If changed, a warning will be logged. Our saved bits/byte would then be updated to the new state providing additional comparison queries throughout the logged flight. The program is a validation / cheat logger, an output example is here - http://fs-duenna.com/flights/logs/VGLnbVak2KrmIBdnIPHC4KLS9M.txt Thanks, Roman

Hi Pete, Instead of using the "state" would a control "listener", similar to lua's event.control, work in your .dll? We need the returns at an offset since the programmer is using C# w/ Paul Henty's client .dll and using lua on the end-users machine is not feasible. Something like, using lua as an example (added 1 more needed control) - function TogBit(controlnum, param) if controlnum == 0x104A4 then ipc.togglebitsUB("assigned byte", 0x1) elseif controlnum == 0x103D0 then ipc.togglebitsUB("assigned byte", 0x2) end end event.control(0x104A4, "TogBit") event.control(0x103D0, "TogBit") If this will work and you are willing, there will be no huge hurry in implementing into your next release. If done, could you provide the assigned offset via PM? (Secretive) P.S. It looks like you and Ray had an excellent time at Brooklands Museum! :mrgreen: with envy.. lol ! Thanks in advanced, Roman

Just adding info & it may not be related at all, maybe it will help. Our Around the World Race Team has experienced the R6025 error many times. When it occurred it also caused a few, not all, of other multiplayers flight sim to crash fatally with the same pop-up error at the very same time. Therefore it was transferred over the MP network. We use FSHost & FSHost Client as our MP environment. (Enables FS9 and above to be in the same MP session) 90% of the time the faulting module (fs9 & fsx) was visualfx.dll. The error would cross sim versions in MP. With the same Exception code: 0xc0000005 In most cases the fault occurred when an aircraft either entered or left a certain players TCAS range, a user changed aircraft or, one had just joined or left the MP session - a change of TCAS information. One particular aircraft, the Mario Noriega Avanti V3, caused more problems than others, although not singled out as the primary cause. I am getting a private poll started over at Avsim with our teammates to hopefully get a bit more of information. These errors started ~ 5 years ago, much of the above was from memory. Primarily going to ask the teammates if one had the error, was WideFS running. ( Not singling out WideFS as the cause )

Hi Pete, Hope all is well with you. Just updated to 4.949p from "c" to get the latest docs to search but not found. What i'm looking for & hoping you can provide is a read offset to show the state (on / off) of control C66724 - "Toggle Airport Names". This is for a flight validation program. According to the SDK this command is shared cockpit available so hopefully a variable is floating around? Just did a quick test while writing this and confirmed FSX starts up with names defaulted off so maybe a "flip/flop" can be had by monitoring the control? If names = on then C66724 end Thanks in advanced, Roman

A little over my head but maybe try... (psuedo) I would try AP_PANEL_ALTITUDE_SET - 66105 Disp = Pre calced/written value on the display If Disp <> FS_AP_Alt value then ipc.control(66105, Disp) End

It probably can, through a workaround. All keyboards have a fixed set of standard keys, any extra have to be handled through the keyboard software as macros. On my MS Sidewinder X4 it has 3 selectable banks of 6 extra buttons for a total of 18 extras that are also program focused. On bank 2 & 3 of my setup are all macros that I use through FSUIPC for gauge/lua programming debugging. Once unused FSX key macros were made on the keyboard, if I remember correctly I had to hand edit the FSUIPC4.ini as the FSUIPC trapping of the keyboard was at a lower level than the macro provided by the keyboard. (The workaround) Advise to go to the manufacturer's site and get a manual or check the specs on how the extra buttons work.

Thanks in advanced! :D

Reinhard, Very interested! Hope you're willing to share. LUA rocks! Roman

This isn't the correct forum for this - at all, but i will try to help a little bit. 1. Standard.xml is the settings for keyboard/joysticks assignments and calibration 2. the xml has syntax errors. If at all familiar with XML these "may" be easily fixed. 3. Dragging the file over to an open Internet Explorer window will give line #s of the first error & a possible reason. 4. If p3d ( do not own ) has a similar installation routine as FSX, a backup of Standard.xml should be in root P3D folder - copy and paste it to C:\Users\Peter\AppData\Roaming\Lockheed Martin\Prepar3D v3\Controls\ overwriting the bad one.* NOTE all you assignments will be lost. Some links with a similar error, different files, but still xml. http://www.prepar3d.com/forum/viewtopic.php?t=115414 http://www.prepar3d.com/forum/viewtopic.php?t=113804 It's totally fixable, if unable to do so yourself, start a topic on the P3D forums and either post or attach you standard.xml, someone there will help. Good luck.

Not sure on this but you could try hand editing the FSUIPC4.ini. 1. Find the axis supplied for the 1st tiller in the FSUIPC4.ini [Axes] section 2. Copy it and add another entry in the [Axes] section changing the Joy number to the new tiller. Ex. crude & is not relative to anything regarding a tiller [Axes] 4=0S,1,D,7,8,0,0 <-- If this is the first tiller on Joy #0 copy it 5=0S,1,D,7,8,0,0 <-- And paste it changing the entry & Joy number to match accordingly to the actual new tiller joy # Worth a try.

Excellent! :razz: There will now be a "FSUIPC4.key" file in the FSX:SE\Modules folder. Copy that and save it somewhere. It will save troubles on a new install etc.. check existing registration = I have a FSUIPC4.key, please check it. enter new registration = I have do not have a FSUIPC4.key, please create one & check it.

Iain, I hope this helps, I haven't had to do anything since installing in 2011. I believe the key is created only after the pertinent info is entered, then one could use "check existing registration". If there is no key you should use something like... "Enter registration information" or similar when the dialog comes up. Sign into simMarket - click Your Account / Purchase History - click the FSUIPC purchase. All the registration information needed is now given for entry. You must rerun the FSUIPC installation.exe in order to enter this information. Once this is done a key is then created for subsequent updates etc...

Iain, Was the "FSUIPC4.key" file in the FSX:SE\Modules folder? If not, locate it from a from a possible saved email, current FSX:boxed installation, backup files -or- get a replacement .key from simMarket via customer account. Once that is done make sure the .key file is in the FSX:SE\Modules folder & retry the FSUIPC4 installation.

Like this I would assume - Standard keyboard assignments vs. FSUIPC assignments <Entry> <Key>Caps_Lock</Key> <-- Standard FSX / P3D keyboard assignment <Down>MP_VOICE_CAPTURE_START</Down> <---- ON KEY DOWN - MP VOICE CAPTURE START - FSUIPC Control = 66684 <Up>MP_VOICE_CAPTURE_STOP</Up> <---- ON KEY UP - MP VOICE CAPTURE STOP - FSUIPC Control = 66685 </Entry> <Entry> <Key>SHIFT+Caps_Lock</Key> <-- Standard FSX / P3D keyboard assignment <Down>MP_BROADCAST_VOICE_CAPTURE_START</Down> <---- ON KEY DOWN - MP BROADCAST VOICE CAPTURE START - FSUIPC Control = 66735 <Up>MP_BROADCAST_VOICE_CAPTURE_STOP</Up> <---- ON KEY UP - MP BROADCAST VOICE CAPTURE STOP - FSUIPC Control = 66736 </Entry>

I believe these are worded differently in the UI versus the actual commands. If this is for MP usage then yes FSUIPC has these commands. MP BROADCAST VOICE CAPTURE START 66735 MP BROADCAST VOICE CAPTURE STOP 66736 MP VOICE CAPTURE START 66684 MP VOICE CAPTURE STOP 66685

The easiest way to do this would be to create a shortcut to MakeRwys.exe then in the shortcut properties | Shortcut Tab | Target field, modify it so it includes the switches. ex Target = "<path>" switch 1 switch 2 switch 3 etc... Then use the shortcut to run MakeRwys

John, Ran into this the other day. Start FS & do the clicking OK to get into the sim. Load a flight plan then save the flight with default flight being checked. That should take care of it the next time FS is started. What I believe happens is that the waypoint counts do not match in the .flt file in the [ATC_Aircraft.0] , [ATC_ActiveFlightPlan.0] & [GPS_Engine] or the path to the to the .pln file is no longer valid within the [GPS_Engine] section.