Steve38
-
Posts
81 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Steve38
-
-
Are you using LINDA? If so, make sure you disable the VR Insight MCP support, it makes the Goflight MCP go crazy.
-
can anyone tell me how create an NGX configuration for GFConfig i can find anything show you how
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
-
You are a god, that works, just tested quicly but VOR/ADF is now working without interfering with the MCP, will test during a full flight tomorrow ( this afternoon lol)
thanks again, for your kindness.
Franck
LOL, hardly. Glad its working OK though.
Best wishes
Steve
-
Hi Steve, the EFIS is set to 1 into your sript so it is disable.
The other script I am running is this one : NGXEFIS_PP_2.02.lua, you can find it on AVSIM by searching opencockpit. I prefer to tell you the script than copying it here without the authorization of the writter.
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
-
Hi Steve038, I am sorry to disturb you again, but I have a question, could you please tell me what is the function of this part of your code :
local function toggleVORL(state, unit)
....
end
Here is why I am asking you the question, I have an EFIS from opencockpit, and I use a lua script from roarkr on AVSIM, and when I push the VOR 1 switch to VOR 1 , I have my MCP Pro HDGSEL button that light up, and then immediately light off, and of course on the NGX, I can see that the VOR1 swicht goes back to off, even if on my Opencockpit EFIX the switch is still on VOR 1. Have of course the same problem using ADF 1 / VOR 2 / ADF 2.
Do you have any idea what can I make to solve the problem.
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
-
Hi Steve, it is completly crazy.
I went into FSUIPC and played a little bit with all the button to see if something was attached to one of them like you told me, I went back to FSX activate the lua script like I always do, and guess what now it works ....
I dont know if the test program as done something, if the fact that I went to FSUIPC without activating the script and play with the button did something, but now it works again.
Anyway, a big thanks for your patience and your help, and of course for your EXCELLENT script.
Hope I wont come back again i few days ;)
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
-
I Steve I have tested with the check program, every thing is OK, all button are working, the swtiches too, and I can press multiple button at the same time.
So the problem is comming somewhere else. FSUIPC maybe, I have the last version install. Could a script be interpreted differently beacause of regional settings ?
Does the NGX as to be configure in a certain way ( lbs or kg, mm hg etc...) ?
Thanks for the help you may provide.
Franck
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
-
Hi every one, I am sorry to post here again, but after the SP1 update, the script doesnt work any more, I have exactly the same problem as a few days ago, the rotaries work, but the A/T switch, FD switch dont work. I dont understand where the problem is coming from.
If I click in the VC, I can see the green led switching on on the MCP Pro. If I use the switch on the mcp pro, I hear the click in the VC, but the switch doesnt move.
This plane is driving me crazy.
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
-
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:
-
can anybody tell me how to creat the gfconfig, i open up my go flight gfconfig could find a optaion to creat the pmdg file
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.
-
Yes the config is set on "Compatible Addon"
I really dont understand why it has work, and now the switches refuse to change their position.
Franck
Ok, can you message me your email address so I can send you a test program.
Thx
Steve
-
I steve, the answer is yes to all of your questions. I have tested also with FSUPIC version 4.76 (the one I did use before the upgrade of my computer). FSUPIC see correctly the button of my MCP Pro, as you can see in my pevious message, everything works perferctly, only the swithes are not working, but I can hear the switch in FSX when I use the MPC PRo, but it is not activate in FSX. I did test my MCP Pro with the original B738 of FSX, and the switches work correctly.
I remember with my old computer, I gave install the PMDG B737, all the hotfxes and then the SP1, on my new computer I did install the PMDG 737 + the SP1 directly without using the hotfixs in between, any one have tested this way ?
Thank you for the help.
Franck
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.
-
hi, everyone, first thank you for your work.
I have flew with this script for 2 months with no problem.
Last week I did change my motherboard and processor, and reinstall everything (Windows, FSX etc...), and since then, the FD, AT switch doesnt work, when I use them on the MCP pro, I can see and hear that somthing is done, but the change is not active in he VC. If I click in the VC on one of the switches, I can see the green light lightning on the MCP Pro.
Do you have any idea ?
All the drivers and PMDG 737 are up to date.
thanks
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
-
steve
tar,,,,i got rid of linda and the hat switch is good again,,,,and your scripts a good un with the goflight mcp pro
Andy
Good news!
Best wishes
Steve
-
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
-
Hi steveo38
ive been using the lua script for a few days and find it great except in my case a small prob.
i use a saitek yoke as well,,,,and each time i use the hat switch to pan my view around the virtual cockpit,,,all the numbers displayed on the goflight mcp change and flash for a second or 2 then revert back to there correct values,,,,have you any ideas what i need to change.
ive never mapped the hat switch on the yoke so its auto detected by fsx commands.
thanks
Andy
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
-
Hello Guys....
Good, Good news... I've reinstalled PMDG with latest hotfix, latest 2.03 GF driver, add buttons 321, and change userprofiles to NO in FSUIPC.ini, with lastest LUA release by steve.
And...it works !!! When plane is loaded MCP turns on values, Rotary are OK with a lite lacks , Button OK with a lite lack too expecially for A/P engage button.
A/T & F/D are ok realtime !
But the new is that NO freezes ( since now... keep fingers crossed!! )
There is something that we can do for eliminating lags when rotate and A/P engage I have to push it more that 3 times before have it on. I see that if I select before ALT HLD, V/S or HDG it turns on faster ( it is not a strange behavior ? )
Regards,
Francesco
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
-
New version added. See top post.
Best wishes
Steve
-
plz standby.. i just tryeid to re-install to reprosess of what could have happend. I am as confused as az1228 latest version of FSUIPC the Script steveo38 gave only shows dashes and buttons dosent work..
sounds wired it worked before also when inserting my old fsuipc.ini file from before it works again ??? but whit the new nothing happens.
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.
-
Fantastic! I'll let you know ... many many thanks!
Francesco
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
-
Well i just tryeid it and it worked ok,on my short testing. but like whit the driver the displays dosent show the same, before after 0.5 - 1 sec. depending on the setting used bu cant remove the lag but might be the file from goflight as same whit gf driver. + when plane crash or so the GF device gets blank. but els it seems to work quite good. exsept from the known mouse problem.
About the displays i cant say as im not much into the structure you use but mabe by let the display run as a lua file for it self might help. I did it that way on for pmdg J41 and the rest of the lua files and it works whit out any lag.
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.
-
** 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
-
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.
-
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
GF46 Button 0 crashes FSUIPC
in FSUIPC Support Pete Dowson Modules
Posted
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.