Jump to content

bussgarfield

Frozen-Inactivity
  • Content Count

    121
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by bussgarfield


  1. Hi.I am one of the newbies to FS2Crew and would like to ask some of you more experienced guys some advice.My system incoporates a Logitech 5:1 surround system plugged into the sound card. When I plug my Saitek headphones into the top of the computer (not the front in my case), the microphone is recognised (and has allowed me to do the Windows voice training) and I get the engine/cockpit noise through the headphones. When attempting to use FS2Crew (Voice Control), I can just barely hear the FO talking. The voice volume seems to be very low. When I unplug the headphones, I get the same issue through my speakers - low voice volume.Which leads me onto the other issue I have.How on earth do I get the voice only through my headphones and not the engine and general NGX noise. I have tried through the audio settings in the control panel to no avail.I am using Vista 64bit with Hi Definition on-board audio.I haven't been able to use my FO yet as I can't hear him !!Yours hopingGary


  2. Hi all,I contacted Opencockpits yesterday to enquire whether they would be updating their scripts now that the NGX SDK had been released so we can use all the other hardware that we may have - (NAV, VHF and CDU etc). I received this reply this morning.'Hello, Yes we are working on it, when the new scripts will be running we will send a news mail for all Opencockpits users.Thanks,'Alejandro.Your Opencockpits Support Team. So, it looks promising and will save Roar a lot of hard work too.Just for your info.


  3. Hi.An interesting review Robert, thanks for taking the time to do this.Sounds like a good bit of kit. I have gone down the route of a scale 737 MCP and EFIS unit which I now have working with the NGX. Buttons and displays where they should be which I find to be more immersive than a generic unit. That said, space is not a limitation for me and I am constructing a scale cockpit.I am sure that anyone else purchasing this unit will find it of benefit too.


  4. You guys are killing me!!...I've tried everything (most recent files from AVSIM) and now I can get the MCP to light up all "0's" but rotaries and switches don't work...I got excited when the MCP finally lit up only to be crushed when nothing worked...aaarrrrgggg!!!!!...I'm currently running FSUIPC 4.600a...would version make any difference???...Thanks in advance!!Steve Leingang
    Steve,I know just how you feel but believe me, you will get it up and running. Fred, John and Roar all helped me get my MCP and EFIS working.With the latest download from Roar, it is all there - a fresh sioc.ini, the Lua files and sioc.ssi.Despite downloading the latest files, I still had issues with the A/T not working and both FD switches not working. I carried on and lo and behold, after two start ups of FSX it is now all working as it should.I have just completed a full programmed flight and auto land from LFBD - LEAL. Best flight yet and all systems are go.Back to the issue in hand, have you got the latest version of SIOC? It will be worth getting that as well as the latest FSUIPC. You can then start building from there.It took me a good two weeks to finally get it sorted and get it sorted, you will.Good luckGary

  5. Phill,I normally get the same response from the FMC too. I do recall once that it actually recognised the gate I entered but for the life of me I can't remember the airport, although I do think it was a major airport (in the UK). I would imagine that the data base is just not big enough to store all the gates of all the airports.I use Navigraph by the way.


  6. HI,Opencockpit MCP script for PMDG 737 NGX is now updated.What is fixed?1. VORLOC Led on OP MCP didn't light up when selected.2. VERT SPEED selector on OP MCP gave DN instead of UP changes to NGX3. CWSB didn't functionAll issues have been solved in the LUA file.A new LUA file can be downloaded here: https://docs.google....jU5MmRiNmQ1NzliGo to the right on the Google doc page and download the updated LUA!!The version number is the same so you don't need to do anything else than replace the old LUA file with this one in FSXModules folder.A new updated version of Opencockpit EFIS script ( both ssi and LUA file) will be release in a day or 2.Happy autopiloting!
    Alberto, hope this helps.

  7. Hi Alberto.As you can gather by all my posts here, I am not the one to try and give you any advice on sioc but in relation to the the Captains FD - When I start up the NGX, whether cold and dark or running, the FD is always in the on position. A quick flick on the OC MCP resets it. I can live with that. It may just be a quirk with the NGX.In relation to the VS wheel, I do remember reading somewhere in this thread that someone else also had that problem but If I recall, the latest .ssi and lua had been fixed by Roar to combat that problem - I may be wrong.Fred and John, I wish I knew. I uninstalled both SIOC and FSUIPC and re-installed and the problem still persisted. I sent Roar the sioc and fsuipc .ini folders and it was the sioc.ini that was the problem. The .ini that he sent back to me was literally bare bones so there was obviously an entry in mine that caused a conflict some where.If Roar reads this then he may be able to expand on exactly what the problem was.


  8. Guys,Played safe as I am quite new to all this hands off and automated flying by doing PMDG's tutorial from EGKK - EHAM.PERFECTEvery button and encoder works in both the MCP and EFIS and I have had a more relaxed flight without having to keep changing views and using the mouse.Roar - excellent stuff mate and thank you.Whats next - FMC, VHF and NAV radios or TCAS ???Regards to all - now off to have another play !!


  9. I think I am going to be a really happy chappy later today.A big thank you to Roar.I sent Roar my sioc.ini and fsuipc.ini files for him to study. He came back to me saying he had found faults in the sioc.ini file and sent me the correct one. I copied that into my SIOC folder, fired up FSX and then SIOC and I had all my digits light up on the MCP. Things were looking good.I loaded up the NGX and hey presto, I can now control the NGX MCP from my OC MCP. Not only that but the OC EFIS module also works the NGX EFIS too.I have yet to fly with them and use them in conjuntion with the FMC but I will plan a flight later today (once the good lady gives me a bit of time) and let you know how I get on.Thanks again for all that have shown an interest in sorting out my plight especially to Roar, Fred and John.Fingers crossed and I will post an update after my flight later.Regards


  10. Hi all.I have checked and re-checked all connections. I have re-installed both SIOC and FSUIPC. I have also transfered FSX to the CProgram Files (x86) location after reading up on the FSUPIC installation that this is the recommended location. The old FSX location on just C has been deleted. FSX and the NGX run fine.All Lua and .ssi files have been re-installed and the sioc and fsuipc.ini files updated accordingly.The MCP and EFIS still refuse to work for me.Any further suggestions will be most welcome.


  11. Thanks John, always worth a try but to no avail I'm afraid.It has got to be something really silly that is preventing these modules from working.I am going to start from the ground up and check all the basics first - all the connections and power feeds. Swap them around and then start up again. If I can eliminate power sources and usb connections then it must be something to do with software/programming.


  12. Just as an aside to the topic in hand, I am feeling really chuffed with myself. I have just completed a flight from EGSS to LEAL having programmed the FMC and a fully automated landing which is a first for me.So, Roar.Uninstalled FSUIPC and cleared out the modules folder, re-installed FSUIPC and the lua files and put the lua references under AUTO in the FSUIPC.ini file.No change.We will get there - in the end.


  13. @RoarI have tried changinging the timer value to 1000 and 10000 - no change.I have tried putting ! infront of the MCP line and later in front of the EFIS line in [Auto] - no change@JohnNo, I am not using a saved flight or flight plan. The difference in the system time and the FS time are purely down to loading the NGX in the daylight hours whilst the system clock says it is night time. This morning I loaded the NGX at the same time as the system clock and there is no time difference in the NGXMCP_202.log (see below).********* LUA: "NGXMCP_202" Log [from FSUIPC version 4.758] ********* 124786 System time = 07/02/2012 10:59:29, Simulator time = 10:59:02 (10:59Z) 124786 LUA: beginning "C:FSXModulesNGXMCP_202.lua"I have downloaded the MCP test program from OpenCockpits to make sure the LED's and digits actually still work - they do and the encoders and button presses are registered too. I tried the test whilst FSX and NGX was running and it came up with FSUIPC status - OK.The extract from the FSUIPC4.log this morning (below) shows that FSUIPC appears to be trying to start the MCP and EFIS (highlighted in bold txt).********* FSUIPC4, Version 4.758 by Pete Dowson *********User Name="Gary Buss"User Addr="bussgarfield@FSUIPC4 Key is providedWideFS7 Key is providedRunning inside FSX on Windows VistaModule base=61000000 968 System time = 07/02/2012 10:57:26 968 FLT UNC path = "C:UsersAdministratorDocumentsFlight Simulator X Files" 1030 Trying to connect to SimConnect Acc/SP2 Oct07 ... 1061 FS UNC path = "C:FSX" 1872 LogOptions=C0000000 00000001 1888 Wind smoothing fix is fully installed 1888 G3D.DLL fix attempt installed ok 1888 SimConnect_Open succeeded: waiting to check version okay 1888 Trying to use SimConnect Acc/SP2 Oct07 4025 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 4025 Initialising SimConnect data requests now 4025 FSUIPC Menu entry added 4072 C:FSXFLIGHTSOTHERFLTSIM.FLT 4072 C:FSXSimObjectsAirplanesAircreation_582SLAircreation_582SL.AIR 19438 C:FSXSimObjectsAirplanesPMDG 737-800NGX WLB737-800WL.AIR 124052 System time = 07/02/2012 10:59:29, Simulator time = 10:59:01 (10:59Z) 124068 Aircraft="PMDG 737-800NGX PMDG House Winglets" 124723 Starting everything now ... 124786 FS Control Sent: Ctrl=69990, Param=536870912 124786 FS Control Sent: Ctrl=69990, Param=131072 124786 FS Control Sent: Ctrl=69990, Param=-2147483648 124786 FS Control Sent: Ctrl=69990, Param=524288 124786 FS Control Sent: Ctrl=70000, Param=536870912 124786 FS Control Sent: Ctrl=70000, Param=131072 124786 FS Control Sent: Ctrl=70000, Param=-2147483648 124786 FS Control Sent: Ctrl=70000, Param=524288 124786 KEYDOWN: VK=54, Waiting=0, Repeat=N, Shifts=0 124786 .. Key not programmed -- passed on to FS 125035 FS Control Sent: Ctrl=70010, Param=536870912 125035 FS Control Sent: Ctrl=70010, Param=131072 125051 KEYUP: VK=54, Waiting=0 125846 FS Control Sent: Ctrl=70006, Param=536870912 125846 FS Control Sent: Ctrl=70006, Param=131072 127906 Advanced Weather Interface Enabled 129590 KEYDOWN: VK=49, Waiting=0, Repeat=N, Shifts=0 129590 .. Key not programmed -- passed on to FS 129700 KEYUP: VK=49, Waiting=0 217778 KEYDOWN: VK= mega_shok.gif, Waiting=0, Repeat=N, Shifts=0 217778 .. Key not programmed -- passed on to FS 217871 KEYUP: VK= mega_shok.gif, Waiting=0 271692 KEYDOWN: VK=52, Waiting=0, Repeat=N, Shifts=0 271692 .. Key not programmed -- passed on to FS 271895 KEYUP: VK=52, Waiting=0 274827 Sim stopped: average frame rate for last 155 secs = 13.3 fps 376041 KEYDOWN: VK= mega_shok.gif, Waiting=0, Repeat=N, Shifts=0 376041 .. Key not programmed -- passed on to FS 376134 KEYUP: VK= mega_shok.gif, Waiting=0I have no idea how the smileys got there !!!!


  14. John,NGXMCPEFIS_PP_202.SSI loaded into SIOC. FSUIPC.ini and sioc.ini checked. All relevant entries are as they should be.SIOC monitor shows all buttons and switches to be working on both MCP and EFIS. SIOC window shows FSUIPC connected.I went into SIOC and deleted all .ssi files and text relating to any MPC and EFIS just leaving NGXMCPEFIS_PP_202.ssi in case there were any conflicts.Still no joy. I have even tried connecting the modules to different powered USB hubs just in case. I have swapped the power supplies to both modules around in case there were issues there too but still I have no joy in getting either to work with NGX.

×
×
  • Create New...