3rdwatch

I have some issues too. I had to reboot my controller to get switches to work. I started the whole thing in VR instead of 2d and switching over and I had some of the wounds but no warning or call outs. I am like you I prefer the 733 and MD-80 era vs the 738. But they have VR so dialed in on the Zibo. I am not sure why it's so hard for other aircraft.

Anyone have any ideas why I lose the sounds when I go into VR? I have this problem with the rotate MD-80 also but not the ZIBO.

First I want to say a big thank you for doing this update. I wish I could have given some feedback sooner but world events in the last 2 weeks have kept me busy. For some reason when I went to VR mode I lost all of my sound. I am still looking into this and was able to get the FT Sim fmod to work. It's not perfect either but I was able to at least have some sounds. I hate to compare to the ZIBO but right now I have found nothing easier to fly in VR, I use hard wired controls so VR is more view and switch movement. I found a few switches a little difficult. The APU bleed was hard to move from the Capt position. Also some of the buttons for the EHSI data were difficult to turn off for some reason. I do like the bigger green boxes on the switches of the Zibo Small nitpicking but overall it was amazing.

Jan, I know a lot of VR simmers actually use hard wired controls. In my case I have a full 737 quadrant from Jetmax, tiller rudder pedals and a yoke.. When I fly vr I only use the right manipulator for switches. All my trimming etc is on my yoke. Thanks for all the hard work

Tom, That is great news. Thank you.

Thank you everyone for the responses. It is a little heartbreaking not to be able to fly the update in VR. But it is nice to know that an update will eventually be coming.

I got it and the good news is no error mesg's or crashes. So it's a great starting point. Obviously that is the most important. I hope you really didn't tweak the knobs. Again I know this is baby steps but the they were very sensitive but my guess is you were more concerned with seeing if it work. That it does.

Awesome, I will check back later tonight

I am with you on this one. I just need the knobs/switches to be operable. I can't imagine trying to fly with just VR controlers

Yep I think the naming is an issue. Here is the complete VR file from SimVRLabs SimVRlabs-IXEG-737-V100(1).zip

Jan, Yeah that's what I don't get get. It's acting like the datarefs's path changed. I am probably different them most VR users. I only use the VR control to manipulate knobs and switches. I still have a yoke and a full 737 quadrant and tiller. So even though I am in VR I still physically touch the controls. I usually only turn on my right hand controller to manipulate everything else.

Jan, This is portion of my error log. Was there a change to the data refs? I am confused as the VR config is fairly simple file. I have attached the old VRConfig 03:01.785 I/OVR: Reading VR conf file: Aircraft/X-Aviation/IXEG 737 Classic/B733_vrconfig.txt 0:03:01.785 W/VRCONFIG: Could not find matching manipulator for type: axis_knob with dref1: ixeg/733/MCP/mcp_plt_course_act dref2: (NONE) tooltip: 0:03:01.785 W/VRCONFIG: Could not find matching manipulator for type: axis_knob with dref1: ixeg/733/MCP/mcp_heading_bug_act dref2: (NONE) tooltip: 0:03:01.785 W/VRCONFIG: Could not find matching manipulator for type: axis_knob with dref1: ixeg/733/MCP/mcp_bank_angle_act dref2: (NONE) tooltip: 0:03:01.785 W/VRCONFIG: Could not find matching manipulator for type: axis_knob with dref1: ixeg/733/MCP/mcp_cplt_course_act dref2: (NONE) tooltip: 0:03:01.785 W/VRCONFIG: Could not find matching manipulator for type: axis_knob with dref1: ixeg/733/ehsi/ehsi_range_pt_act dref2: (NONE) tooltip: 0:03:01.785 W/VRCONFIG: Could not find matching manipulator for type: axis_knob with dref1: ixeg/733/MCP/mcp_ias_mach_act dref2: (NONE) tooltip: 0:03:01.785 W/VRCONFIG: Could not find matching manipulator for type: axis_knob with dref1: ixeg/733/MCP/mcp_alt_target_act dref2: (NONE) tooltip: 0:03:01.785 W/VRCONFIG: Could not find matching manipulator for type: axis_knob with dref1: sim/cockpit2/gauges/actuators/barometer_setting_in_hg_pilot dref2: (NONE) tooltip: 0:03:01.785 W/VRCONFIG: Could not find matching manipulator for type: axis_knob with dref1: sim/cockpit2/gauges/actuators/barometer_setting_in_hg_copilot dref2: B733_vrconfig.txt

Jan, I am not sure about entitlement but numerous payware aircraft are missing vrconfig. VR makes up only a small segement I get that. Honestly first and 2nd gen VR wasn't very good. I have a reverb and its resolution is great. I worked the ramp while I was going to school and the first time I did a walk around of the plane and it was in scale was really mind blowing. There was one for the IXEG that worked fairly well but X-Plane is saying all the datarefs changed. A VR config file took the Rotate MD-80 from useless to an amazing experience. The standard for a VR config is hands down to me the ZIBO. I am not sure who made it but it is solid.

Is there any chance we can get a VR Config file for this bird. Right now most knobs are ridiculously touchy in VR and not usable. I know we make up a small segment but it is the wave of the future. If you have never used VR it will blow your mind.

Go Flight

Nope never did. I have to set it to increase mixture, So they work at start up but I shut down I still have to move them then click the shut off in my 3d cockpit

I really do appreciate you taking the time to do this for me. For the life of me I can't figure out why it wont work. You even have me reading the Flywithlua documents. It does disable the cutoff in the virtual cockpit so something is being read I just don't know what. Again thanks for all the help.

Well I was really hoping it would work. Just to make sure the file goes in the flywithlua/scripts folder. Also do the fuel lever buttons need to be unassigned? The jetmax throttle is plug and play so it's not a very complex unit. X-plane doesn't seem to read it any different than by saitek throttle.

Thank you but no success. Engine 1 is 129 and engine 2 is 128. I tried editing the file myself and changing to 127 and 128 but the levers do not move and they are frozen in the sim.

Thanks for helping with this. They seem to work like this Recognized as switch When you toggle the handler up to idle, a button press displays and it stays. I mean it keeps displaying like something went to ON When you toggle the handler down to cutoff button representation on the display turns off. Here is a pic of the switches at idle and cutoff

Hey I appreciate the help that is what I have it set at. The problem is when I move them to cutoff there is no button. I have to move the lever to cutoff on my throttle and then enter the 3d cockpit and move the lever to cutoff to shut down.

The JETmax throttle does not require any software. Xplane recognizes the fuel cut off as a button. So when placed in the "idle" position it show a button press.Yes i run flywithlua

I am wondering if someone can help me out here on what I did wrong. Let's start by qualifying that I have a/p disconnect from the ixeg 737 mapped to my go flight home and the Ixeg A/T disconnect to the A/T disconnect on my Jetmax TQ. So not the default xp10 commands. So so I am flying in LNAVand VNAV into KSEA I am not a huge fan of Vnav and switch over to me tuning the MCP while using LNAV. I am on a 7 mile final to rwy 34R at KSEA and decide to hand fly the approach I move my ghost throttle over the A/T ones and hit the a/p disconnect. It all disconnects however I leave the auto-throttle connected. I decided time for me to disconnect the a/t. I hit the button on my throttle and there is a loud switch sound and the auto-throttle switch tuned off on the MCP. Now the real problem is here. I pulled throttles back but the engine won't reduce power it stays at AT speed and won't reduce power . Is there something I missed. Thanks 3rdwatch