frumpy

Hi there, once in a while I boot up the IXEG and see how I do What I noticed with X-Plane 11.55, 737 v1.33, Geforce 4070 driver 3.27.0.120 and all plugins removed is that the instrument reflection is quite strong. It's been there sometimes, but other times it is not. I'd like to figure out why this is. Also happened on my old Radeon card. Independent of lighting direction, when I turn 360° on the ground there is no change. Perhaps I need to tone a file down or delete it? I'd go for full contrast. Any advice? Thanks, Olli IXEG B-737-300 Situation.sit edit: After flying some time, the fog lifted and I had clear instruments. When I returned to the airport, the milkystuff came back. I set weather to clear sky, but it did not have an influence.

Whats the speed of your internet?

I'm using Air Manager for interfacing. The default value of ...733/CDU/key_x is "-1". Clicking with the mouse within XP sets the dataref to "1", releasing it to "0" - while the CDU prints the character. I found sending just a "0" to the dataref via AM does a keypress, but with several characters. So there is no need to reset the dataref, setting a value of "0" to "0" is handled like a keypress. Sending "0" twice does the same as sending it once. It shows 2-5 characters, not reliably reproduceable.

Hi guys, as the title says, I am trying to do some interfacing. Using the dataref tool, I found that pressing a button within X-Plane sets the dataref from 0 to 1, releasing the button sets it back to 0. I can manually change the value of the dataref and this is working fine. However, when trying to do the same thing in LUA, I'll get several characters displayed on the CDU (like "AAAAA" instead of "A"). I see some people already interfaced the CDU for their private sim or as commercial software, but I wonder how this was done? Example code, which prints "BBBB" one second after clicking the "B" button: function b_pressed() xpl_dataref_write ("ixeg/733/FMC/cdu1_B", "FLOAT", 1) timer_start(1000,timer_b) end function timer_b() xpl_dataref_write ("ixeg/733/FMC/cdu1_B", "FLOAT", 0) sound_play(clicksound) print ("B pressed") end Can anyone help?

Good call on the programming issue, Tom! I do too program little stuff once in a while, even though it's only basic if-then-else variable computing, for me things and models of reality can cause quite some irritation if they get too complex (plus, there is no one else to check the code). After all, it's hard to create code 8 hours in a row. I am happy that you are still trying, I feel the plane is a bit of an underdog that did not receive all the praise it deserves.

Could you guys share your results? If I'd have the $$$$, I'd go for Brunner too.

Perhaps these links will add some confusion: :-) http://aerowinx.com/board/index.php?topic=4751.msg50540#msg50540 https://www.quora.com/How-much-force-is-needed-to-move-the-flight-controls-while-taking-off-in-Boeing-or-Airbus-aircraft https://assets.publishing.service.gov.uk/media/5ad6fc84ed915d32a65dbcd5/Boeing_737-8AS_EI-EBW_05-18.pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.430.6702&rep=rep1&type=pdf Judging from a 737 simulator, the controls are "quite heavy". Dont know if that helps, though..

I found it myself. This thread is very helpful: http://forums.x-pilot.com/forums/topic/11696-fmc-output/?tab=comments#comment-111966

Hi guys, I would like to interface the CDU. Checking the datarefs, I don't find any info on the displayed data, eg. the destination airport. However, there seems to be a clever way to interface this, as seen in this sim (which runs the IXEG): I wonder: how is this done?

I did it a long time ago, but now the interface has changed. It's more like plug&play now, while the code is harder to read, it can be all automated by the configurator: http://simvim.com/ardsimx/config.html In Air Manager the code for the gear-down-LED would look like this: -- LEDs // Gear gear_led = hw_led_add("ARDUINO_MEGA2560_A_D10", 0) -- define the pin which has the LED function gear_down_xp(position) -- name of function that controls the LED print(position) -- just for debugging if position[1] == 1 then -- this is FLOAT hw_led_set(gear_led, 1) -- turn LED on else hw_led_set(gear_led, 0) -- gear not out, turn LED off end end xpl_dataref_subscribe( "sim/flightmodel2/gear/deploy_ratio" , "FLOAT[10]" , gear_down_xp)

There are a few ways to do so, e.g. ARDsim is good & for free, an older one would be Teensy with the plugin. I'm using Air Manager, good support by a very friendly team, ongoing development, fits P3D too and best of all - you can develop your own instruments with it.

That's a point. Personally, I don't undertake this detail of planning. I check fuel, weight, CG and off I go. Study qualities, but consumer market. A sidenote: In PSX I saw graphically how a gradual increase in fuel shifted CG back and forth. Extremely detailled and exact with the numbers, it's got vulcanic ash and elms fire simulation too. Maybe that's what you are looking for.

How do you define "study-level"? Concerning the MTOW, 138,500 vs. 139,274lb: Would you notice the 700 pounds difference? I wouldn't. And that pretty much summarizes what this is all about: in a flightsim you'll have to make concessions. Even a $350 tagged PSX does have some (okay, very little) things that are not "real". I mean do you go in a level D sim and complain about the duration of g-load in certain situations? I think the bottom line is that the IXEG is one of the best (...) aircraft for XP. Don't you agree? Glas is still half empty? Why don't you look at the things that were done very good, rather than trying to find things you don't like?

That's great news, thank you very much!! That'll make a nice toy.

No, the encoder sends twice the signals that I need, thats why I use only every second signal. This way one click equals one degree in heading change. The thing is really that the HDG_bug_inc_90 command from the first post should only move by one degree, not 90 - then it would work like the course knob as you see on the video. I'll check Ben's recommendation tonight, however I think I would stil be bound to the time delay due to reading&writing the dataref. Olli