mmerelles

as long as i understand they did create its own modified b733_cockpit.obj file to create manipulators that were not present on the ixeg file. i.e. to manipulate the yoke via controllers. But i am trying to just use the vrconfig.txt file from them (and modified it to eliminate all yoke, throttle and those manipulators i do not need) and xplane keeps telling the datarefs does not exisit. i.e. course, ias, hdg, etc.

I just realized the file B733_cockpit.obj is not there. There is a another file B733_cockpit_281.obj file instead. That would be the same or a problem?

yes, a mix of phisical + vr is what works best to me I do use a phisical yoke, rudder, tiler and TQ + a VR setup based on Samsung odyssey + controllers I have been using VRLABS VR mod for the IXEG but it no longer works for 1.3 datarefs not found too.

In order to the FDs, A/T, A/P, LNAV and VNAV to work you must program the FMC entirely and properly. It is not just flipping up or pushing the MCP buttons for the systems to work and the aircraft control speed, vertical and lateral navigation on its own. All the programming on the FMC needs to be done and arming/engaging each system in a timely manner is also required. congrats on your achievement, be adviced (on your latest posts) you are testing, attaching videos and images over a 737-800NG aircraft that has nothing to do with the IXEG 737-300CL these support forums are for. So i would presume you will not receive support from the developers for a product is not from them. I would suggest you always do the testing and content sharing based on the ixeg 737-300 aircraft when asking for support here

In the last 2 videos i have seen there are a number of issues. -You are at high altitudes flying very slow, even slower than minimal clean flap speed. -Your FDs and A/T systems are completely off. The aircraft will be unable to control speed, vertical and lateral navigation under this scenario. What i just observed is the plane basically falling from the sky, impossible to maneuver. I would like to know how you put the aircraft in that condition in the first place.

if trim goes all the way up on its own, the most common cause would be you may have some hardware assigned to trim axis in xplane. Please double check is there any way you can record a full video starting when you load the aircraft, to see all configurations you perform, etc. until you get airborne and the aircraft comes crazy to fully understand what may be happening?

Is this on purpose or missing? I do fly VR but just playing around with the mouse noticed the V/S WHEEL does not offer scroll wheel support as all other dials, knobs, etc. does.

read here

the developers are aware already

The glareshield tip ends (anti reflection tips), as noted on the attached pictures, look solid as expected when looking at them from one side, but they are totally transparent when looking at them from the other way around. i.e. if sitting on the on the captian's seat and looking to the left glareshiled end tip, it will look solid gray. But if you are looking from the captain's side to the right glareshield end tip it will be transparent. note: my english is far from brilliant, hope to be clear enough on the issue.

When you report a potential bug, or wrong behavior, you should always attach evidence of the aircraft on its own (despite the saab, boeing, or whatever payware or freeware), otherwise the support guys may be chasing an external aircraft application/plugin issue. To your question: is it normal the aircraft requires full trim up during most phases of flight, the answer is no. I am customer of this aircraft too, the balance and weight, trim works normal to me. So what then? -The logs may tell if anything wrong. Please attach them when possible. -Attaching the real aircraft pictures will show the developers what the aircraft display are saying, despite the third party app. -Using xplane weight & balance menu is limited and tricky, can lead to weight & balance issues easily. You may consider a third party app for managing the aircraft weight & balance, among other very nice features it provides

you may consider this third party app for weight and balance, very nice! http://forums.x-pilot.com/forums/topic/6873-igodispatch-for-saab-340a/

In your video you seem to play with x-camera and ixeg menu. But what about the plugin "simcoders - headshake" plugin you have installed seen at 00:43?

you may also consider installing a free xplane plugin (there are several) for having progressive braking while pushing and holding a key/button instead of the on/off braking behavior by having no pedals hardware.

just logged in and the links is still there. Maybe you were not on the download section https://forum.thresholdx.net/topic/483-ixeg-737-300/

Despite IXEG making their 733 VR compatible (i am awaiting for it too), you can already enjoy the 733CL from IXEG on VR by installing the free mod below. It will make the aircraft VR compatible. I am using it for more than a year already with no single issue. https://forum.thresholdx.net/topic/437-ixeg-737-300-simvrlabs-mod/

you need to put a folder (not file, folder) exemption on the windows defender for the entire /xplane 11/, this will cure the problems.

Seems weird to me the idea of using xplane maps having the aircraft cockpit, but... Pulled out some hairs until figured it out, go to xplane map, zoom in a bit, then clic over the ILS on the map

I am using the 737-300 almost daily, now running on XP11.50b4 vulkan enabled. Not a single issue with ILS and/or any other system. For testing purposes, just loaded the aircraft at LEIB RW24, tuned both NAV 1&2 radios to 109.5 on the pedestal and both worked with no problem! note: since this is custom coded simulation (not a default xplane aircraft), i am unsure if you can tune the radios by using default xplane map. You should try using the aircraft systems. If it still doesn't work, maybe a plugin, script or external radio hardware interfering?

Sorry i do not understand what the pictures shows? what is the problem here? What you mean it did not take it? In the second picture the aircraft is refusing to descent because the MCP ALT was not configured to a lower altitude by the time the aircraft had to start descending. MCP ALT acts like a fence, for climbing and for descending. If you are flying FL300 and you want the aircraft to start descending at TOD, the MCP ALT must be configured to a lower altitude before reaching TOD or the FMC will alert RESET MCP ALT as on your picture and the aircraft will continue FL300 because it can not violate MCP ALT note: MCP ALT is a safety fence, so the aircraft does not move automatically no matter what VNAV has pre-configured. On real life an aircraft changing altitude up or down inadvertedly is a ticket to an accident due to traffic crossing above and/or below.

I was on a training session on a level-d sim, ohh this comment pulled back my memories. I was having a very hard time trying to keep the nose in a leveled path during a 45 manual ils interception, the instructor told me disengage A/T while handflying, A/T is cheating you . That cured all my problems The pitch moment of a/t thrust kicking in is a real nightmare. I have noticed in all Boeing approaches (not including bad weather approaches here) a/t goes off by the time you take handflying as discussed above, but on Airbus (by seeing lot of footage) seems they rely on a/t until they do retard the levers for touchdown Is my observation correct? if so, why the difference?

Go to x-aviation.com -> my account->login->within your orders list you have the download links. It will install latest version available 2000ft but at what distance? maybe you were too close to the airport and the glideslope below you already. You must intercept from below if you can share a screen capture or video we can be sure what is going on known bug, nothing to worry What you mean by, "there are a a few?". Not all the waypoints have populated speeding/height on the legs page? This is a good indication you did not fill up all required performance data on the corresponding pages. note: the FMC will compute/populate speeding/height predictions automatically to all waypoints in the flight plan once all required performance data is entered properly for it to calculate a valid vertical profile. The ones having speed and/or alt restrictions are due to being hardcoded on the SID/STAR procedures you selected on the DEP/ARR. hope this helps

No FMOD/FMC development is expected on the upcoming patch, they split development in 2 branches to release the converted 3D aircraft to XP11 standards + tweaked flight model and no longer delay due to the extensive coding requirements for FMOD/FMC features. note: the answers you are looking for are below, pay attention to the last 2 posts specially were Tom explains they split development in 2 branches not to delay everything awaiting for the FMC/FMOD large coding requirements.

yes you can General tips: -set your nav displays to VOR mode -use VORLOC mode on the MCP to track a VOR radial for lateral navigation -use FLCH or V/S for climbing/descending. FLCH would be a better option for climb not to stall when trying to reach your cuize altitude. -You set VOR frequencies on the pedestal, you set the COURSE on the glareshield If you are not familiar with the 737-300CL systems, you may search a VOR to VOR navigation example on youtube, there are many available.

can you record/upload a video and share the youtube link? At least several screen captures before the aircraft is approaching the G/S glideslope and after to see what modes are engaged and what the system is telling? In order for the ILS to operate, check: -The ILS freq. is tuned -The CRC (course) is set to corresponding heading -Make sure you are not intercepting wrong ILS side in those airports sharing frequencies. What airport/runway you are trying? -is the LOCalizer being captured but not the G/S? or both? -A/P should be engaged and not in CWSP mode to capture. It will be really useful having a video or a few screen captures so see what is going on, because there are a number of things o check.