Jump to content

mmerelles

Members
  • Content Count

    1,184
  • Joined

  • Last visited

  • Days Won

    29

mmerelles last won the day on June 29

mmerelles had the most liked content!

Community Reputation

451 Excellent

4 Followers

About mmerelles

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

7,756 profile views
  1. You need to know some new concepts. -True heading (212 shown by the IRS display). This is the TRUE heading the aircraft is following in relation to earth's geographical north (not the magnetic north) the difference between true vs magnetic varies across the globe, you may see isogonic lines/charts -ND heading (244). The NAV display shows the heading the aircraft's nose is pointing in order to maintain the desired magnetic course 236. Since you have a VERY STRONG crosswind coming from the right, AP is pointing the aircraft's nose to 244 in order to compensate those strong winds trying to drift the aircraft out of desired 236 track. if no crosswind components were present ND heading and planned magnetic course should match. -Magnetic course. This is the magnetic course the aircraft should follow as per the flight plan. hope this helps
  2. What hardware you have? I have seen several forums post were people using WMR hardware have no sounds if they do start xplane before starting WMR.
  3. this is a known behavior of current vnav implementation, if you are planning to fly a SID/STAR having dual altitude contrains. i.e cross waypoint 123 below XXX and above ZZZ then the FMC will code invalid altitudes and prevent vnav from engaging. It is important you delete those restrictions and re-enter them manually correctly until vnav code is redone.
  4. It is a safety warning on the real thing your throttles are at IDLE and your landing gear is not down!
  5. I presume there is a confusion here? IXEG_user_prefs.txt is the file updated/modified by IXEG to incorporate new features added B733_prefs.txt is the xplane quick_look feature (numpadkeys). Make a copy of this and place it back after an update hope this helps
  6. xplane default & active sky may be using different weather sources. please note WIND DIRECTION AND SPEED on the EHSI will come available when winds are GREATER THAN 6 KNOTS! ACTIVE SKY had 5 knots thus not activating the EHSI report XPLANE DEFAULT had 8 knots by the time you did the test thus SHOWN. I do use ACTIVE SKY nothing wrong, you are on the very limit of SHOWN vs NOT SHOWN on the EHSI. In aviation winds 5 knots and below are considered calm and will be reported as calm when landing by ATC.
  7. Hi @Stratosfeerick All brands/controllers have its own "personality" and the average sensivity setting may not be optimal, besides the personal preference factor as well tip: 1. textedit the file "vrconfigs.txt" found on your IXEG 737 root folder (make a backup first just, in case you do something wrong) 2. search for "radios" you should find a section that looks like below: BEGIN_MANIP drag_xy ixeg/733/radios/radios_nav1_mhz ixeg/733/manip_placebo ACTION axis_knob -40 40 1 ixeg/733/radios/radios_nav1_mhz DEG_PER_ACTION 100 WRAP_MANIP END_MANIP BEGIN_MANIP drag_xy ixeg/733/radios/radios_nav1_khz ixeg/733/manip_placebo ACTION axis_knob -40 40 1 ixeg/733/radios/radios_nav1_khz DEG_PER_ACTION 100 WRAP_MANIP END_MANIP BEGIN_MANIP drag_xy ixeg/733/radios/radios_nav2_mhz ixeg/733/manip_placebo ACTION axis_knob -40 40 1 ixeg/733/radios/radios_nav2_mhz DEG_PER_ACTION 100 WRAP_MANIP END_MANIP BEGIN_MANIP drag_xy ixeg/733/radios/radios_nav2_khz ixeg/733/manip_placebo ACTION axis_knob -40 40 1 ixeg/733/radios/radios_nav2_khz DEG_PER_ACTION 100 WRAP_MANIP END_MANIP 3. Change the value 100 to 300 i did highlight here in red for the nav radios Mhz & Khz knobs. You may play higher or lower if desired later note: you need to reload the aircraft to take effect hope this helps
  8. At present time you will have to setup weight, fuel, gpu, and general aircraft preferences over the 2D window as said on the IXEG announcement, but i am quite sure the IXEG menus will also be integrated to VR later. Anyway, i do use their previous version (1.21) with a mod for VR and you have to only to pull up your VR headset for a minute to use the mouse over the regular monitor to set the aircraft parameters then put your vr heaset back again. You do not need to disable/enable VR or anything like that. link to the announcement
  9. I am using a hardware usb tiler (microsoft wheel) and rudder pedals, everything works ok always. No issues. Jan, for your evaluation, you may implement a user preference -When set to tiler, rudder works 7 degree, the tiler does its job at slow speeds (by 78 degree if i am not mistaken). Helps for cockpit builders and improved hardware setups -When set to yaw, the peddals do both as it does now, for most users having no tiler axis. Having said that, i don't push the rudder pedals but the tiler for taxing and can leave as is. works great anyway.
  10. Did you push in the steering wheel on the pilot's side panel?
  11. Map this command "LES/CMD/CW/button/AP_disconnect" to a yoke button. This is the RED button found on the aircraft yoke. first clic disconnects AP second clic silences the Alarm as per the real thing.
  12. yes it does integrate to xplane. You install the app in your iphone/ipad and you do all the weight and balance programming there over a graphical interface. You configure passengers, payload, fuel, etc. and the app will configure xplane/aircraft when you hit load. it also offers several other nice features for the flight
  13. Happy to hear this is working for you. I wouldn't think the sim pauses are related to vrconfig but to loading or something related to the sim. But it is nice if you continue to use it and report feedback. I am waiting a new update from ixeg since some issues/bugs were reported to 1.3 to continue the job. Anyway i am still testing on my own to perfect sensivity and all that stuff in preparation.
  14. @3rdwatch In order to make the IXEG 1.3 work under VR i had to do 2 things: 1. Create a new vrconfig.txt file from scratch to accomodates their newer manipulators 2. but it didin't work still, after further debugging i realized the ixeg cockpit_281.obj file contains quite a bit of trash characters most likely coming from issues on the laminar's blender exporting tool. So i cleared them up and got it working nicely I will share my findings with IXEG team for their testing/evaluation, maybe this helps out to save some time/effort to start providing their bird vr ready Please find attached 2 files, both should be placed on the 733 root folder (make a backup first of their original B737_cockpit_281.obj for safety/rollback if required) This is the list of things i already covered (tried to cover the most critical), please test them for some feedback and i will continue to cover the rest of the manipulators on the cockpit -Both Course selectors -Heading bug and BANK angle -IAS -ALT & VS -Pilot Copilot & stby Altimeters -Auto Brake knob -Nav1 & 2 -Comm 1 & 2 -Pilot & Copilot DHs -EHSI Mode & Range selectors for both pilot & copilot -IRS system. left, right modes & display selector -Left & Right engine start knobs B733_vrconfig.txt B733_cockpit_281.obj
×
×
  • Create New...