Hi,
I have the same issue.
cheers
Florian
Printable View
There as an update in the evening, please try it...
JL
Hi guys
[Who could help me? I can't see WXR.
1st PC: P3D, FMGS SERVER, Default shared folder WXR.
2nd PC both NDs, WXR setting= \\SERVER_NAME\WRX (I can access this manually)
Search for an airport with precipitation in AS16, today was SBCG somewhere in Brasil, so tilt degree is the only I can see on NDs during a litle flight there. There was 9 dat files in WXR folder 800KB each, but no prcpt image on NDs.
What is wrong? Thanks]
EDIT: It's OK adding write privileges to shared folder.
I have a 2015 Skalarki Pedestal with WxRadar panel, I can change gain and tilt with the Pots, but tilt gives one problem: While properly calibrated I can only turn the tilt down to 0 instead of -15 and so I mostly donīt see the precipitation on the ND. I can reach negative tilt values only via MCDU and then the precipitation display on the ND is present as it should be. Is that a problem of Skalarki profiler or can it be solved somewhere in JeeHell?
Has someone already solved the disconnect autothrust issue?
Have installed the latest skalarki profiler and assigned several release events.
The problem still occurs.
If someone has fixed this issue please tell us how.
Great job JL.
Only one question. I was assigned a Joystick button for the landing gear and now it does not work for me. Why can it happen?
If I out the FMGS it works.
Thank you!
The interface should work. If the skalarki controls do not work, then first thing is to check with Marcin, as usual with hardware issues.
Hi to all,
I have insert <<allowAFLOORinhibit=yes>> to x:\A320FMGS\FMGS Server\PERF\PA320\Aircraft.ini.
Deactivated <<Act as pushbutton>> and assigned only ATHR TAKEOVER for Action on state for Levers 1 and 2.
No assigment for Action on state:Off according to the skalarki JL_FMGS Profil.
I still cannot activate Auto thrust.
Does the problem still occur with someone or has it solved in the meantime? A feedback would be wonderful.
Best regards
Hi to all,
this morning i have a problem with the updater!
on every pc in my homecockpit the updater is coming up, when i download the version i can read from version 47.0. i install it with admin rights, i start the starter.exe and the updater comes up again to updat to version 47.0!
Anyone the same problem or arework for me?
Regards Peter
Yes, I can confirm this. Update software message continues even after the update has been made.
John
Hi John,
i have fixed my problem!
You have to look for the date of the A320FMGS_B47_0.ex file it must be the 23.03.2017. in my case the downloader did`t override the older once! Run the exe file again and you will see if it update, after this the updater come once again to update the PFD. In the whats new.txt you see then the following:
A320 Software Solution Beta 47
------------------------------
23/03/2017
What's new in B47.0:
----------
-Corrected PFD display
22/03/2017
What's new in B47.0:
----------
-Corrected wrong version being displayed
-Reworked PFD/ND EIS2 layout a tiny bit (to take up all visible area).
Now in my system i`m on the actual point.
Regards Peter
Ok, thanks I will try that.
John
Hi
The autobrake Decel is ok on Max position, No Decel on Med position and Decel is ok on low position only at the last second when airplane stop ??
Ridha
Jean Luc would it be possible to bump a "patch version" number each time you update the installer? I think this will solve a few misunderstandings and make it more consistent. Much like what semver.org suggests, a widely adopted software packaging/distributing naming scheme.
It could be like:
47.0.0->47.0.1 for fixing bugs, nothing else changes
47.0.0->47.1.0 for adding minor functionality that doesn't break anything and is backwards compatible safe
47.0.0->48.0.0 for adding major functionality that breaks/might break compatibility and/or requires some caution and/or advances the provided options a lot*
You're already doing this more or less, we just need the patch number too :)
*The last statement defers from the original semver proposal to be more consistent with how JH cycles are currently distributed
Hi all
Question to those of you who have already made a "distributed" installation.
Do I really need an installation of the FMGS-software on the visual pc or is it ok to just copy the Aircraft- and WXR-folder onto it and to do the necessery entries in the cfg-files like simobjects.cfg etc?
Cheers
Greg
First, thank you very much JL for this very nice update!
Everything seems to work nicely. However, in my case I am unable to get the weather radar to work. Here is my setup:
PC 1: Running FSX and Jeehell FMGS Server
PC 2: PFD, ND, E/WD, SD and Software FCU
PC 3: Capt. MCDU and Overhead interface (this PC is a Windows-Tablet)
PC 4: Active Sky 2016
I always install as an admin on every PC. I have shared the WXR-folder on PC 1 and I have mapped the correct folder on every client PC. I am able to read and write to that folder from every PC. Active Sky 2016 is working and is injecting the weather into FSX. I just installed the latest FMGS update and I am currently flying in severe rain with rain and thunder/lightning. I have also read the nice tutorial for setting up the network share and I couldnīt find that I had missed something.
No files are being written to the WXR-folder on PC 1. I have not installed Jeehell FMGS on PC 4 since it only runs Active Sky 2016.
When I turn on the WXR through the MCDU, the only thing that shows up on the ND is the tilt value of the radar. It varies depending on the pith attitude of the airplane. EGPWS is working and I can turn on and off Terrain on ND as I could before.
Any ideas?
Best regards,
Isak
Hi Isak - can you try running AS206 on the same computer as the visual computer and see if that helps. Regards.
With the simpatch module enabled the weather radar is now working! I had manually disabled the simpather because I was doing some flights with a small GA aircraft and FSX was always shutting down with an error. Now, with simpatcher re-enabled, I still get an error when shutting down FSX. But that is just a minor issue as long as the Jeehell FMGS suite works perfectly.
Thank you so much for your help!
Best regards,
Isak
Hi Jean Luc,
sorry for my bad english, but I have a problem since Beta 47.
In my Home Cockpit I use four Computers. On all Computers the software starts automatically via Autostart Folder. With a little tool I can start every software in the right order delayed in seconds.
On the PC running FSX and FMGS Server, the order for start is starter.exe, Skalarki profiler and then FSX.
This order is by the Situation that I use FSX in Full Screen mode. All Software must be startet bevor FSX is ready.
Since Beta 47, FSXConnect and HardwareConnect doesen't connect to FSX if it is fully loaded.
After FSX is fully loaded I must Close starter an reopen it. Do you made any changes?
Include Version B46 all works fine
Do you have any idear or solution for my problem?
Thanks Dieter
it should be the contrary, start my software AFTER FSX.
I am having some issues with simconnect, and I am trying to solve them. This may affect other parts of the simconnect connectivity...
I also have the same problem with P3D and B47 on shutdown. I always get a crash some several seconds after closing P3D (generally with P3D the main window disappears fast when closing it but the program runs in the background for a while until it goes). Maybe simpatcher's cleanup code is not realising resources on receiving the quit event.Quote:
I had manually disabled the simpather because [...] FSX was always shutting down with an error. Now, with simpatcher re-enabled, I still get an error when shutting down FSX. But that is just a minor issue as long as the Jeehell FMGS suite works perfectly.
I also some times get the same crash while starting P3D after the welcome screen that allows you to select aircraft, airport, etc. I have a default flight with jeehell pa320 loaded in a gate. If this startup crash happens once will keep happening until I change something (usually select another aircraft, another graphics profile, airport), even if it would be the same loaded on the default flight, just reselecting it will most of the times work. I even deleted my default flight and created another one just in case there was something wrong there but again with intermittent crashes on startup. I didn't bother confirming simpatcher is the culprit as it is relevantly a small nuance and I didn't see anyone else mention it before.
I had the Same problem with B47 and doing FSUIPC reinstall solved this for me .
i do it after all install because sometimes P3D dll.xml or simconnect have troubles after add-ons ..
Every time i had this i reinstall FSUIPC and all works fine ..
I don't use FSUIPC at all so my issue is not connected with it.
I also took a look in dll.xml just in case something was messed up there, nothing's wrong. I only have `as_connect`, an ActiveSky2016 dll and simpatcher.
I had the same problem since B46. In B46 I change the order in dll.xml for the loaded modules and it solved the Problem. In B47 it doesn't help.
Regards Dieter
Can someone help with the continuous flaps sound.
thanks
I don't have crash with JL e p3d 3.4
I did an extensive search, the issue was brought up by many , even in the French A320 FMGS but could not find the reply. I know it is there and was replied by Jeehell around 2 years ago.
Let's hope someone will come forward with an answer. Till then I will mute the flaps sound in sound.cfg.