• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Guido

  • Rank
  1. Hi, I hopped that Fscene would also enhance the Alps area. The default and current version of Fscene present the peaks of the Alps with desert like brawn textures and green trees. Unfortunately this does not look very nice at all and especially with my photo scenery Switzerland CHPROX. I wonder if the textures used for mountains could be replaced/changed with a gray tone one (within the landclass limitations of P3D/FSX)? Thanks for feedback and help to change the top of the Alps texture with a more realistic gray. Rgds Guido
  2. Hi Thomas, Thanks for the help. As proposed I deleted the old assignment and renamed the new created IDs with the former joy letters. This did the job. Rgds Guido
  3. Hi, When transiting from FSUIPC version 4959 to 4969 I got a missing joystick issue. With this behavior my assignments are “gone” and second some joysticks are now twice listed with new IDs. I don’t understand what is creating the <<MISSING JOYSTICK>> message (except for F=737YOKE) and why the detection after. Appreciate any help to fix the issue. Guido Attached: File compare and log file FSUIPC4.log missingjoystick.pdf
  4. Hi, I got the W10 anniversary update by surprise. And the surprise swapped the GoFlight assignments of the two GF186 (NAV<->COM) and the two GF-RP48 units. Meanwhile I understand the basics about the USB mechanism. But I don’t understand how and where the unit numbers displayed in FSUIPC (Joy# 174, 175,…) are linked with the USB HW Port/Hub number and/or USB addresses? Registry? As I am using parallel to the W10 P3D also a W7 FSX system I really would like to keep the same assignment for both sims. How can I influence W10 to change back to the former unit order (174 <-> 175) assignments? Many thanks for help
  5. Thanks for feedback and hints. And I am sorry for the miniscule script. To answer first the question: Yes, I did read the A2A forum topic. Triggered by Paul’s comment I did the following steps which solved the problem - Replacing the RealityXP(RXPGNS.ini) with the original empty file - Deleting the lately added two A2A assignments (via input configurator) - Starting FSX. Now FSUIPC and FSX accepted key commands - Shut down FSX - Entering the same 2 assignments again using the input configurator of A2A - Renaming the RealityXP ini files to get the former status - Restarting FSX and things work Difficult to say what it was but at least I could assign ruder trim to the buttons :) Again thanks for the help. Guido
  6. Hi After installing A2A's C182 and assigning via FSUIPC some buttons and keys to GoFlight HW some days later I could not add new key codes to buttons. Even rolling back to the older FSUIPC.ini file version does not help. All buttons are inactive or blanked (attachment) independent if specific is tagged or not. Also changing to other airplanes has no effect. Compared to the FSX.cfg version without C182 the differences are the following lines: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.rbcratezqkteollihqcneubobuntnccbtbnelcnc=1 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\A2A_Accusim.DLL.ihanbthaiabztoluzunklboizqttkazwciqrlbhh=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_C182\panel\C182.DLL.hekhcekicobbeznctihozwrunzwtilhoiqqazlho=2 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\A2A_C182\panel\C182_Illumination.DLL.aiqzikzhoanearrwbqerwwarlkanihahzitwkilw=2 C:\Program Files (x86)\GoFlight\GFDevFSX.exe.uzbqceeqtnqokbittcwwtlzrzahhanzkkkqqnhuw=1 I wonder what could block FSUIPC to accept new key/button inputs. Many thanks for the help. Rgds Guido FSUIPCBS.pdf
  7. Hi Pete Thank you for the feedback. I will check and inform the supplier of the add-on. Rgds Guido
  8. Hi "Every" time updating FSUIPC I run in to the issue to edit the dll.xml. As the FSUIPC update installs always at the end but before <simbase.document> <rwyadv> is not behind FSUIPC a). In this case I get a R6025 error when ending fsx. If I move FSUIPC before rwyadv the problem is solved b ). It is easy to fix when you know what to do but the reason is not clear to me. Thanks for your feedback. File: dll.xml a) </Launch.Addon> <Launch.Addon> <Name>RwyAdv</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Addon Modules\RwyAdv.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </SimBase.Document> b ) </Launch.Addon> <Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> <Launch.Addon> <Name>RwyAdv</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>Addon Modules\RwyAdv.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </SimBase.Document>
  9. Thanks for the feedback and the coming fix. I wonder if I understand the DX9/DX10 comment right. DX10: The scheduler uses only flights of aircrafts which are compatible with DX10 and DX9 mode.
  10. Hi Burkhard After the update to 5.4b I checked if the A380 from Singapore is now at Zurich Airport (LSZH). I did set the time to 9 and then to 10. Unfortunately I could not find it (FSX AI at 30). But I did spot between 5 and 6 Thomas Cook planes. Looks like they have a new home base. I wonder if I set something wrong ? On the other hand it looks like that the update installs the 2012 schedule automatically. Further I spotted some black Bombardiers at several parking positions. One last remark: DX10 is for me not useful as most of my scenery add-ons do not support it and no update is in sight. Therefore I decided to go back to DX9 as the advantage is marginal but the problems big. Thanks for your help and I wonder what I need to change for a better AI traffic representation. Best regards Guido
  11. Hi The problem is solved. I deleted FSUIPC.ini, rebuild and copy-past it. Now it works as expected. Thanks Guido
  12. Hi I am new to LUA and below is my first simple program. It should test several 737NGX annunciation flags to control the LEDs of the second RP48. A simple RP48 LED flash test program did work. But I fight with the offsets. I did set the EnableDataBroadcast=1 and tested the Re-simconnect trick but nothing flashs. I am getting out of ideas what to do next. I appreciate your support very much. My LUA script: --Begin model = GFRP48 -- GoFlight model number unit = 1 -- Sets the Variable Device "unit" to GFRP48 174: 0; 175: 1? MCLED = 0 -- Init LED Numbers APLED = 1 ATLED = 2 FMCLED = 3 -- Function Master Cautionto light on/off function MasterCaution(offset,value) if value ~= 0 then gfd.SetLight(model,unit,MCLED) -- Turn RP48 2 MCLED ON else gfd.ClearLight(model,unit,MCLED) -- Turn RP48 2 MCLED OFF end end -- Function AP Cautionto light on/off function APCaution(offset,value) if value ~= 0 then gfd.SetLight(model,unit,APLED) -- Turn RP48 2 APLED ON else gfd.ClearLight(model,unit,APLED) -- Turn RP48 2 APLED OFF end end -- Function AT Cautionto light on/off function ATCaution(offset,value) if value ~= 0 then gfd.SetLight(model,unit,ATLED) -- Turn RP48 3 ATLED ON else gfd.ClearLight(model,unit,ATLED) -- Turn RP48 3 ATLED OFF end end -- Function FMC Cautionto light on/off function FMCCaution(offset,value) if value ~= 0 then gfd.SetLight(model,unit,FMCLED) -- Turn RP48 2 FMCLED ON else gfd.ClearLight(model,unit,FMCLED) -- Turn RP48 2 FMCLED OFF end end -- Main program gfd.SetBright(model, unit, 15) -- Sets the Brightness of Unit#1 on the GFP8 to 15 (full). event.offset(0x6506, "UW","MasterCaution") event.offset(0x6550, "UW","APCaution") event.offset(0x6552, "UW","ATCaution") event.offset(0x6554, "UW","FMCCaution") --END Thank you for help and bregards Guido
  13. Hi Pete Sorry I did not catch it the first time. The advanced users guide was not part ot the initial down load package and I mixed it with the users & programmers guide. Again sorry about that. Now things are clear. Rgds Guido
  14. Hi Pete I am one of the 3D cockpit users and therefore I think mouse macros will not work. Until now I did not study LUA and I guess I would need a variable list. Do you know a good link to learn and start with LUA? For Wilco’s A320 is an interface available called exporter to control A320 specific commands. I am using it already to manage the altitude information. I read through FSUIPC the commanded altitude in FSX (coming from my MCP-Pro) and write it through the exporter to the A320s virtual FCU. What I want to do now is to detect some MCP-Pro button event via FSUIPC “inside” FSX (I am not using the MCP-Pro development kit) and then write the event into the exporter interface. The trouble is that I do not know how to detect the MCP-Pro button event (#158/11,12,13) via FSUIPC and FSX. The rest is no problem as I did test it with a joystick button event (offsets 32FF, 2910 and joystick #0/button 2). I hope there is a way to detect the event via FSUIPC. I am not sure what I can do with offset 66C0 as it is for general use. Can I use it to detect “joystick” number 158 button 11? I guess not. I am sorry for my not so usual “miss use” of FSUIPC. I am also happy if another easier method exist to do the same. Many thanks for your help. Rgds Guido
  15. Hi Pete I want to emulate the Airbus FCU’s push/pull button functions with MCP-Pro’s rotary knops push button event to switch between managed and unmanaged mode. In the pilots guide I could not find a key code for this function. But by using Eric’s exporter interface it would be easy to implement it. The “only” problem is that I cannot detect the “key” event. As FSUIPC does detect it in the button assignment window I hope to have a chance to detect it somehow through it. But how is the question! Can you help? Thanks for your support. It is really excellent. Rgds Guido