Hi,
can anybody tell me the offset (Jeehell) which I could use in my SIOC code to execute the same command as I'd use the EXT PWR item within FSX menu (in order to have EXT PWR AVAIL direct after starting SIOC).
Thanks!
Regards
René
Printable View
Hi,
can anybody tell me the offset (Jeehell) which I could use in my SIOC code to execute the same command as I'd use the EXT PWR item within FSX menu (in order to have EXT PWR AVAIL direct after starting SIOC).
Thanks!
Regards
René
Rene: Check on the website for offsets document (check my signature).
JL - APU startup page is fixed. There is a new bug now with the latest release -- the ELEC page activates and is a selected page throughout the whole pre-flight, flight, and landing procedure. No SYS warnings.
Hello Jeehell, today I updated again FMGS and SKALARKI Profiler.
ECAM LED issue is now soleved. I can confirm Hardware is now working again.
Comes to parkingbrake issue. As soon as I start the engines or APU, which means as soon as hydraulic power is available, something happens in FMGS occuring this issue.
1. engines and APU off, no braking action. release and set parking brake works.
2. hydraulic power is available, there is a braking action. set and release parking brake works. Now we have to press both brakes (Captain and FO side) to fixx this issue. After moving pedels both sides, there is no braking action anymore when releasing parking brake.
Now comes to NavData. still no SIDs shown. I found a bug in scenery.cfg, which I fixed. But still not working.
Here is may scenery.cfg
maybe there is still something wrong?Code:[Scenery]scenery.cfg=C:\ProgramData\Lockheed Martin\Prepar3D v2\scenery.cfg
FSfolder=C:\Games\Prepar3D v2.5
AerosoftPath=C:\Users\Prepar3D#Sim#PC\AppData\Roaming\JeeHellWare
ip=192.168.1.131
Best regards Marco
OmniAtlas Thanks! I've already got this list and tried $78EE with value 79. Didn't work but I'll try again. I think it shoul be this Offset.
Regards
René
MCDU panel "MCDU display problem please report issue." error.
@ALL : there is a little issue in the joystick system from windows (this affects only regular HID joysticks like logitech, sidewinder, or even probably joysticks using emulation like leo bodnar's). Unless any axis is moved after the FMGS initialization (and it's access to the joysticks readings in windows), it will see all axis in an undefined position, usually centered on the axis course.
This means that brakes will be seen as braking, even if the pedals are released.
I will try a work around, but this won't be perfect I'm affraid... and there is apparently no way to force windows do a full joystick rescan...
@Romeow: look at 78ED value 33 ...
@Omniatlas: are you sure you did not have anything wrong with the ELEC system? Even a transient issue? Did you try to switch the ECAM back into auto mode? (select another page twice to put it back in auto mode, usually pages like HYD is never called automatically in any flight phase, so you display it once, then push the HYD button again and it goes back in auto mode). I cannot reproduce this, so for now I do not consider that as a bug.
@SimStar: did you recompile the navdata bin files after changing the scenery.cfg?
@yaarslan : That is a shame I broke my crystal ball.
My apologies JL -- everything seems to be working now. There was an electronic board issue...cheers.
Yes this I did, but nothing happens?Quote:
Originally Posted by jeehell
So would you be so kind to describe hwo to install new navdata, as well as which paths has to be in the scenery.cfg?
Thanks a lot. Best regards! Marco
Thanks Jeehell for the offset. It seems to be my lack of experience with SIOC which caused the problems. In my last code 78ED/33 worked but after rewriting the script this offset stopped working. So I wonder if there was any change. But as I said it was my own incompetence.
Regards, René
there is nothing more than what you seem to have already done, I do not what happens on your setup, you're the only one who seems to have that issue...Quote:
Originally Posted by SimStar001
Try again all from scratch:
- install in a new folder,
- copy the navrecord files in navdata\navdata1 & 2 folders (only required on server PC).
- check the fsscenery.cfg is correct
- run the fmgs server and let it wait for some minutes before trying to check anything on the navdata