Jump to content
The simFlight Network Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


Biggles2010 last won the day on January 29

Biggles2010 had the most liked content!

1 Follower

Profile Information

  • Gender
  • Location
    Suffolk UK

Recent Profile Visitors

841 profile views

Biggles2010's Achievements


Newbie (1/14)

  • Dedicated Rare
  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges



  1. Sorry for delayed reply, been away for a couple of days. The cockpit is home built using proprietary buttons and switches and Leo Bodnar interface cards. Relatively low cost using mdf board and plywood for most of construction. Total cost was about £700 plus monitors and fairly high end pc. Flying controls also home built. Main thing there is to use good size axis shafts and bearings and industrial grade potentiometers or hall effect sensors. The whole project was fairly straightforward, although I had about fifty years of building model aeroplanes and other stuff before I started the sim. The forum has limits for images, but I've attached a few pics of the yoke and throttles. If you are going to start building, let me know and I can provide a lot more details. I was restricted for space so I made a couple of changes to the MIP for easier single handed operation, but everything works as intended.
  2. You were pretty quick getting that checked out. I agree it would not be so convenient for many users, but having the CDU always available, I just select the NAV page and rotate the knob. As I said I found it by accident when I was setting up the cockpit and at first thought I had made a wrong assignment until I worked out what was happening.
  3. It's possible using mouse macros and very simple, but the way to do it is totally obscure and something I found by accident when building my cockpit some years ago. I use a touchscreen for the MCDU with 2 rotary controls just below it to set frequencies. These are mapped to the double rotary on the MCDU popup using FSUIPC mouse macros with one rotary for full numbers and the other for the decimals, each rotary giving increase and decrease. Now for the obscure bit. With the RADIO page on the MCDU they control the frequencies according to the LSK selected. When the NAV page is selected on the MCDU I discovered the rotary for the whole numbers now controls the map range, up and down. Don't ask me why, but it works. Edit: I should add that the rotaries I used operate like switches, not like a continuous axis control.
  4. Yes, it's rather a shame it's all gone very quiet lately. I use the E195 exclusively and have spent a lot of time playing with config settings for a better rotation. The two issues for me were the reluctance to unstick at Vr, requiring too much positive trim to achieve rotation, followed by excess pitch up once airborne as result of higher trim setting. Recently I tried a different approach, looking at the contact points. I reasoned that moving the contact points for the mainwheels forward might help. Bingo! In the aircraft config the standard settings are point.1 = 1, -9.0, -9.0, -11.75, 2300.0, etc. point.2 = 1, -9.0, 9.0, -11.75, 2300.0,etc. My modified settings are point.1 = 1, -7.0, -9.0, -11.75, 2300.0, etc. point.2 = 1, -7.0, 9.0, -11.75, 2300.0, etc. This change has no effect on visual appearance. It simply makes the aircraft more willing to rotate at more realistic (lower) trim settings. Where previously it required up to +5.0, I was able to reduce takeoff trim to +2.0 with a smoother rotation and better transition to climbout. I have not found any adverse effects from this change. Usual disclaimer - make a backup of config before editing. Once off the ground the contact points have no effect on flight dynamics, but the lower trim setting avoids the excessive nose up pitch change after lift off. Landing characteristics are unchanged, but it seems to have a slight benefit of allowing the nosewheel to be lowered more slowly.
  5. If the controls you wish to use are recognised by FSUIPC, then it is very easy. Just create mouse macros for the FPA and Vertical Speed functions and assign them to the controls. All the instructions are in the FSUIPC documentation.
  6. Trial and error. CofG modelling and aircraft dynamics are not what they could be. Varies between models, but trim settings are likely to be quite different to the real aircraft.
  7. In the course of trying some things for another poster, it highlighted 3 seperate issues. 1. Shutting down the APU brings up immediate shutting down message on Eicas, but then nothing happens for 45-50 seconds. Only after this long delay does the APU start to run down. On previous versions It reacted much more quickly, which seemed a more likely response. 2. After shutting down an engine in flight, it is not possible to restart it by any means. I'm not sure about the real Ejets, but most jets have the ability for a restart in the air, although it may be restricted by company SOPs. Could engine restart in the air be implimented? 3. Flying an assymetric approach in the v3 E195 could be called challenging. Even at very light weight, the minimum control speed with around 95% power on one side is in excess of 170 kts. On an approach, using a 20 kts increase in vref, it still runs out of rudder with even small power adjustments. This was with the rudder scalar increased to 1.2. I was flying manually, because the AP gave up trying to maintain directional control as the speed reduced. Modern airliners have pretty good assymetric performance, but this was more like a Gloster Meteor, renowned 70 years ago, for killing pilots trying to land after an engine failed. I know Feelthere did not design the v3 Ejets for single engine flying, but these characteristics are part of the overall flight dynamics, which could be better.
  8. I understood your original post and video. As I said, I tried yesterday using each of the scenarios you described. In each case the engines shut down on the engine stop switches. Trying an engine shutdown in the air was for my own interest to confirm it still worked. I just tried again - Cold and dark start, short flight, land, clean up. Then shut down engine 1, started APU and shut down engine 2. Both engines shut down normally. What controllers are you using? I don't see any mouse cursor on the stop switches in the video, so have you programmed some buttons or switches. Have you checked for any duplicated control assignments. You say the shutdown problem only occurs after a flight, so things to check first would be any assignments for things used specifically in flight, like spoiler, autobrake, landing gear and flaps etc. The throttles look OK because if they were not at idle for shutdown, the Eicas would show a warning.
  9. P3D 4.5 HF3 E195 v3 SP2 - engines shutting down normally after a flight. Engine Stop switches operate with or without pumps running. Tried in flight and engine stop switches operate to shut down, providing AT off and throttle at idle. HOWEVER - engine will not restart in the air under any circumstances. Throttle at Idle, I tried these options - Ign Overide/Auto, APU on/off, speeds from 160 to 240, gear up/down.
  10. I do not get the fps drops mentioned, so here are a few thoughts. Are the issues perhaps occurring with 4k screens, and very high graphics settings? What light settings are being used - Dynamic lighting on/off, HDR on/off, use of shader software, high resolution cloud textures etc. Using the E195 v3 SP2 and P3D 4.5 HF3, I've just tried again and get possibly 1 fps drop with either taxi lights or landing lights and less than 2 fps drop with both selected. Switching between 4X SSAA, my usual setting, and 4xMSAA made minimal difference. E175 produced similar results.
  11. That could also be the result of conflicting assignments. Do all the lights cause this effect, or just particular lights. When you turn the aircraft lights off, does the frame rate immediately recover? edit: Just tried all external light combinations on the runway, with little effect on fps. Compared with all lights off, I saw about 1 fps down with all lights on, except taxi lights, and up to 2 fps reduction with landing and taxi lights on together (with all other lights on). Tried default airport and FT Copenhagen with same effect. Also same with different cockpit views. Seems to suggest something else causing your fps drop.
  12. If you have a controller with available pushbuttons, it can be done using the paid version FSUIPC. You can use the mouse macro facility to identify and assign any of the working Ejet button functions to buttons on your controller. The later versions of P3D were changed to allow this process to work very effectively. You can add additional usb controllers or interfaces to allow more functions to be controlled this way.
  13. The radar is very hit and miss. It needs heavy precipitation to produce any return. I also use P3D 4.5 and AS 7410 and often have no radar response when I would expect one. Other occasions it seems to work reasonably well.
  14. I have no connection with FeelThere, but as a long time user of the E-Jets software I have spent a lot of time trying to assist you. This has been difficult because you would not accept there could be other causes of your problems. Your responses have always been confusing and often misleading. You now say that you have found a solution to your problem without even saying what it is, yet in this same post you say it still does not work. I am not clear if your problem is solved or not. I hope it is, but I feel like I have been chasing shadows and I do not see any point in doing that any more.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.