Hi guys

 

Just a quick query , when I create radius arcs around a runway for approach using the fix option ,I notice a drop in my FPS. I think this is strange because I don't see why radius circles should affect FPS.The drop gets pretty severe when I put around 3.

 

Does any one else notice this ,or is it just me?

Same problem, Tabs said that he had insufficient reports to solve it. So, send a ticket.

One of the common links I've seen is ATI/AMD cards though - they handle the GDI+ drawing and transformation stuff differently. I've posted pics before showing no FPS difference with tons of FIX page stuff drawn using my GTX570... this is some kind of hardware specific thing. Highly unlikely we can do anything about it - we just tell the API what to do and it does it - we don't control the low-level stuff.

Hey,

i have the same symptom with a GTX570 B)

 

regards

 

Jürgen

I have the same problem on an ATI 7690M XT. I drop from a steady 27 for to around 16-20 fps. I just don't use fixes anymore.

 

Ethan E.

Hey,

i have the same symptom with a GTX570 B)

 

regards

 

Jürgen

 

Can you give me the example to test?

 

Can you give me the example to test?

 

Try KLAS ILS 25L. Add BLD as a fix and use the radials for each of the three waypoints on the chart. When all three are activated in the fix page, the fps will decrease.

 

Ethan E.

I'll test here - AMD user. Strange that a couple of lines should be any more graphically intensive than any other display element - makes no sense. Are you sure they are not being sent more often than necessary to draw? Makes more sense for it to be slower as the result of additional, redundent processing, that is occuring only when fixes are present.

 

EDIT: It appears to be a computation problem in the FMC.

 

Enter a waypoint in the FIX page. I used LON (sat at RW27R, with only EGLL/EGLL entered in the RTE page, and one fix, LON, in the LEGS page).

 

In the FIX PAGE 1 I entered LON. The first radial/distance was fine. entered 360/50. The second radial killed it. I DELETED each radial in turn. I had to delete both entries to restore FPS. Now for the interesting part. I entered them both again - NO FPS HIT. I entered a third - FPS hit again by the SAME amount as the first attempt with only two entries (hope you are keeping up :) ).

 

In summary at this point:

 

* Enter a FIX

* Enter the first radial/dist - fine

* Enter the second - FPS hit

* Delete both radials - FPS restored.

* Re-enter the same radials - FPS *OK*

* Enter a third radial - FPS HIT (by the same amount as at step 3).

 

Go to FIX page 2, leaving FIX page 1 intact.

 

Enter CPT (COMPTON VOR).

 

* Enter first radial - FPS HIT further (remembering it is still down from FIX PAGE 1).

* Delete first radial - FPS restored to that of FIX PAGE 1.

* Enter first radial - FPS *OK*

* Enter sercond radial - FPS HIT

 

Rinse and repeat.

 

Clearing all FIX pages restored FPS to that seen prior to using the FIX page.

 

I hope this helps isolate the problem.

 

Radials entered:

 

LON

360/50

120/50

210/50

 

CPT

010/50

130/50

220/50

 

I used /50 to ensure they drew off the map, in case it was some oddity with clipping. ND range made no difference.

 

It doesn't appear to be a graphics issue, more a logic issue in the FMC with radials present.

 

Best regards,

Robin.

I use a GTX 270 as well, but I do have an AMD CPU,

I can confirm this also.

 

This is not just an AMD or ATI issue.

 

Windows 7 64 bit

Intel i7 950 3.07 GHZ quad core

NVidia GTX 465

FSX w/ SP2 (no acceleration) running in DX9 mode

 

Btw, radius circles (green range rings from the FIX page) are NOT causing this (at least on my end). It's the radial lines that are drawn.

I.E. typing /50 around the London VOR will not cause an FPS hit. If you put a radial with it, 360/50, that will cause the hit to frames.

 

I duplicated the method Robin wrote down. Started at EGLL, put EGLL in my TO/FROM on the route page, and put LON as my only waypoint in LEGS.

Put LON in FIX page 1, and started drawing radials & circles.

 

(**note** all tests done with the mouse cursor "parked", that is off the screen and not causing it's own FPS drop. I made sure to record each FPS drop 3 times when entering radials into the FIX pages just to make sure. My tests are NOT contaminated from the mouse lag)

 

- started with 30 FPS solid

- input 360/50 on LON on FIX 1 page = no FPS hit

- input 120/50 = FPS dropped to 22

- input 210/50 = FPS dropped to 19

 

- deleted 210/50 = FPS went back to 22

- deleted 120/50 = FPS went back to the default 30

 

- input 210/50 & 120/50 = FPS back down to 19

 

FIX page 2 (CPT)

 

- input 010/50 = FPS dropped to 15

- input 130/50 = FPS dropped to 12

- input 220/50 = FPS dropped to 9

 

- deleted each radial/circle one at a time, each time the FPS rose to the previous value

 

I tested this whole process 3 times in a row. Same results and same FPS drop.

 

I also tested just drawing the circles and NOT the radial lines. No FPS drop. With a /50 /40 and /30 range ring around LON and the same around CPT, there was no FPS loss.

As soon as I started adding in the lines (360/ 120/ 210/ for LON) the FPS drops straight away.

 

Also, I tested this both with the plane in a cold dark state with just the battery on and the IRS not aligned and with the default state that came with the NGX (everything powered up and engines running).

 

In the un-aligned state, there was NO FPS HIT with the circles AND lines drawn into the CDU, since my nav display wasn't powered on. So it's not just because you're entering it into the CDU...it has something to do with the actual radial lines showing on the ND.

bumping this for awareness

Your test seems to be well done, I guess this is a matter of investigation from PMDG.

@trip7cap: did you not see the behavior whereby entering the first two radials a second time after deletion, did NOT result in FPS drop? This behavior is consistent for me.

 

Best regards,

Robin.

@trip7cap: did you not see the behavior whereby entering the first two radials a second time after deletion, did NOT result in FPS drop? This behavior is consistent for me.

 

Best regards,

Robin.

 

No Robin, it wasn't like that for me. Entering the second radial gave me an FPS hit. Deleting it restored my FPS. I deleted the original radial and started over.

First radial, no FPS hit. Second radial, FPS hit, and every other radial entered after that dropped the FPS further and further.

Deleting a radial restored the FPS by the original amount that was lost.

 

Entering a second radial for me always resulted in an FPS drop, and deleting the second radial ONLY always resulted in that same FPS restored.

 

I never had to fully delete everything off the FIX page to restore original FPS; only up to the second radial.

trip7cap

 

 

 

I tried your idea and it worked for me , if I don't put in the radial line the FPS doesnt drop

 

Thanks for the help