Jump to content

bussgarfield

Frozen-Inactivity
  • Content Count

    121
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by bussgarfield


  1. Hi Fred, hope you are well.Glad you are up and running. If you recall we had a chat regarding my issues in getting the MCP working.Just by way of an update, I completely uninstalled SIOC and FSUIPC and started from fresh. Having re-installed them, I downloaded Johns combined MCP/EFIS text and compiled it into my NGXMCP.ssi file. I have followed the advice regarding the configuring of the MCP at 0 and EFIS at 1 in the sioc.ini. All knobs and switches on both the MCP and EFIS are shown as working in the sioc monitor and in the main SIOC window appear to be good to go.I start FSX and the NGX then run SIOC and still I have no lights on the MCP and it or the EFIS still wont work within FSX or the NGX.Would it be possible for you to send me copies of your sioc.ini and fsuipc.ini files so I can make some comparisons with mine. The SIOC main window shows that FSUIPC is OK.RegardsGary


  2. The next thing I would do is to make sure that FSUIPC is not using other hardware/software that utilize the free offsets between 66C0-66FF.So make a backup of your FSX/Modules , then1. Uninstall FSUIPC2. Reinstall latest FSUIPC3. Modify fsuipc4.ini with line 1.lua NGXMCP_202 in the AUTO section4. Copy NGXMCP_2.02.lua to your FSXModulesTry againIf that doesn't help there could be problems related to that you have your FSX installed under the C: drive together with Vista. You could try to install FSX in its own directory.AT last you should ( not only for this issue) move over to WIN7 OS. The FSX behaves much better there.
    Hi Roar,Uninstalled FSUIPC and re-installed as suggested. FSX modules updated with the NGXMCP_202.lua file and FSUIPC.ini file updated with the entry[Auto]1=lua NGXMCP_202There were no further possible conflicts as every thing was clean.Started up FSX and NGX (for FSUIPC). Exited FSX. Started up FSX and NGX again then started SIOC once lua had begun - the result - the same. The MCP still will not light up and when buttons are pressed, there is no log in the FSUIPC Console log. The SIOC monitor registers the pushing of buttons and turning of the encoders.I understand what you say about the FSX location but I uninstalled from the CProgram Files (x86) location on the advice of the NGX Avsim forum prior to it's release as they said it would eliminate any issues with virus updates and and windows updates whilst FSX was running.The MCP worked fine with the default 737 and my set up with FSX in it's current location and with Vista. I will update to WIN7 in the future but surely I should be able to run SIOC, FSUIPC lua files and the plug and play addons on my current set up.You and Fred have been a great help and I am sure that we will get this problem sorted in the end. Given that all lua files and FSUIPC have now been refreshed (and they work on other peoples systems), I am wondering if the problem still lies with SIOC somewhere.Thanks again for your help.Gary

  3. Roar.2 -- have been entered in the timer line and saved, changed to a different NGX and still no difference.Yes I am using other hardware through FSUIPC. Throttles, rudder pedals, ailerons and elevators and the autobrakes. I think that is all.Would that be beneficial to delete all these settings and offsets.


  4. Hi Roar.Firstly, I changed the value from 100 to 1000 in the last line of the lua file but still with no joy.Secondly, I have downloaded the latest version of FSUIPC 4.758 and started up FSX but the MPC still does not spring into life.My VHF, NAV and TCAS work in NGX with the old and existing scripts apart from the selector knob on the TCAS so I know that there is communication between SIOC and FSX. I know that Vista is not the ideal platform for FSX but at the time of purchasing the computer, Vista was the latest system at the time.Gary


  5. Hi Fred.Like you, when the going gets tough, the tough get going - as the saying goes but in my case the weak get going so I had another go at the 1st tutorial from EGKK to EHAM - very successful with the finger on the mouse !!!Still no joy with linking the MCP with the NGX. I saved my complete SIOC folder then deleted everything bar the bare essentials and loaded the MCP ssi. into this (the only ssi file there) and still no joy. As per Roar's instructions, the lua file was put in the FSX modules folder and the[Auto]1=lua NGXMCP_202 copied into the FSUIPC ini file which resulted in the script [LuaFiles] 1=NGXMCP_202 materialising in the FSUIPC ini file.Still with no joy, I put the complete script from the lua file into the FSUIPC ini file and there was no difference.I am a SIOC 'dummy' when it comes to getting things up and running and rely very heavily on people like you, Roar and John - so please be gentle with me.We will get this sorted and it is refreshing to see that others are having great success with the hard work that has been put into helping the likes of me get rid of the mouse !RegardsGary


  6. Hi Roar, John and the rest of you guys. I haven't been onto the forums here for a while so imagine my surprise when I saw this thread started by Roar. Since I started buying items for my cockpit nearly four years ago now, I have stuck with the OpenCockpit p&p modules and panels. I had the MCP, VHF, NAV and TCAS working fine with the default 737. I have not got a clue regarding sioc so I read this thread with quite some anticipation and it seems that many of you have been rewarded by the efforts of those concerned.I downloaded the latest MCP files that Roar presented to us and followed what was suggested in the acompanying readme text. I fired up FSX and loaded the NGX but nothing. The MCP works through the compiler - or at least the buttons and encoders are recognised but I cant get it to link with the NGX.Over the years I have added new scripts to the sioc.ini file with my latest efforts of trying to get my flaps gauge working.The first question that I have is this, have I got too many scripts? I am sure some are now redundant so would this in anyway confuse sioc or cause some modules to fail. I have still got the CDU and EFIS to sort out as well in the future. Now we seem to have the facility to link the OC modules to the NGX, I will not be needing the scripts for the defaulf aircraft any more so would it be worth my while to to uninstall all my sioc scripts, files and folders and start agian from scratch or should I persevere with trying to use these latest scripts 'as is'.


  7. Thanks a lot Michael. I saw your original post stating you were going to them and you have done a great job. I flew the 1st tutorial tonight so guess what I will be doing tomorrow now I have the check list to hand? - starting up cold and dark.It is a wonderful guide around the cockpit and overhead as well to help a relative novice like myself as well as a procedural document. Thanks again for your time and effort.


  8. Hi to all at PMDG and thanks so much for this wonderful piece of software that has now come to life in my sim. I had to uninstall/reinstall FSX to get it up and running properly but now I am over joyed. I have until now been flying the FSX default 737 and the procedures with the NGX are so different and so much more advanced. The sound just blows your socks off (even impressed the wife) and I have no stuttering even on my meagre system (2 yrs old). Tonight I followed and completed Ryans tutorial from Gatwick to Schipol. To say I was impressed would be an understatement but when I lowered the HUD on finals, I was totally gobsmacked. There has been a lot of gripes and whinging in the forums prior to release so lets just hope that those days are gone and you guys can now take a well deserved break - you could even have time for a shower now!! Cheers guys. Gary


  9. Thought I would check in before hitting the sack. It is 00.10 Spanish time. What the heck. This Tuesday Spanish time, Uk time, US time or next Tuesday. What many of you forget is the fact that it does not matter when the price and package details are released, you can't buy the blooming thing yet. Just chill and wait.Gary


  10. Hi Martin.I had the set of manuals delivered to me in Spain via UPS. It took about two weeks and I was able to track their progress. I incurred no additional costs.They are very in depth and for a novice 53 year old, I am finding them quite hard to get my head around them but with a lot of re-reading, they are starting to come together.There will be a PDF manual released with the NGX so it is up to you whether you want to wait or pay for the very professionally made originals.As suggested earlier by Steven, AoA will be producing a comprehensive video tutorial for the NGX so I am hoping that with the combination of the manuals and video tutorial, I will be able to get a grasp of the poper procedures and flying of the new aircraft.Hope this helps.Gary


  11. Doug,Just to second what Shane said. I run Saitek yoke, throttles and rudders pedals. I have found that it is best to plug the yoke into a different powered usb hub to the rudder pedals. The throttle should be plugged into the back of the yoke. I also found that using FSUIPC for all my axis was a god send. If you go down this route, save all your original FSX settings first and then delete all the axis controls in FSX and let FSUIPC take over. You have much more control with regards to settings and calibration. If you go down the FSUIPC route then I have some PDF tutorials which may help you if you are new to FSUIPC especially designed for the Saitek yoke.Gary

×
×
  • Create New...