Leaderboard
Popular Content
Showing content with the highest reputation on 12/30/2016 in all areas
-
Yeah, there is a lot of life in the 737-300, we are nowhere finished with it, yet. I personally could see a -400 and -500 (they are just variants) as an expansion. Not looking further than that for now. Jan6 points
-
Fear not my friend I hardly get bored. I've been flying the 767 for a year now and don't get bored one bit. Rest assure the same will be with the 7332 points
-
If they would make (which I don't think) a B737-800, it wouldn't be an 'expansion'. The -800 is simply a completely different aircraft, at least system-wise. Almost everything would have to be modelled from scratch, so I guess we have to wait for another developer to make the NG (perhaps PMDG? ). Would be cool to see a -400 or -500 at some point though.2 points
-
2 points
-
Received this email today from Tanguy. Awesome photo, so I thought I'd share it (with permission) I'm a B737 pilot with more than 1500h on B737/300/400/500W and wanna congrat IXEG for the amazing product you created. Im Very impresed with the fidelity. Still some minor bugs and fix but its awesome. Attached is a pic for you guys. Kind Regards! Tanguy1 point
-
Hello Captains! I made a simple LUA-script for v-speed callouts. It includes callouts for 80 knots, V1, Vr, V2 (V2 is optional) and positiv rate / gear up. The script is tested on X-Plane 10.51 and X-Plane 11 on Windows 10. Feel free to leave a comment if you liked the script (or not) Requirement: - You will need FlyWithLua installed - http://forums.x-plane.org/index.php?/files/file/17468-flywithlua-for-xp9-and-xp10/ Installation: - Unzip the files in [X-Plane]\Resources\plugins\FlyWithLua\Scripts You should get a structure something like this. Settings:Edit the IXEG_vSpeed.lua for the settings. Set to true to enable "V2" callout and false to disable. true and false have to be written with lowercase letters.Enable_V2 = false Set to true to enable "Positive rate/Gear up" callout and false to disable. true and false have to be written with lowercase letters. EnablePosGearUp = true Sync the First Officers speedbugs with what you set on Captain side. Default = false. true and false have to be written with lowercase letters. SyncSpeedBugs = false Change "SoundLevel" to adjust volume for the callouts. Adjust between 0.10 min - 1.00 max (default 0.55) SoundLevel = 0.55 How to use: This is how I use the bugs. It may not be correct compared to real procedures. The required bugs you need to set for the call out to work is Bug_2 to V1 speed, Bug_3 to Vr speed, and set the MCP speed to V2 (if you use V2 callout). You can set the other bugs to whatever you prefere. Demonstration: Known bugs/limitations: - Speed bugs can only be set on Captains side. Credits: @xplana for his excellent voice for the callouts Changelog: v0.111- Made variables and datarefs unique to avoid conflicts with other lua scripts. v0.110 - Minor optimizing of the script. v0.109 - Added setting to sync the speed bugs on First Officers side with what you set on Captains side. v0.108 - Added setting to adjust volume for the callouts- Added setting to disable "Positive rate/Gear up" callout v0.107 - Speed bugs did not reset. Fixed v0.106 - Reseting speed bugs when loading script. To avoid callouts if you dont have set the bugs. - Some adjustment to the sounds. (not so much right panning). v0.105 - Changed the default for V2 callout to false (disabled) v0.104 - Fixed V1 callout when starting X-Plane/loading aircraft v0.103 - Fixed "Positive rate / Gear up" -callout when V2 is disabled v0.102- Added setting to disable V2 callout v0.101 - Fixed compability with X-Plane 10 v0.100 - inital version You can download the script here: http://forums.x-pilot.com/files/file/1029-ixeg-vspeeds-callouts/1 point
-
Hi everyone, we would like to give all of our loyal customers a short update on the work going on behind the scenes. As you are all aware, we are working on patch 1.1. It will include a number of additions and fixes to our 737, some of which we hinted at in our sneak peak thread: http://forums.x-pilot.com/forums/topic/11745-spot-whats-new-v11-spoiler-alert/ We are not quite ready yet to release the full list of features and fixes, especially since we want to make sure that we can actually include the items in question and also run a more thorough test on this patch than we had the time for on the last "hotfix" type patches. For the same reason we won´t commit to an ETA at this point. As we draw closer to release, I will update this post with more info on 1.1. We know it has been a very long time without updates and we thank you for your continuing support in spite of this! Happy landings, Jan1 point
-
1 point
-
well to be fair, there's still a lot of work to be done into the 733 so i doubt that their team will be able to start an another project. Thankfully, it seems they want everything to be perfect so one thing is sure, is that the 733 is heading towards perfection! so why bother with a 738 yet?1 point
-
Digital Gauges ... because most 737 Classic in Europe are fitted with them and I like 80s high-end electronics.1 point
-
Hello, Are you sure you set the bugs correctly ? Could you take a screenshot of the speed bugs after you have set them.1 point
-
Is it possible to have the automatic speed bug setting (when setting up the CDU) like it is without your script? Regards Robert1 point
-
1 point
-
1 point
-
IXEG 737 official status: We are currently working on v1.1 of the aircraft which will include: Systems and 3D updates pluss bugfixes. As it looks right now v1.1 will be for XP10. By long experience we know that new XP runs are buggy for quite some time after release - which means - that in the beginning of a new XP run it will often be difficult for us (and you) to determine what is an XP11 bug and what is a Gizmo or IXEG bug. So officially we will not support XP11 until after the release dust has settled a bit. Rushing into XP11 is not a good idea since we might break more than we fix. This *might* change if it turns out there are few problems and easy fixes. We'll see. As for the timeframe, it is very hard to say depends on alot of factors that IXEG does not control. But basically what needs to happen in the following order is; 1. X-Plane 11 related bugs needs to get sorted and get stabilized by Laminar (if needed) 2. Then Gizmo needs to get updated by XA (if needed) 3. Finally, IXEG needs to update the aircraft (if needed) So atm our time and focus here at IXEG is on v1.1 for XP 10 while monitoring whats going on in XP11 and making sure the others involved do their part Also from experience, it usually takes atleast a few months from first beta for a new run of XP default to run satisfactory to the user. From an aircraft developer point of view we need to remember that since XP10 was released a few years ago, aircraft in XP has become A LOT more advanced, meaning that there is likely more that needs to get updated from the developers side. So we are definitely talking months before everything is back to "normal" again. So if you are a 737CL addict and/or don't like "beta software", hang on to XP10 for a while for things to mature.1 point
-
1 point
-
1 point
-
Sorry. Some other Linux useless internet trolls ruined the party for everyone. Details here:-1 points