Jump to content
Joe Park

LFRS & FSLABS A320X

Recommended Posts

Hi Guys

I wondered if you could be of assistance. I have an issue with LFRS and FSLABS A320X in P3d v4.1. 

The issue involves the flight controls of the Airbus at the Airport, Departure and Arrival up 300 feet Altitude, the ailerons flutter excessively causing the aircraft to roll right and left in a jittery manor, above 300 ft and out of the airport scenery area flight controls return to normal.

I have been in extensive discussion with FSLABS developers and tested various fixes but to no avail.

It only happens at Nantes, I have uninstalled the scenery back to default and the issue  disappears and the aircraft operates normally but once I reinstall LFRS we are back to the conflict with the Airbus A320.

I have tried various options within the configurator, eg: disabled Dynamic Lighting, 3D Grass, lowered the scenery, unchecked the animations and disabled SODE  but made no difference!

 

May I have your thoughts how we proceed forward to try and resolve this issue?

 

Regards

 

Joe  

 

Share this post


Link to post
Share on other sites

Hi Joe,

This is indeed a really weird issue. To be honest, I don't know what part of the scenery could cause such strange behaviour with the FSLABS A320 (especially because we have not added anything in the air around the airport). I don't own this aircraft, so I can't try to replicate the issue. I would love to hear from other FSLABS A320 users to know if they get the same issue at Nantes.
There might be something which could help, but it is of course just a though: if you are using a mesh resolution setting of 1 meter, I have know that in very rare cases it can sometimes have an impact on your aircraft right before landing or after take-off. I experienced it a few times on different add-on airports, but I don't know the cause. You can try to use a mesh resolution of 5 meters to see if there is any improvement.

If I get any other idea I will of course let you know.

Best regards,
Thomas

Share this post


Link to post
Share on other sites

Hi Thomas

 

I did what you suggested but to no avail, still have the issue.  It seems that something is conflicting between the aircraft control surfaces and the scenery. Hoping for a imaginative solution :D

 

regards 

 

Joe

Share this post


Link to post
Share on other sites

Hello

I just purchased this scenery and I use the FSLabs A320 almost exclusively. I too have the same issue with controlling the plane when landing on this airport. The ailerons seem to be somehow affected and cause the aircraft to slightly bank left or right when passing below 250-300 ft, but are terribly difficult to override causing the plane to veer off the centreline before touchdown...

My install is vanilla P3D V4.1 apart from your LFRS scenery. I've got no issue in others default airports (don't have an issue with the default scenery of Nantes neither)

It's a shame as I bought this scenery to use it with the airbus... Any new ideas on what could cause that problem ?

Merci d'avance

Share this post


Link to post
Share on other sites

Thomas, 

J'ai a nouveau fait des essais en tentant de changer la mesh resolution, ignorer les crashs dans le simu, sans ActiveSky, etc mais rien n'y fait... (Les avions par defaut n'ont pas ce probleme pour info)

Apres plusieurs approches a LFRS avec le 320 de FSLabs, j'ai constaté que le probleme se produisait passant precisement les 300 ft.

On voit un phenomene étrange qui limite et rend tres saccadés les mouvements du joystick dans le cockpit virtuel (confirmé par la page systeme "flight controls" qui ne montre quasiment aucun debattement des ailerons meme avec full stick a gauche ou a droite). Si on remet les gaz, passé 300 ft on reprend a nouveau le controle total du debattement des ailerons. En refaisant une seconde approche meme probleme passant les 300 ft.

Y'a t'il un module specifique activé avec l'aéroport ? Est-il possible de desactiver SODE temporairement ? (je n'ai pas vu comment)

 

Share this post


Link to post
Share on other sites

Bonjour, et merci pour vos tests.

Il est possible de désactiver SODE pour LFRS en retirant temporairement les fichiers JSD_LFRS_jetways.xml et JSD_LFRS_obj_DL.xml du dossier C:\ProgramData\12bPilot\SODE\xml . Il n'y a pas d'autre module activé à LFRS.

J'ai bien réfléchi à ce problème. Ce qui me perturbe est qu'il ne touche que l'A320 de FSLabs. J'ai fait énormément de vols de tests avant la mise en ligne avec différents avions autres que FSLabs (Carenado, PMDG, Aerosoft CRJ, etc.) et je n'ai jamais eu ce souci. C'est pourquoi je n'ai aucune idée de ce qu'il se passe. La seule possibilité aurait pu être un object de la scène placé par erreur à 300 pieds, mais j'ai vérifié et ce n'est pas le cas. Et surtout, je désactive les collisions sur tous mes objets scèniques, donc il n'y aurait pas eu de problème de toute façon. Le problème pourrait-il simplement venir du FSLabs lui-même?

Share this post


Link to post
Share on other sites

Bonjour

J'ai tenté d'enlever tous les fichiers LFRS du dossier SODE que vous m'avez indiqué et le probleme est toujours là, idem avec une désactivation complète de SODE...

Cela dit, apres avoir vu dans le menu SODE que ce dernier "cherchait" des jetways dans un rayon de 6.5 NM/12 KM j'ai voulu tester le probleme en dehors de ce rayon avec la fonction "slew" de P3D, en laissant l'avion l'avion au sol et le deplacant a travers champs. Et en effet a 6.6 NM du VOR NTS et au dela le probleme disparait, et a l'intérieur de ce rayon il revient. Cela peut peut etre aider ? Qu'est-ce qui aurait un rayon d'action horizontal de 6.5 NM et de 300 ft de haut dans la scene ? s'agit il du rayon d'action de SODE peut etre ?

J'ai comme l'impression que la fonctionnalité SODE fait conflit avec cet avion... meme si le desactiver n'entraine pas la disparition du probleme. Serait-il envisageable d'obtenir une version de la scene avec jetways statiques peut etre ? Si oui je serai pret a la tester avec cet avion. Ou bien cela représente trop de développement ?

A noter que je n'ai pas FSUIPC. Je ne sais pas si ça change quelque chose.

Question : doit-il y avoir une mention de SODE dans le dll.xml de P3D après installation de LFRS ? car je n'ai pas cette mention

Share this post


Link to post
Share on other sites

Thomas, apres un troubleshooting j'ai résolu le probleme, c'était bien lié a SODE, voici la solution en anglais pour les clients intéressés :

---------------------------------
Here's how I solved the problem :

To people using this airport with the FSLabs A320 and having aileron control problem below 300 ft landing at this airport : the problem is due to a potential bad installation of SODE during the installation of the airport. I could check that by looking at its log file (located by default in the programdata / 12bPilot / SODE / log folder). There were several warnings in the log ("WARN" in orange if you view it from the SODE software itself). As a result I suspect SODE was constantly making "calls" to something it couldn't find and that was interfering with the flight controls runtimes used by the FSLabs A320.

1) Deactivating SODE doesn't solve the problem by itself.

2) So I kept the scenery installed but I first uninstalled JetStream_Designs_LFRS_SODEobjects_P3D (basically LFRS jetways). Then uninstalled SODE 1.5.3 itself, in that order.

3) Then I reinstalled SODE 1.5.3 first, registered it for P3D, then JetStream_Designs_LFRS_SODEobjects_P3D (both located in the doc folder of the JetStream designs folder in your P3D). I went to the configurator and put the scenery back to default and the problem was solved. There's no warning in the SODE log file anymore neither.

------------------------------

Sinon la scene est superbe Thomas. J'attends avec impatience l'update du PAPI en 03 du coup :)

Share this post


Link to post
Share on other sites

Also of note is that SODE has been updated to version 1.6.0, and it seems the new version solves the problem I was describing before (see bold text below). From their website :

"In the past, SODE would just throw in all objects it found in a certain radius into the simulator. [...] larger projects with hundreds of SimObjects (jetways) could saturate the simulator’s SimConnect server and this would result in a stutter until all objects are loaded. Now, SODE injects its objects in chunks with small delays in between. This way, SimConnect and the sim remain responsive.
Also, another source of stuttering was eliminated when the simulator was not able to find the requested SimObject on your harddrive. A missing SimObject is not the fault of SODE, it is an issue coming from installers forgetting to install the SimObjects properly or uninstallers forgetting to remove the controlling xml file but correctly removing the SimObjects. Both cases lead to a controlling xml requesting to inject a SimObject that does not exist! The simulator is trying hard to find the requested SimObject and this results in massive stutters for each object requested!
In this version, SODE checks during initialization if each and every SimObject (i.e. the MDL file belonging to a SimTitle) is actually accessible on your disk! If the MDL file is not present, SODE will internally replace that with a “red cross” object to indicate the missing object(s) to the user. Now that the simulator is able to load a model anyway, the stutter will not occur!
Another mechanism to enhance performance is the addition of cutting-off injections when the user aircraft is above 18’000ft. Cruising above a heavy SODE jetway populated airport will not affect performance anymore."

Is this new version of SODE compatible with LFRS ?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×