Jump to content
The simFlight Network Forums


  • Content Count

  • Joined

  • Last visited

Everything posted by Steve38

  1. There is a bug in GFDevFSX.exe that causes this problem when nothing is assigned in GFConfig to the GF46. GoFlight have fixed the problem in version 2.21 (or above), but currently its not released.
  2. Are you using LINDA? If so, make sure you disable the VR Insight MCP support, it makes the Goflight MCP go crazy.
  3. Run the Goflight program called GFConfig.exe. Click on the EFIS and MCP/MCP PRO to set the options as defined in the readme file. Then click File, Save Configuration As and then save it with a filename something like PMDG NGX.gfc GFConfig remembers the last configuration file you created/loaded, so all you need to do is ensure that if you have loaded or created another configuation file after creating the PMDG NGX file, load up GFConfig and click File, Load Configuation and pick the PMDG NGX configuration file. Best wishes Steve
  4. Hi Frank, I've just had a quick look at the other guys script and found the problem. It uses the same offset's as my script for the MCP so that when data is written by the open cockpits interface it is interpreted by my lua script as a change in the MCP state. Esentially the memory addresses 0x66D0 to 0x66DD are used by both scripts and therefore clash. The only way around this is for the scripts to be changed so they do not use the same offsets. Its late here, but a quick check seems to indicate that if you do a search and replace in my LUA file for every occurance of "66D" and replace it with "66E" and then save the file, that should sort out the conflicts. Best wishes Steve
  5. Hi Frank, You must make sure you have disabled the EFIS code in my script including the stuff you quoted. To do this, go to the user customisable section near the top and change: DISABLEEFIS = 0 to DISABLEEFIS = 1 That way, no EFIS code will ever be executed by script. If it persists I would firstly suspect the script you are using for the EFIS is sending the wrong LUA commands. Let me know how you get on. Best wishes Steve
  6. Thats very odd Frank. Something isn't right somewhere; but see how you get on and give me a shout if needed. Best wishes Steve
  7. Hi Frank, OK. Are you using LINDA and have you checked to ensure the Goflight configuration for the MCP PRO is set to compatiable add-on? For the switches that are causing problems, I want you to load up the NGX with my script and then go into FSUIPC/Buttons and Switches. I need you to check that you have nothing assigned here. Finally rename, your FSUIPC ini file and let FSUIPC create a new one. Add the lines from the readme.txt file in the script download and see if it works OK. Best wishes Steve
  8. Hi Franck, I have Goflight's MCP test program I can send you. It will enable you to check that everything from a hardware perspective is OK. PM me your email address and I'll send it to you. Best wishes Steve
  9. Since SP1b, the LUA script has been the cause of a freeze when returning to the FSX menu following a flight. I have posted a work around at AVSIM in the following thread, post number 114: http://forum.avsim.n...00#entry2209376
  10. You configure the Goflight equipment in GFConfig and then click "File" followed by "Save Configuration As". You then get the option to enter a filename for the configuration you just created, so in the case of the NGX something like PMDGNGX.gfc will do. You can have different configuation files for different aircraft, you just need to make sure you load the correct one before FSX starts, noting that it always will reload the last configuration file you used if you don't load one.
  11. Ok, can you message me your email address so I can send you a test program. Thx Steve
  12. Ok, have you made sure that in GFConfig you have the MCP PRO set to compatiable add-on? EDIT: Yes I have tested it with an orginal install with only SP1 applied.
  13. Do you have the latest FSUIPC installed (I'm using 4.749d) and are you using version 1.0 of the LUA script (it will tell you at the top of the file if you open it in notepad). Have you also tested to make sure that FSUIPC can "see" the buttons you are talking about by using the buttons tab in FSUIPC and flicking the switch? Best wishes Steve
  14. New version 1.00 provides a few bug fixes for SP1 users. See initial post in the forum for the new file. Best wishes Steve
  15. Hi Andy, I have the saitek yoke as well and don't have that problem. I would guess you must have something assigned in FSUIPC or the saitek software. It sounds like the button press is starting gfdDisplay.lua which runs a diagnostic. You may have that lua script assigned to the hat switch. Another problem may be electrical. Have you tried the yoke on a different port or hub. It may also be a conflict with LINDA if you are using that. I noticed that it incorrectly sees the MCP as VR hardware and does funny things. Turn off LINDA and try it. I think renaming ipcReady.lua in the modules directory will turn it off. Best wishes Steve
  16. Hi Francesco, All buttons run from the same routine so if there is a performance problem it would effect all buttons. I suspect that you think the CMD button is not engaging because it wouldn't engage in the Virtual Cockpit either. If you read some of the NGX forum posts you'll realise that the AP won't enagage under some circumstances, for example above a certain height and no pressure on the yoke (properly trimmed aircraft). No-one has reported this problem either so I think your issue is that the aircraft is not in the correct state to enagage the AP. Best wishes Steve
  17. Read post #55 here http://forum.avsim.net/topic/345151-goflight-efis-and-mcp-pro-partial-interface/page__st__50 Its to do with default profile settings in fsuipc.
  18. Be carefull with this extra script since it will result in dual read and writes which Pete identified as a possible cause for the displays freezing and potentially MCP lock ups. For those without a lock up problem go ahead if it helps. I'll look at refining the script further to improve performace, but at the moment its written to be safe and will be fine with people on older firmware. The vast majority of people have reported great success with it so far, so don't worry. I support people directly via email, so if you need support contact me on my email address at the bottom of the readme. Best wishes Steve
  19. The displays use the event.offset structure as recommeneded by Pete. There is a user customisable section at the top of the script where you can turn up the polling times to increase performance. They are set by default to balance out for most systems (not everyone has a 4.5Ghz i7!). Try increasing the polling times to get rid of any lag.
  20. ** UPDATE 14th March, 2012** Hi, Since a number of people have started to ask for help in installing the script, I decided to update known issues. 1) The freeze that occured (because the cleanup/exit routines called ipc.exit) has been fixed in FSUIPC versions 4.805 and above. Please install the latest FSUIPC so that you no longer need to remark out the aformentioned routine in the script. You can get it here: http://forum.simflig...pdated-modules/ 2) If you don't use Trackir and Ezdok, you will notice that the VC moves when using the MCP. This is because the mouse look command is sent to cancel out the mouse pointer being displayed. There is an option in the user customisable section of the screen to disable this functionality if problems are occuring. Change CANCELMOUSEKEY = 32 to CANCELMOUSEKEY = 0 3) 99% of the problems people have are incorrect entries in fsuipc.ini. Please ensure you remove all sections you have added related to NGX/Boeing 737 and include only these (no duplicate entries can be present): [General] ShortAircraftNameOk=Yes UseProfiles=Yes [Profile.PMDG NGX] 1="PMDG 737" 2="Boeing 737" [Auto.PMDG NGX] 1=Lua NGX_AUTO [buttons.PMDG NGX] various stuff here depending upon your own config [JoystickCalibration.PMDG NGX] various stuff here depending upon your own config Best wishes Steve ** UPDATE ** New version 1.00 provides a few bug fixes for SP1 users. Best wishes Steve ** UPDATE ** New version 0.16B provides a temporary solution for outer baro and mins dials on EFIS. Still work in progress, so if you need support contact me on my email address at the bottom of the readme. Best wishes Steve ------------------ ** UPDATE ** New version 15B fixes a few bugs and adds some performance enhancements. Still work in progress, so if you need support contact me on my email address at the bottom of the readme. Best wishes Steve ---------------- Attached is version 0.14B of an LUA script that now fully supports the MCP PRO / MCP and upto 2 EFIS (captain and FO). It now supports displays and lights. It requires the latest version of FSUIPC and the PMDG Hotfix 4. It's still a beta as I need some feedback to polish off any rough edges. Best wishes Steve GoFlight EFIS and MCP PRO interface for the PMDG NGX.zip
  21. Yes I think most Mcppro users have had that problem. It's a complete lock up though, displays, dials and switches which requires an unplug of the mcppro. Then you have the problem of fsuipc not seeing the mcppro anymore etc. It's so annoying when it happens. Perhaps at some point you could look at a way for fsuipc to re-recognise the mcppro after a replug.... That would be very useful. My issue is different though, just the displays freezing for a short period.
  22. Hi Pete, I have re written things using event.offsets and it works OK. I still get the odd display freeze though. I will test my script on some other peoples MCP's to eliminate any hardware faults. Thanks for your help Steve
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.