XPlanePort

Edit: Sorry, just noticed reply from jfjoubert Hi Jim, Please check this and see if you can add X-Plane folder to the AVG exclusions: https://support.avg.com/SupportArticleView?l=en&urlname=Mac-AVG-AntiVirus-FAQ "How do I exclude files or folders from scanning in AVG AntiVirus or AVG Internet Security?" You can specify if you want certain files, folders, or servers to be excluded from AVG scans. To set up exceptions: 1. Click AVG AntiVirus or AVG Internet Security in your menu bar, then select Preferences... from the context menu. 2. Select the Exceptions tab. 3. Click a shield in the left panel to select it. 4. Click the lock in the bottom-left corner of the window, enter your system administrator credentials, and click OK to grant permission for the changes. 5. Click the + (plus) symbol to add a file, folder, or server to the exceptions list. 6. Navigate to the file or folder you want to exclude and click Open, or enter a server name and select the relevant service from the expandable menu, then click Add. Your exception is now configured. To remove an exception, select an item to highlight it, then click the - (minus) symbol.

Wow. I was already registered, but was not ClubMemeber. Clicked to "Join Club" and now I can download. Was not paying attention. Thank you!!! ))

Thank you for the link mmerelles. I was aware of this mod. When I became aware of the mod it was no longer available for download, so I was not able to get and use it. I am registered on the site and the actual link to the file is: https://forum.thresholdx.net/topic/483-ixeg-737-300/?ct=1588527998 Unfortunately, the file is no longer available for download.

Can’t wait for the 1.3 update. Many thanks to everyone involved. Question regarding VR: From Jan’s post above: “there definitely is a plan to get the plane VR-ready. I don´t know when that will happen, though” and “fully compatible with VR is definitely our goal” Is there a better idea where you are with the full VR support at this time? Will VR be fully supported (all the manipulators accessible with VR controller) be available with the 1.3 update, and if not, are you working on this for the near future release?

The Questions/Request is regarding airspeed (on PFD (under the speed tape)) .000 and TAT gauges (with “Use ‘steam gauge’ engine instruments) 00.0 readouts. The small issue (if at all) is not only affecting the IXEG 737, but also present in other X-Plane aircraft. I am referring to constantly (very fast) jumping of the values. The gauges are showing exactly what the X-Plane values (that are feeding the gauges) being generated by the sim are. So, here are my questions and request: 1) Do the weather values (airspeed (wind/pressure) .000 and (temperature) 00.0 in the real world change as quickly and as often as they are in X-Plane? 2) If the above is "Yes", are the aircraft gauges this sensitive to the outside changing conditions (wind/pressure (in this case I think wind only) and temperature)? If the answer to the first question is "No" (this is X-Plane issue) and the second question is "Yes", is it possible to adjust the gauge output values to not react to unrealistic X-Plane generated data (“speeds” and “aircraft atmosphere”), so the readouts are not so jumpy for the last digit in the gauges? Would you consider not to feed the X-Plane generated data directly to the gauges, but instead, read and predict (based on the craziness) what the value should be on average, and then input the values to the gauges (work around for the X-Plane issue). I hope you understand what I am referring to. P.S. I actually like the effect of the changing value on the main “steam” airspeed indicator. Thank you.

Hello everyone. Ben, Just in case you still looking for additional info regarding this bug. I am also getting the same error when starting X-Plane with Zibo737 and then changing to IXEG. Just tried to start with default Cessna. Switching from Cessna to IXEG, same crash (Loading IXEG first, works without problems): I am using the latest Gizmo from your Facebook page: Gizmo64 v18.02.12.240 Edit: Reloading the Current Aircraft from X-Plane Developer menu, reloads IXEG without crash. I am currently on my MAC laptop. Can try the same on my main windows PC if needed.

This is from XEnviro developer: "Andrey Sheybak October 3 at 9:32pm Some changes have been made to our Roadmap reflecting the current project status. One noticeable feature of 1.08 is a general windshield preciitation effect that works on any aircraft. As I continue working on the cloud shader my colleague Vasily is making important adjustments to the atmosphere lighting and sky colors. Some issues with blending, haze and shadows will probably go through 1.08 and 1.09 until I finsh changing the atmophere model drawing order." So, there is hope!

Thank you!

The ninja fix that was done for X-Plane 11 addressed ground handling (maybe something else), but if you need to use the 1.1 in X-Plane 11 (like I do), you still need to do the two modifications for the plane using X-Plane 11s plane maker (as described in the post mentioned by Jah above). One to fix APU, and the second, to fix the engine problem shown in your video.

Thank you!!!

Thank you!

Thank you!

You are correct. On top of everything you mentioned, it is also easier to see the flex in the videos with winglets. Point of reference against background.

Most of the wing flax on 737-300 you can see during taxi, takeoff roll, rotation and in unstable air. This is the effect everyone here is talking about. You can clearly see this in the video:

I reported this sometime back. The problem was related to X-Plane 10 and not IXEG 737-300. At the time I filed X-Plane bug report. Looks like the bug is fixed in X-Plane 11. Running IXEG in X-Plane 11 and getting 359-000-001 on both sides.

Most likely you already know about this and maybe this is not the problem, but since this is X-Plane 11 with new install folder… Check if you have the new X-Plane 11 folder excluded from your Virus scan software and/or Windows defender.

X-Plane 11 Public Beta 2: No Gizmo error!

Are both of your NAV radios (left and right) tuned to the ILS frequency? Also, make sure your left and right course selectors are both set to the ILS heading.

Sure. I am ok with the answer. Wander what other users (that are Reading TFM and finding bugs) think. The post was not desperate call for help to waste your time, it was FYI for the team, to be aware of this, and for users to

Cameron, you are correct one many occasions..., but: If this is your logic, then what about us flying different routes and doing things with the plane that should not be done in the real world, trying to brake things and then provide the IXEG team with all the bugs, so they can be fixed? Following your logic, I think you should have provided us with set of instructions on what one should do or not do with the plane, to avoid all the gizmo crashes and all the other problems (Provide us with all the routes, button clicks, etc., that beta testers did.) Anyway, I love the product and the team (as previously stated) and have no problems waiting for the OS to be GM and IXEG providing the fix and all the other fixes and improvements. But, this is not the first time I see you attack others who are trying to help. I know, it’s your baby you are trying to protect…

And this is what I meant. I am sorry for starting this topic. It was only meant to provide developers with information and to give me an advice to fix this ((ONLY if there is a very simple way for me to fix this (taking into account the software/hardware configuration provided))). The topic was not meant to start a lecture on Beta software and its dangers. Sorry and thanks everyone for your help.

I would say it is Not a good idea, if the Web Driver i use (also Beta ) was not specifically made for the Sierra Beta. I did try with default Sierra video drivers, same result. I am ok with this not working on my test system (running Beta OS, Beta Driver, Beta X-Plane: The perfect Beta! ).

Thank you Cameron. Not a problem. I asked the entire team, hopping that person with Gizmo knowledge (Ben Russell) will take a note and reply with a suggestion (if any), but I guess you answer for everyone (which is ok as well).

Not a problem. Not asking to support your products on untested (Beta) OS. This is why the disclaimer: "IXEG Team, this is for your information only (I purposely use Betas to discover problems)" So, this is just an FYI (since I came across this). Just trying to help.