Printable View
The previous version worked so, but B46 didn't read previous ACcontrols.cfg backup file, so I configured controls from the beginning and suspecting the brakes I increased the neutral zone for both brakes, but nothing happened. Anyway, thanks Michael.:(Quote:
Originally Posted by Firefly77
Hi Leonidas,
You can use your previous AControls.cfg and JoySW.cfg backup files.
1 - Save what you just made with your actual files (it's safer... ;)).
2 - Put your previous files in place of them in FMGS.
3 - Run FMGS_Config.exe, and click on "Save configuration" without change anything.
Now this should work because of a new format of these files.
So, maybe you'll have to correct your axis (See Installation Guide Ch4.2) and error margin values for each position.
Regards,
Michel
Hi JL, I have a red Flag with "LOC" on my ISIS and it is not disappearing !? Is that correct ? Thanks and best regards
Michael
[QUOTE = Firefly77; 164846] Hallo JL, ich habe eine rote Flagge mit "LOC" auf meinem ISIS und es verschwindet nicht!? Ist das richtig ? Danke und viele Grüße
Michael [/ QUOTE]
....and the Baro have constant 1013
Have done it already, but got error message when application run for the first time, so I configured control fro the biginning.Quote:
Originally Posted by Mitch95
PS. B46 fresh installation, not updated.
It should only affect the aircraft when the FMGS soft is running.Quote:
Originally Posted by dcutugno
Quote:
Originally Posted by Busdriver65
....and the Baro have constant 1013[/QUOTE]
LOC flag: I need to check. It probably appears if an ILS is tuned but not in receiving range?
Baro setting: on soft startup it will always be 1013. The ISIS has its own encoder to change the setting, it is not linked to any of the EFIS controls.
Leonidas, check in your appdate\roaming folder the P3D DLL.XML.
If it does not have the simpatch.dll installed in it, do it manually (check posts number 45 and 51 in this thread).
The double entries in addon menu is not a big problem.
Have you tried disabling simpatcher.dll in your DLL.XML file?
You will not lose much for now, and it will help find out where your issue comes from.
FSUIPC is able (throught LUA plugins) to do equivalent hack into P3D to fix the ground friction. It could be here that you have a conflict.
If disabling simpatcher.dll fixes your issue, try then to re-enable it but disable FSUIPC (it is also done in the DLL.XML file).
First, thank you very much JL for this great update. I have simpatcher installed and the plane flies really nice and smooth, also no more pitch up and down on the approach.
However, in my case there is a problem with the ND. When during a flight I get a shortcut (DIRECT TO), the plane will fly to the specified waypoint, but the ND will not update the route. This is also the case if I have to change the landing Rwy and/or STAR/TRANSITION - the route is not updated on the ND. In the MCDU, everything is correct and the plane will fly the new route. This was not an issue with the previous versions.
Any idea what could cause the problem?
Best regards,
Isak