Results 21 to 30 of 30
-
10-02-2014, 04:48 PM #21
- Join Date
- Mar 2008
- Location
- France,Nice
- Posts
- 2,652
Re: Can't start some elements of FMGS
Hi Barry,
so it crashes really early upon launching.
I changed the EIS.exe file a bit:
http://www.jeehell.org/EIS.exe
Put it in your EIS folder on the faulty PC. Try to run it alone, using one of the shortcuts (PFD, ND, wahtever) which are created by the installer. It will create a file called startlog.txt, and see if it is empty as well.
JL
-
10-02-2014, 05:03 PM #22
- Join Date
- Mar 2008
- Location
- France,Nice
- Posts
- 2,652
Re: Can't start some elements of FMGS
I also believe the issue is OpenGL. There have been big issues with ATI cards, especially older ones.
When googling your graphics card, it seems to have some issues with some of the drivers and Opengl. Are you sure you have the latest one released? ( I could find a 10.2 version ?).
I activated OpenGL logging from the application, the EIS.exe should output an EIS.log file, which may indicate OpenGL errors/info. Download it again if you downloaded it before this message...
http://www.jeehell.org/EIS.exe
JL
-
10-06-2014, 04:43 PM #23
- Join Date
- Jan 2007
- Location
- East Yorkshire UK
- Posts
- 267
Re: Can't start some elements of FMGS
I think we are getting to the bottom of this problem.
I updated the drivers and the following is the EIS log:
0 (I) Thread ID 3192 Log subsystem started in elapsed time mode.
16 (I) Thread ID 3196 Service thread started
328 (i) Thread ID 3196 Temporary rendering context created
328 (I) Thread ID 3196 Getting OpenGL entry points and extension
328 (I) Thread ID 3196
328 (i) Thread ID 3196 OpenGL rendering context information:
328 (i) Thread ID 3196 Renderer : ATI Radeon X1950 GT
328 (i) Thread ID 3196 Vendor : ATI Technologies Inc.
328 (i) Thread ID 3196 Version : 2.1.8545 Release
328 (i) Thread ID 3196 GLSL version : 1.20
328 (I) Thread ID 3196
375 (I) Thread ID 3196 Getting OpenGL entry points and extension
406 (i) Thread ID 3196 Backward compatible core PBuffer context successfully created
406 (I) Thread ID 3196 Service context successfuly initialized
688 (i) Thread ID 3192 Temporary rendering context created
688 (I) Thread ID 3192 Getting OpenGL entry points and extension
688 (i) Thread ID 3192 Temporary rendering context destroyed
734 (I) Thread ID 3192 Getting OpenGL entry points and extension
43828 (i) Thread ID 3192 Service context queue task depleted
The earlier version of drivers was 2.0.6645
I could then start the ND's and PFD's so open GL is indeed the problem. However the graphics ran so slow as to be unusable and I have had to roll the drivers back to keep my sim operational. The AST ND and PFD has always worked fine on this PC.
I then found that I could start the standby's, SD, EWD on the third PC of my system which looks good, this is fitted with a Radeon HD2400 PRO as is my PC4 which will eventually run the overhead.
I don't want to throw a lot of money at these PC's but I have found a HD2400 PRO on ebay which I will put in PC2. That could well fix this problem.
Barry
-
10-06-2014, 04:54 PM #24
- Join Date
- Mar 2008
- Location
- France,Nice
- Posts
- 2,652
Re: Can't start some elements of FMGS
Hi Barry,
Just for the sake of knowledge, which graphics ran slow: AST or mine or both?
Regards,
JL
-
10-06-2014, 05:06 PM #25
- Join Date
- Jan 2007
- Location
- East Yorkshire UK
- Posts
- 267
Re: Can't start some elements of FMGS
Everything on the PC ran slow including AST or yours. Even affected the network. Really was bad and all corrected when I rolled the drivers back except yours.
Will report when I have changed the card.
barry
-
10-06-2014, 05:12 PM #26
- Join Date
- Mar 2008
- Location
- France,Nice
- Posts
- 2,652
Re: Can't start some elements of FMGS
Ok so that was apparently a driver issue more than anything else. Yes please keep me posted!
JL
-
10-10-2014, 05:26 PM #27
- Join Date
- Jan 2007
- Location
- East Yorkshire UK
- Posts
- 267
Re: Can't start some elements of FMGS
Changed the graphics card and the modules now load so it was probably open GL was that problem. Next problem is the graphics are running very slowly, like a slide show. CPU showing 99%. Running the same modules of AST runs at around 60% and very smooth. Wonder why the difference. Will try running on another PC when I get the chance. EWD, SD and standbys on another computer running well.
barry
-
10-11-2014, 06:17 AM #28
Re: Can't start some elements of FMGS
Running the standby instruments is very CPU intensive, try running without that first.
Soarbywire - Airbus Flight Simulation and Engineering | Jeehell FMGS - Free professional A320 avionics software for the cockpit enthusiast.
-
10-11-2014, 06:53 AM #29
- Join Date
- Jan 2007
- Location
- East Yorkshire UK
- Posts
- 267
Re: Can't start some elements of FMGS
They are on another PC. I am trying to run 2 ND and 2 PFD on one PC using two screens into one card. Nothing else running on that PC. Tried starting one ND and one PFD but still not smooth.
-
10-11-2014, 02:09 PM #30
- Join Date
- Mar 2008
- Location
- France,Nice
- Posts
- 2,652
Re: Can't start some elements of FMGS
Hello Barry,
Please update to the latest version I just put online.
Then, in the EIS folder, you go to the PFD.ini, ND.ini,PFD.ini, FOND.ini and add the following lines:
PFDminDelay=0.04
PFDmaxDelay=0.2
NDminDelay=0.04
NDmaxDelay=0.2
Now those are the default values. You should change mainly the minDelay value, this is the value which decides how fast the application tries to update it's display (0.04 means once every 4 ms which is 25fps).
The ND (and a bit the PFD, but less than the ND), can take a LOT of CPU, because it needs to perform a LOT of calculation each time a new frame is drawn. If the 4ms is too tight, the process will eat the CPU time available for all applications, resulting in the 99% CPU usage.
I suggest you do the follwing to tune the timings:
1. Run the software, only CPT PFD, check how much CPU it takes.
2. Adjust the PFDmindelay in PFD.ini so that it takes less CPU than 10%. Everything less than 0.1 should be relatively smooth.
3. Run only CPT ND, check how much CPU it takes.
4. Adjust the NDmindelay in ND.ini so that it takes less CPU than 25%.
5. Max delay should be fine at 0.2.
Every time you change one value in the ini file, you need to save the ini file and start again the software.
Now, put those PFDmindelay and NDmindelay values in all the ini files (PFD,ND,FO PFD, FO PFD) (each PFD can take the place of the ND, and vice versa, the PFD timings being used while in PFD mode, and ND timings while in ND mode).
Note that you can also adjust the EWD, SD and STBYs that way (SDmaxDelay, SDminDelay, EWDmaxDelay, EWDminDelay, STBYmaxDelay, STBYminDelay).
Regards,
JL