Check you do not have a default assignment in P3D controls for this button.Quote:
Originally Posted by capt_pero
Printable View
Check you do not have a default assignment in P3D controls for this button.Quote:
Originally Posted by capt_pero
Sorry. For sure - that was the issue. ELEV Trim Down was assigned to both buttons.Quote:
Originally Posted by jeehell
Happy easter!
Since installing B50.0 I have an issue when flying with STD pressure on a FL. I recognized it when flying online. Controllers tell me I´m on a wrong altitude and ask me, if I´m flying with local QNH. I have definitively turned "STD" and the correct FL in the FCU as well as in the PFD. My son, who also is controller in VATSIM network, checked it in Euroscope. We can reproduce it in every flight. I crosschecked it with the Jahn/Visser DC-3, and there all is o.k. It must be an issue of A320 FMGS to give a wrong altitude to the simulator. I have it in Prepare3Dv3.4 same as in Prepare3Dv4.2. Flying above transition the altitude for the FL (not the altitude for QNH) becomes correct, when I turn in the local QNH. This changes, when I am still below transition altitude or when I descend below transition level. Here the altitude with local QNH becomes correct.
Strange! Seems my A320 FMGS automatically changes to the FL above transition altitude while the local QNH is tuned in and therefore the altitude gets wrong when I turn to STD pressure. Turning to QNH 1013 leads to same result.
Anyone with same problem (caution: you will only recognize that when flying online!)? JL, do you have an idea?
Happy easter to all!
Hi!
The issue is described in the FMGS Installation Guide on page 44:
Setting the "Altimeter Temperature Effect" option to "no" should solve the problem.Quote:
Altimeter Temperature Effect : Basically, FS and P3D do not simulate an important
phenomenon : the effect of temperature on the altitude displayed on the altimeter. If it is
warmer than the ISA atmosphere, the altimeter underestimates the altitude; if it is colder,
he overestimates altitude.
The default "Altimeter Temperature Effect" option ("yes") takes this effect into account.
However, for those who fly online (IVAO, ...) the altitude of the aircraft will not be that
expected by the controller or other aircrafts ... The "Altimeter Temperature effect" option
allows you to disable this function by replacing “yes” by “no”.
Regards and happy Easter,
Isak
THX a lot, that did the job. RTFM...
Finally installed 50.0 yesterday and got the same „issue“ with the engine not starting (going to auto-crank)... I do not understand this behavior.
Is there an explanation for it?
But overall, thanks for your effort, JL!
Cheers,
Micha
hello guys:) anyone can give me installation manual? where is he?Quote:
Originally Posted by Beaufort
regards
fred
Hi Fred,
Installation Guide is in the package...
You've surely installed it, while installing B50.
It's the same for all JeeHell versions, all the official manuals can be found in your folder C:/A320FMGS... :
>>> Installation Guide,
>>> User Guide,
>>> Advanced User Guide.
"EN" for English version, "FR" for French version...
Regards,
Michel
One thing more :
If you want to read it before any installation, you just have to :
>>> run the installer (as an administrator),
>>> uncheck all the modules during installation : You will get all the manuals.
>>> Paste them in another folder.
>>> Then run the uninstaller "unins000.exe".
Regards,
Michel
...and of course, the manuals are updated with every new JeeHell version...
Michel
Hey Guys,
I do not know if I'm just too stupid, but somehow that does not work with the joystick over network.
Have RemoteJoy installed on a client machine. All right until then.
First question: How can I now configure the joystick on the client?
Then I start the server. The client PC connects to PFD ND and so on, and then a Windows error message comes on the client that A320 FMGS no longer works. The program is not executed properly due to an error ...
Before I installed the Remotejoy, everything worked.
I try also a fresh installation of FMGS.
Any Ideas?
Cheers
Florian
Hello Florian,
Your first question about configuration :
>>> On the client PC where ypour joystick is located, you only have to run RemoteJoyApp ("as an administrator" as for every JeeHell module).
>>> On the FMGS Server PC, you only have to run FMGS_Config : your joystick can now be detected and configured.
If not, check your antivirus/firewall which may "unappreciate" RemoteJoyApp...
About error after starting Server :
>>> What are the JeeHell modules running on the client PC, when the error occurs ?
>>> Be aware about FMGS_Server and RemoteJoyApp which can't work together on the same PC
Please have a look too, to Installation Guide chapter 4.1 (page 18) and 4.2 (page 22) about all this.
I made all this working, without any error...
Regards,
Michel
" Chapter 4.1 page 18"... lol.
Hey Mitch,
Thanks for your reply.
I actually stuck to everything. Antivir and firewall disabled and also tested. I even deleted the FSUIPC.ini.
The attempt on a second client to install brought exactly the same result.
It always seems to crash the hardware.exe on the clients as soon as they connect to the server and only after install the RemoteJoyApp.
@Jeehell: I have three crash files here, it would be help.
It´s Something like this
: <EventType>APPCRASH</EventType><Parameter0>HardwareConnect.exe</Parameter0><Parameter1>0.50.0.1</Parameter1><Parameter2>5aa6e6f6</Parameter2><Parameter3>StackHash_b0b3</Parameter3><Parameter4>0.0.0.0</Parameter4><Parameter5>00000000</Parameter5><Parameter6>c0000005</Parameter6><Parameter7>00000000</Parameter7
Mhm ok it seems to tun now, there was a wrong Ip-adress for the Server in the RemoteJoy.ini
:roll:
Thought it automatically picks up the ones specified in the installation routine.
Since a few days I am receiving an error message concerning the complexjoy.dll:
"Access violation at adress 05C996Ca in module 'ComplexJoy.dl'. Read of address C5B98530."
It came out of nothing... at least nothing, I am aware of.
I already made a clean reinstall of JL on the server pc and reconfigured the Joystick (use the Complex Joy option for my Saitek TQ). It was working then for a few days - now this message comes again...
Anyone with a clue?
//edit: could this be caused by the USB keyboard, that I plugged in and out again?
Best,
Michael
Hi,
Ok Joysticks over Network runs, perfectly. But I get on every client after connected to the Server the HardwareConnect.exe crash. I´d like to connect on one client a bit of SIOC Software and on the other Servos that works with Mobiflight and it uses FSUIPC. I think booth needs the HardwareConnect, right?
@ Jeehell Do you need the Crashlog files?
Cheers
Florian
Are you sure you did not install some modules which you do not need? some may crash if they don't find their related hardware
did run all the time with the same settings.
I am pretty sure, it's the changing USB hardware as usb Port adresses change then also, so I guess the original axis is not found then.
does this make sense?
how are you assuring, that usb assignments stay unchanged when plugging new hardware in or out?
I do not use an USB assignment but a GUID generated by windows. This guid could change if USB is messed around with. But on my computer I never had any undesired USB port change which would change the GUID...
Hi Jeehell,Quote:
Originally Posted by jeehell
Thanks for your reply.
To crosscheck this, today I completely uninstall FMGS (including deleting the folder) and reinstalled (off course without any modul except remotejoy) on one client. But unfortunately the hardware.exe still crashes as soon as they connect to the server. On ther Server runs the following modules.
SIOC (Korrys, Switches, etc)
FSUIPC (For PTT on IVAO Client and CameraViewPoint)
FDS (For MCDU)
Cockpitsonic with EHID(Radio F/O)
CockpitConncept (For genius Parts: Radio (CPT), Rudertrim, ACP, TCas, etc.)
King regards
Florian
Hi JL,
Quick question regarding AP PID. Is there any maximum flight control deflection that AP can command?
I’m modifying the OP MODE CLB/DES PID as I use my own 320 aerodynamic model.
Hi all
since today I have a issue with the idle state of my throttle (Skalarki), it does not show idle anymore in ECAM and when try to start the bus it does not speed up,all states like clb rev etc are shown on ecam. Can not taxi or move the plane with engines.
Calibrated a few times the controls but somehow there is a problem, also the flight control check on ecam is not moving, but in nd the white cross is moving when moving the side stick.
Someone an idea what to check to solve this issue?
Never had problems like this before. It si strange, when the bus is moving it is moving backwards....
Best regards
Stefan
check APFBW window if you have something selected in the dropdown list?
Hi Jeehell,Quote:
Originally Posted by romeow
referring to my post #39 I'd like to point again to the fact that in B50 STD (on PFD) doesn't blink when you pass (during descent) e.g. TL 60 although FL60 was entered on APPR page - and activated of course. Same with FL 70.
I think this true to original feature (as a warning) was implemented in earlier versions, wasn't it? Possible to "reactivate" it in the next update/version?
Regards
René
Hi JL
thank you for the quick reply. CFM is shown. I do not know what the problem was, I got the aircraft.cfg of a friend, but it did not solve the issue in the first row. I restarted all again and now it works. Don't ask me what setting this issue solved...
Kind regards
Stefan
Hello together,
i just crawled some threads, but i can´t find the answer, which was definitly given by Jean-Luc some time ago.
So, perhaps someone can help me with it. I want to change my configuration to reduce the load on the P3D-PC (i8700K@5GHz), so someone can tell me, which modules are the minimum requirements for the P3D-PC, when its set to client mode?
Server and all other modules shall be moved to the FMGS-PC (i3770K @3.5GHz), where also the complete Skalarkihardware is connected. There is lot of power left, which can be used instead of the visual-PC.
Best regards
Henrik
you have some info in the installation guide
Hey Jean-Luc,
thx for the info, i did the install as described, but time was running out at the evening. First test was not OK, but i think, it was only missing Simconnect files and correct setting in IO-Profiler from Skalarki.
I will report, when its done.
Regards Henrik
You can set it up so the visual computer (P3D) is independent to the FMGS PCQuote:
Originally Posted by Jerec
https://soarbywire.com/2017/02/17/ru...ne-simconnect/
Hello Henrik,
This is described ine the B50.0 Installation Guide...
>>> Chapter 3.3 + picture page 14,
>>> Chapter 4.1 from page 16 to 18,
>>> Chapter 4.3 about Simconnect.
Best regards,
Michel
And install Skalarki Profiler on P3D PC (Skalarki needs FSUIPC) and connect hardware on this PC.
Maybe it works on another PC through WideFs, but I think "the fewer network exchanges, the better" ;-)
Michel
Hello guys,
thank you very much for your tips and your help. I got it working now, only Master Sound and Intercom is running on the P3D-PC.
I also considered to move IO-Profiler to the P3D-PC, but this worked in the past very good on remote-PC.
One tip for all people having issues with USB. Always avoid to produce Hub-cascades, always connect an external hub to a direct port of the USB-Controller, not to an internal hub-port. You can perfectly check this with the USB Device Treeviewer, and reconnect to have an optimal result.
For example, the dongle of ImmersiveDisplay needs to be the first device on an controller, otherwise it will disconnect and reconnect again and again.
Best regards
Henrik
Hello. Anybody uses hardware from POLIDRANOGET? after installing JH B50. the driver of this software stop working sometimes, and i can not use modules( overhead; ECAMS; autobrakes, etc). Anybody uses hardware from this brand?
regards
Frederico
Can anyone pls advise how to fix hardwareconnect.exe crashing.
Have installed v50 twice with all correct software with same outcome.
Thanks
Michael
which hardware? are you sure you did not install hardware support for other vendors? install ONLY the required modules.Quote:
Originally Posted by bindook
Pc1 is running just fsx and pc2 is running skalarki, sioc card and fds card and all controls (which have been configured thru temote joy). So thats all im installing.
Something i have noticed is in the configure.exe is the box for "computer running fmgs server" will not stay checked on the fsx pc.
The configure.exe issue is not causing any hard crash. As long as you re-tick the correct boxes before clicking to validate, this is a non issue.
Regarding the hardware crash, try to remove the remote joy function at first (so remove the remotejoy.dll).
if it still crash, remove all the DLLs, then put them back one by one until you find the issue.