Biggles2010
-
Posts
130 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Biggles2010
-
-
18 minutes ago, John Dowson said:
Then why not post in that topic, or at least provide a reference to it...
The details are somewhat different. Link below.
19 minutes ago, John Dowson said:No macro files are ever deleted by the installer (or uninstaller) - if they were deleted, something else must have done this. Maybe show me your InstallFSUIPC6.log file, as well as any uninstall log files (if available).
Immediately before the FSUIPC update, all macro related cockpit functions were working, using FSUIPC 6.1.0. Therefore the macro files must have been in place. Then immediately after the update, control functions had been lost and the macro files had gone. Between those points, nothing else was installed, uninstalled or changed by me
I've attached logs, but as you say, there's nothing obviously related to macros.
I have used FSUIPC in various versions for the last 20 years on many computers. However, I built this computer 2 years ago and made a new purchase of FSUIPC 6.0 which was installed in the recommended location in My Documents/ P3D4 addons and has remained there. I made a new installation of P3D4.3 in its own folder on the C drive. (note, there has never been a Modules folder on this computer). New mouse macros were created and all cockpit functions were set up again from scratch. I did not carry forward anything from previous versions of FSUIPC. I subsequently updated FSUIPC to 6.05 and then 6.10 and P3D was updated to 4.5 HF3. All without any problems.
Recently I installed P3D v5.3 on a seperate nvme D drive, retaining the existing P3Dv4 setup on C drive. The new P3d5 installation was tested and working, but without any cockpit controls because FSUIPC was not yet installed for it. At this point, the cockpit was still fully functional using the older P3D4 and FSUIPC 6.10 installation.
I then downloaded the latest update for FSUIPC which was 6.18 and nominated to install for both versions of P3D. It asked to uninstall the existing 6.10 version and I accepted. The install proceeded normally, into the same folder as previously. I then tried the cockpit in P3Dv4 and P3Dv5 and found most cockpit functions had been lost. Then as I had said previously, on checking the ini file all the macro related items were showing as Unknown and in the main FSUIPC folder the macros had disappeared.
While there is no instruction in the uninstall / reinstall process to remove macros, it appears to have triggered something which has caused that effect. I have no idea what that could be.
-
John/Pete
I thought this problem was just on my system, but I see there is a previous post on this same topic.
I run a home cockpit, previously with P3D4.5 Win 10 and FSUIPC 6.10 and around 200 functions programmed via mouse macros which have worked faultlessly. I decided to install P3D 5.3 on a seperate drive, while also retaining the original P3D4 installation. No problems with that, but I also updated FSUIPC to 6.18. I selected to apply it to P3D4 and P3D5.
Quote from install Guide:
"If you already have either FSUIPC5 or FSUIPC6 installed for P3Dv4 or P3Dv5 (or both), then the installer will first uninstall this/these installation(s). Only the files installed by the FSUIPC5/6 installer will be removed, and other files ( .INI and .KEY files, lua scripts, macro files, etc) will be preserved so that they can be re-used."
This was not the case. All macro files were deleted. The ini was preserved but with all the functions relying on macros showing as Unknown Macro. This had never happened before with any FSUIPC update. Fortunately I had a backup of most of the macro files, but this was a panic I could have done without.
Could you please have a look at the update functionality. It seems like something may have changed.
Thanks, John B.
-
On 10/12/2021 at 9:19 PM, justplanemad said:
(190) is either “all or nothing” with elevator input on takeoff. You need a lot of elevator to unstick it, then subsequently only very little elevator for the rotate…. otherwise it over-rotates.
Also, I’ve setup the pitch trim on my joystick, but if I hold it down for a few seconds - it jumps in 1.0 intervals (rather than 0.1)… so I easy to overtrim. In real aircraft trim cuts out at 3 secs which I’m used to.. but this happens less than 3 secs. I guess the logic holding trim down for a long time is same as holding the CTL button down to get big change.. which works great for speed, altitude knobs .. but unnecessary for trim.
I got around the takeoff trim problem in my home cockpit by a small change to the aircraft config file, which I had previously posted on this forum (see copy text below).
I have not experienced the trim switch issue because I used FSUIPC to assign the standard trim up/trim down commands to my yoke trim switch, which gives me realistic operation.
------------------------------------------------------
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.
------------------------------------------------------------
I always suggest making a copy of the original config file as a fallback before making changes.
-
2
-
-
1 hour ago, FeelThere said:
Please download it from our product's page.
As a long time user and supporter of the Ejets series I have often tried to help other users on this forum. Are we no longer welcome to do so?
Previous to this response from FeelThere, I had already responded and posted a direct link to the Ejets manual, taken from the FeelThere product page.
My post has been removed and the above reply, from FeelThere has been substituted, leaving the OP to do his own searching.
The OP is clearly not familiar and had already said he purchased from SimMarket, where the download page provides no information at all about accessing the manual.
Is there a problem posting a link?
-
On 5/22/2021 at 1:25 AM, TomD said:
I would love to see more pictures and where you picked up some of that hardware like the yoke and throttles? Or is that from a flight safety Procedures Trainer or something?
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
-
-
1 hour ago, TomD said:
Wow, that is quite the find. Nice! Worked for me as well. Not ideal, but for a workaround you could map a macro to bring up the NAV page then use macros on the rotary to change the map range. The radio function of the FMS radio is correct. I’ll have to double check, but I’m pretty sure the map functions (range and waypoint sequencing) are only adjustable on the CCD rotary in the plane.
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.
-
12 hours ago, raam123 said:
I also use Linda and FSUIPC to map buttons...
Couldn't find a way to set map range increase and decrease .... any idea how to blind it ?
10 hours ago, TomD said:I tried creating mouse macros with the map range. Unfortunately, I haven't been able to figure out a way to make this one work. If the rotary on the CCD worked to control map range like the real aircraft it would work. Maybe the developer could look at adding the actual CCD functions on the CCD itself in addition to controlling the MFDs with the mouse.
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.
-
Yes, it's rather a shame it's all gone very quiet lately.
5 hours ago, sags said:take-off trim settings (especially the E195) to mention one. Are these going to be released sometime soon?
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.
-
1
-
-
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.
-
2 hours ago, FeelThere Ariel said:
There are no failures simulated on the EMB at this point
Thanks Ariel, understood.
-
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.
-
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.
-
5 hours ago, Aviator_Kevin_HD said:
I didn't try to restart the engines in the air, I have to explain it, please also watch my video, When I do a normal flight and arrive at my parking position and want to shutdown the engines, nothing happens, the selectors are in the stop position but the engines are not spooling down. Then I did some tests, when I started up the plane and tried to shutdown the engines it worked, but after flying the engines won't spool down for some reason. Everytime after a full flight this happens, but when I do this without taking off and landing this work.
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.
-
12 hours ago, scoobflight said:
Need to see if anyone else is experiencing this. Anyone?
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.
-
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.
-
1 hour ago, sags said:
But why the big drop in frame rates?????
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.
-
7 hours ago, Zcloudman said:
Scoobflight, I'm having the same issue with ChasePlane. ChasePlane uses the center mouse button + Wheel to zoom in and out. It's much needed for ChasePlane. There is no other to zoom in ChasePlane with out the mouse center button. Is there a way in the Feelthere E-jet to set Mach/Speed and Barro/STD toggle push to something other than the mouse center button?
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.
-
On 1/29/2021 at 4:17 AM, theophile said:
Yes,thank you for the reply,I put in this topic because these people are saying that with these settings,my settings,they are getting weather returns.
But I cannot replicate this,unfortunately,and I have no idea why this is so.
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.
-
16 hours ago, Kylian Rogers said:
Moreover I would like to add that I tested it on PREPAR3D V4 and it still does not work! After all, if some software is not compatible with the feelthere, is that the problem with my pc? I think not ! I will never fly the EMB anymore if I must have a clean windows with nothing else. So found a solution to this problem, and I am at your disposal if you need any information.
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.
-
The recovery program should give you the original software that came with your computer. But your previous screenshot shows you still have many other programs installed that would not have come with your computer.
I suspect one of those additional programs is in conflict with your E-Jets installation.
-
I don't understand how you can have reinstalled Win 10. It looks like you may have done a Windows repair which is not the same thing.
A full reinstall means starting with a clean drive and only installing Win 10 and the programs you wish to test (P3D5 and E-Jets v3) plus essential things like Nvidia drivers.
Whatever you did has left all the other software in place, so if any part of it has even a minor corruption you just carry that forward to cause more problems.
The reason for starting with a fresh installation is to test your E-Jets software without any possible conflicts from other software. If it works correctly as I'm sure it would, then you reinstall all the other software item by item and keep checking at each stage. At some point you will probably find a program which causes a conflict. Then you have something specific to investigate.
-
No wonder this is going round in circles. I asked you this:
On 12/6/2020 at 9:44 PM, Biggles2010 said:So there is absolutely nothing else installed anywhere on your pc, even if not in use, apart from Win 10, P3D5 and E-Jets v3, plus I assume Nvidia drivers. I mean no programs on other drives and zero P3D addons.
Your response:
On 12/7/2020 at 10:24 PM, Kylian Rogers said:Yes I have made a full reinstall of windows, with only mozilla, P3D V5 and feelthere. I don't know were the problem come from but for me it's feelthere. For example TFDI had crash issues with some people like me. I hope that we will find a fix !!!!!
I don't see how this can be correct. Your latest post shows your pc looking nothing like a clean setup after reinstalling Win 10 and P3D.
Your Control Panel shows 63 installed programs plus 12 more in your additional list. Almost any of them could be causing a conflict.
It is very difficult to help when you do not provide accurate information.
-
As you have a fresh install, if you go to 'Control Panel' and select 'Uninstall or change a program', you should only have a few entries in that list. Can you take a screenshot and post it here. It might give some clue.
-
Sorry, I was confusing your card with the standard 2060. So, with your clean basic installation, is the problem still the original case of fps drops when you move your controls. or are there any other issues?
Updating deletes macros
in FSUIPC Support Pete Dowson Modules
Posted
I did as you suggested, but first went a stage further and uninstalled FSUIPC 6.18 and recreated the situation prior to my problem, with the 6.10 version installed into My Documents for P3D4 only, and then ran the 6.18 update, installing to the same folder to cover P3D4 and P3D5. All went perfectly with macros and config preserved.
I then reinstalled 6.18 again into C:\ FSUIPC and that also went as expected, with the relevant files preserved and then transferred to the new location.
My original problem remains unexplained, but it's obviously not due to any changes to FSUIPC which is once again running as reliably as ever. Thanks for your help and sorry to have taken up your time with this.
John B.