Jump to content

---> Framerate issues, combination topic


Aerosoft Team [Inactive Account]

Recommended Posts

  • Replies 326
  • Created
  • Last Reply

hi, if I can add my observations based on a flight from LFMP to LEPA on the ground I was getting 34fps this is using no weather program just the fsx fair weather setup. the higher i climbed the slower the fps until at about 30k feet i was down to 8fps.

i followed exactly the same flight plan and profile in the a320 and it was a solid 34 fps but did cut back to around 24fps at 30k feet

a thing of interest is that with the 318 if i looked at it from outside view I immediatly had 34 fps wheras with the 320 I was down to 16fps on outside view

this was using hotfix 1.01c btw

Link to comment
Share on other sites

reinstall, hotfix applied and no RAAS this time. Also installed the ND file from post 2

FPS now much better back to 28-30

Protocol of AB_ND_GDI.dll

company: aerosoft

file version: 1.3.0.28

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

start time of application : Mon Sep 29 12:50:39 2014

12:50:39 : INFO :File read successfully! Airports over all = 9479, airports with runway length >= 4200 ft = 6212 (filename:'F:\Flight Simulator X\Aerosoft\Airbus_Fallback\NavdataPro\airports.txt')
12:50:39 : INFO :File read successfully! Navaids over all = 14018, NDBs = 6625, VORs and/or DMEs = 5949 (filename:'F:\Flight Simulator X\Aerosoft\Airbus_Fallback\NavdataPro\navaids.txt')
12:50:39 : INFO :File read successfully! Waypoints over all = 244476, found intersections = 108796 (filename:'F:\Flight Simulator X\Aerosoft\Airbus_Fallback\NavdataPro\navaids.txt')
12:50:39 : INFO :Opening SimConnect...
12:50:39 : INFO :SimConnect opened successfull...
12:51:08 : INFO :File read successfully! Filename: 'Aerosoft\Airbus_Fallback\TerrOnND\ASDBTerrOnND.dat'
12:51:26 : INFO :cLS: 0, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 1, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 2, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 3, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 4, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 5, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 6, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 7, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 8, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 9, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 10, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 11, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 12, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 13, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 14, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 15, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 16, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 17, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 18, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 19, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 20, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 21, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 22, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 23, c. a. s.: 0, f. a. s.: 0
12:51:26 : INFO :cLS: 24, c. a. s.: 0, f. a. s.: 0
12:52:30 : INFO :S(1) d. t. W.XCNSA 4
12:53:10 : INFO :SimConnect closed successfull
12:53:10 : INFO :Normal termination: Application is closing now!

Link to comment
Share on other sites

Hello to everyone.
I had the FPS issue (FPS droped from 30 to 25-27) and after replacing AB_ND_GDI.dll my FPS became absolutely stable.
But I have an issue with black screen when changin from fullscreen to windowed. I have installed simconnect on FSX but it didn't help unfortunately.
Link to comment
Share on other sites

Those who experienced massive frame drop when using the IAE variant, go to the first page, second post of this thread and try the attached dll.

Tried both DLLs. Problem still exists - as soon as I move the thrust lever, frames drop to unplayable 12 fps and below.. Here's the protocol from AB_ND_GDI.log (looks incomplete to me, but there's no more info in the file):

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

Protocol of AB_ND_GDI.dll

company: aerosoft

file version: 1.3.0.28

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

start time of application : Mon Sep 29 21:15:47 2014

21:15:47 : INFO :File read successfully! Airports over all = 9479, airports with runway length >= 4200 ft = 6212 (filename:'C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Aerosoft\Airbus_Fallback\NavdataPro\airports.txt')

21:15:48 : INFO :File read successfully! Navaids over all = 14018, NDBs = 6625, VORs and/or DMEs = 5949 (filename:'C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Aerosoft\Airbus_Fallback\NavdataPro\navaids.txt')

21:15:48 : INFO :File read successfully! Waypoints over all = 244476, found intersections = 108796 (filename:'C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Aerosoft\Airbus_Fallback\NavdataPro\navaids.txt')

21:15:48 : INFO :Opening SimConnect...

21:15:48 : INFO :SimConnect opened successfull...

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

And here's the protocol from FMGS.log:

[29/09/2014 21:15:49:058]: Start logging.

[29/09/2014 21:15:49:058]: Gauge loaded: 2.

[29/09/2014 21:15:49:058]: Info: 0, 0, size=0x0a7f0000.

[29/09/2014 21:15:49:058]: Module version: 1, 2, 6, 16. Date/time: N/A.

[29/09/2014 21:15:49:058]:

[29/09/2014 21:15:49:058]: GDI+: EncoderClsid 4.

[29/09/2014 21:15:49:058]: UpdateTh: POST_INSTALL=0x0711e470.

[29/09/2014 21:15:49:058]: PIPE: The named pipe, \\.\pipe\FBW_DataExchange, is created.

[29/09/2014 21:15:49:058]: PIPE[1]: Waiting for the client's connection...

[29/09/2014 21:15:49:058]: UpdateTh started: 0x0711e470.

[29/09/2014 21:15:49:073]: PIPE[1]: Connected to the client.

[29/09/2014 21:15:49:073]: SetBuff: 71C9928.

[29/09/2014 21:15:50:244]: Gauge unloaded 1.

[29/09/2014 21:15:50:244]: End logging.

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

BTW, with the two dlls from the post, FSX no longer exists after the Airbus was selected, I have to kill it in the Task Manager...

Link to comment
Share on other sites

Aerosoft, I installed the new "Airbus_ECAMD2D.dll" now I can turn on the Weather radar and my frame rate wont drop drastically. It only drops 2 fps (Normal). So now I can fly it with weather radar. I tested it with CFM e IAE. Maybe it had something to do with weather radar thing? I guess this dll fixes this issue.

Link to comment
Share on other sites

This dll solved my Frame rate issue but something came up: Now when I start the flight using the checklist feature, the engine won't spool up. It only happen if you try the flight with Checklist feature. Can you fix this? Thanks! PREPARD 2.3. From COld and dark to Checklist feature.

Link to comment
Share on other sites

Hi,

But this is not a real solution!

Same problems (version 1.01c) : C&D 35fps - Taxi 22fps - in flight 18fps (unstable!!) - App/final 18 fps (no airport addon) ... in other product , like 777-300PMDG, i have about 30fps stable during all phases of flight.

On my CPU, 2 of 4 processors are 100% utilization from the phase of taxi and very unstable ... (about 1 max with other products).

I also occasionally freeze once logged on ivao (0.4pfs and freeze), i need to restart FSX ... it's a big constraint ...

I have start FSX with clean FSX.cfg, with & without ASN ... same problems...

I use FSX SP2, i5-2500@3.30ghz, 8Go ram and GTX560Ti. Win7 64bits.

Mains Add on used : FTX global, ASN (no beta version), Ezdock & DX10 scenery fixer.

No problems with 737NGX, Q400 Majestic & 777-300PMDG.

I hope this leakage problem will be solved as soon as possible.

Thank you for your listening.

(sorry for my bad english)

I think to have found the solution to my problem (Aforementioned) :
1- I deleted Nvidia 3D vision drivers, Nividia HD sound drivers & Nvidia GoForce Experience installed with 344.11.
2- I deleted Nividia Inspector.
3- (for ivao freeze) I start up IVAP in external directly on win7 not in FSX.
I have an improvement of my fps : 30/40 fps instead of 15/25 fps (with ASN and WX ON) & I have no more FSX freeze.
769967AERO.jpg
Hopefully it can help you. ;)
Bye
Jerome
(sorry for my bad english)
Link to comment
Share on other sites

Started using the new Airbus_ECAMD2D.dll. The framerate has improved noticeably, however I am now experiencing severe stuttering shortly after the wx radar is activated, which seems to be induced by the inability of P3D to keep up with the loading of terrain textures. Indeed the induction of blurries and concomitant stutters make the plane somewhat unflyable.

To rule out any potential effect of having updated to P3D v2.4, I test several default and payware aircraft, including the A2A Cherokee and the RealAir Turbine Duke, in the same area and with the same weather conditions (default Major Thunderstorm) over Fiumicino (LIRF). In these test conditions the framerate did not drop below 29 fps (when locked to 33 fps), and no blurries or texture-loading induced stutters occurred. Prima facie, this suggests that the issue is not related to the update to v2.4. Indeed, I got the impression that there has been an improvement in texture loading performance in v2.4 vs v2.3, but that may be due to a placebo effect!

I'll test the Airbus in this scenario again tomorrow, next time monitoring CPU and GPU temperatures to see if this could have potentially been caused by throttling.

Did anyone else observe this outcome with the new dll?

Link to comment
Share on other sites

I'm having trouble with engines now, as you can see in the picture. As soon as Fs Global weather loads, My engines stop working. It won't spool up. It started with this new DLL!. Any words on this?

Link to comment
Share on other sites

I'm having trouble with engines now, as you can see in the picture. As soon as Fs Global weather loads, My engines stop working. It won't spool up. It started with this new DLL!. Any words on this?

Report before and after frames.

Make a backup of all files before replacing. This are only temporary files.

The dll is only meant to test frames, nothing more.

Link to comment
Share on other sites

The dll is only meant to test frames, nothing more.

I know. The frame rate issue has gone with dll, now I can fly with weather radar on, but this issue came up. Just for you to be aware of. thks

Link to comment
Share on other sites

  • Aerosoft

Gents, short update on this issue.

I have spoken to all developers and we are now 90% sure there is no single reason for the very low framerates on a few machines. It has to be a combination of factors. Now so far we are simply not able to recreate the issue on our systems but looking back at older test results we have found one machine that might have shown this. After a reformat of the disk and a clean install the problem was not detected again and we forgot about it. To put it bluntly, if you get 5 fps on the Bus you are in a perfect shit storm. There have to be several things that affect your system that does not affect thousands of others. As soon as FPS drops under a certain threshold all kinds of processes start to wait for each other and that makes the problem larger and larger. As we have to do so much on a Frame by Frame base this can affect our aircraft more then others.

Our path to 'solving' the issue is multithreaded. Joshua has made some good progress on optimizing some things that will be most beneficial for people with modest hardware while Frank is trying to prevent the ND with WX from being overloaded. Certainly ASN can send massive amount of data in certain weather conditions that even just reading (let alone manipulating and displaying) it can be hard. If this can not be optimized we'll just read partial data (as it is so detailed we believe it will be nearly impossible to detect).

Later this week we'll have a large hotfix that will solve some issues and where we hope that this issue is partly solved. However, and i must underline that, as it just will not happen on our systems and those of our testers (say 50 in total) any change will be a shot in the dark. And as we know it does not happen on a cleanly installed system we are still sure that the code itself is not the problem. It's the combination of the code and the non standard systems some users have.

Link to comment
Share on other sites

I don't think it is related to "non standard systems" as in most of the people with the problem it is only isolated to the newly released Bus weather radar and not other complex addon airplanes with a wx radar system.

In my particular system, it is a highly optimized and clean one only used for FSX. The FPS drop could be reproduced like others have mentioned, above 10 K altitude and using ASN latest Beta 5 release. Will be looking forward this new hotfix and hopefuly the issue will improve or be resolved. Thanks for your effort.

Carlos

Link to comment
Share on other sites

Happy to report my frame rate issues are gone after I did 3 things:

1. Installed the ECAM file

2. Installed the other ND file

3. Didn't use ASN for an entire flight

Which one of those 3 fixed my frame rate problem, I have no idea. I can't use ASN until they patch it for 2.4 so I'll do more testing then.

Did you install Airbus_ECAMD2D.zip? How did you get to spool up the engines after your Weather engine loaded? I tested it with fsx and Prepar3d 2.3, I get a negative number on ECAM.

Link to comment
Share on other sites

See #1 and #3 of my post for the answers to your questions.

Oh. I see. If I dont use any weathe engine, I won't have this issue. This ECAM DLL fixes the frame rate issue. I hope Joshua comes up with a hotfix soon. Because so far, I cant fly like that. Cheers.

Link to comment
Share on other sites

Ok i can report, i solved the frame rate issues on my system.

1. Pushed ASN back to "B5371"

2. Installed the ECAM2D file

Until this point i used the "test" ND file, but i had the same frame drops as before.

3. Restored the original ND file

Now my frames are stable at 30 fps.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use