Splash

I was using "sim/cockpit2/autopilot/vvi_dial_fpm" which works fine with standard Xplane aircraft, unfortunately like you said, IXEG uses an internal dataref. FYI: The interface documentation is out of date. The command "ixeg/733/autopilot/TOGA" has been removed from latest version but is still in the documentation.

Oh, ... I think I understand the issue here ... anything with suffix _act mean actuator position ... not the actual MCP A/P value ... Okay, so I'll use the Xplane's dataref for Course/hdg/alt/speed. But what about V/S? How do I set this value? Xplane's dataref sim/cockpit2/autopilot/vvi_dial_fpm is ignored and you don't seem to have a dataref for it. Please advise.

All, I have installed the ixeg 737 and trying to interface my MCP with it. What I noticed is that ixeg published dataref values (looking through dataref inspector) are different from what actually is displayed on the MCP, Ex: ixeg/733/MCP/mcp_cplt_course_act ixeg/733/MCP/mcp_plt_course_act This is also true for other ixeg datarefs such as heading, V/S. What's going on here? As a side point, the values in Xplane's standard datarefs match what's displayed on the MCP: sim/cockpit2/radios/actuators/nav1_obs_deg_mag_pilot sim/cockpit2/radios/actuators/nav2_obs_deg_mag_pilot Please advise.

site closed for maintenance. when you try to access the links.

Carlos, I am afraid, that's is probably all you can squeeze out of the hardware. The CRJ was developed for high-end systems, because of systems the aircraft has to offer which in turn affects the frame rate., there's unfortunately no default basic systems from X-Plane for the CRJ. My suggestion to you is turn you video down and start increasing sliders that are easy on the video card, the anti-aliasing and pixel shading is more demanding. You're looking to see where your video card tops out. In regards to the CPU overclocking will definitely help if you can.

Very true, exactly how the CRJ behaved on my system. In other words, the statements were quite accurate, doesn't get more accurate than that. In regards to improve your performance do what Javier suggested video card wise. I am affraid but CPU-wise if you are having problems there's not much you can do but over'clock and even then depending on the CPU you may have still lag.

Hehe, it is a fast jet why not? j/k Nah, was more stress testing the aircraft making sure instruments respond correctly but in a real situation for example if have damage to the aircraft and the aircraft plumets it may do out-of-control rolls. You still want to retain orientation if you are in the clouds or is dark outside (night) so you can try to recover aircraft.

I have discovered perhaps something obvious: on the PFD, the artificial horizon works fine until you do cray banks over 45 degrees. What happens the artificial horizon is stuck at 45 deg., ie. does not correctly indicate the roll of the aircraft correctly. Best to reproduce is to take off and then start doing rolls, 360 deg and observe the artificial horizon in PFD, you will note this effect. This is huge problem when flying in clouds and you rely on artificial horizon. System: Win 7 64 bit ATI 5870 1GB i7 920 ~ 3.9 GHZ 6GB RAM

I am not going to take sides but here's my experience in the Microsoft Flight Sim from some vendors: After a problem was discovered, the customer service stated they will have a fix for it. After years, no fix. You send email, you get same false promise again! Therefore, I would like to commend you guys for jumping on the problems and turnning around issues so fast. Your hard work is greatly appreciated. FYI: Customer Service differs from software vendor to software vendor (I know I worked already for 3 different companies). In all my circumstances as a development shop we did not notify any of the customers of the updates, -the updates were simply published publicly on our product support page and if the customer had a problem he would send a support email and we would direct the customer to the page with the update or release new update.

Woa, very interesting. Thanks for sharing.

That's a first. How can you bring all the momentum to stop without Rev. thrust? You will burn those breaks to the ground especially on larger jets.

Working on a virtual joystick, but most likely I will just write a device driver.

My findings were based on stress tests, if I do casual landing it will work probably better. Nevertheless, 90-95% is not 100% for such core functionality. I will wait for Phil's response on this matter.

Nice! Great idea for my new system.

All, If you run the CRJ on 3 monitors (my res. 3840 x 1024) and notice a major hit on frame rates here's what you can try that virtually eliminated the problem (or minimized it): Under rendering options: 1. Turn down your anti-alias. You have to play around and see what works best for you since each video card will top-out at different settings. 2. Using pixel shaders also will drop down your frame rate but not as bad as anti-aliasing. I left my pixel shader on (lost only 10-15 fps). My Setup: i7 920 Overclocked ~3.9 GHz ATI 5870 6 GB RAM If you running at even higher res. it will stress out your video card even more and if your card tops out you will not be able to play because of real lag. The ATI cards are high res cards I am not sure if the GeForce cards handle high res. well.

I would like to add further diagnosis on the problem with reverse thrust: I experience very same behaviour, the rev. thrust does not come on, instead forward thrust comes on. I actually do not use a joystick, instead I have a custom build throttle device. The throttle device interfaces with X-Plane via custom writen plugin writen by me. When a lever is moved forward, my software sends the position of the lever to the sim (a value between 0%-100%, 0.0f - 100.0f using 'sim/flightmodel/engine/ENGN_thro' data ref). During tests I have discovered (I trace all values writen to X-Plane into a console) that even if the lever is at 0% (absolute zero - 0.0f) the reverse thrust does not engage. I've been doing various test cases: full->idle, mid->idle, 20%->idle and the problem is intermittent unforunately. Majority of times it actually works but there's times when it doesn't (I would say 85% success rate that it behaves correctly, 15% it doesn't). If you need further tests or would like a live test I can record vid for ya. If you any questions feel free to contact me. I have also noticed that the animation of the levers is a bit choppy - I am not sure if this will help you diagnose the problem better. My System: i7 920 ~ 3.9 GHZ 6 GB RAM ATI 5870 Kind Regards, Luke

As has already been mentioned, the reason Nova is seeing the reaction from the aircraft that he sees is because of the stated reasons, and would be seen in real life as well. From what I gather, Nova was attributing the issue to product error, when in reality it is "pilot" error. Fair enough, so I take it the aircraft behaves correctly in that very situation.

Oh, one more thing: Thanks for the great aircraft Japo and Phil and anyone who supported you guys. The fact that you guys accomplished something like this is truly amazing.

If I may add to this post ... The goal of the aircraft should be to perform as close to the real one as possible. I think what Nova was trying to say is that real aircraft would handle this differently regardless of crazy pilot input and control. Based on software operation the software should preform to its outlined requirements regardless of user mistakes (ex: user accomplishes a use case out of sequence or enters data incorrectly, etc.) - that is quite common actually. Applying this rule holds true for software that controls an airliner, there's logic to handle various circumstances and alert pilots to mistakes. The point is, the simulated system should respond as close as to the real aircraft systems and behaviour. I am not a CRJ pilot so it would be nice to know what happens if you come in hot into a turn. Therefore, please report the problems to Japo and Phil and I am sure they will kindly resolve these problems if they are truly bugs. I am sure they want their aircraft to be great and they will fix any problems that have been discovered.