Yes, I did, and still have the problem.

Is there anything else I can do?

 

 

 

[GRAPHICS]

AC_SELF_SHADOW=0

AIRCRAFT_REFLECTIONS=1

AIRCRAFT_SHADOWS=0

COCKPIT_HIGH_LOD=1

D3D10=0

EFFECTS_QUALITY=2

GROUND_SHADOWS=0

IMAGE_QUALITY=0

LANDING_LIGHTS=1

NUM_LIGHTS=8

See_Self=1

SHADER_CACHE_PRIMED=1693458432

TEXTURE_MAX_LOAD=512

TEXTURE_QUALITY=3

Text_Scroll=1

HIGHMEMFIX=1

 

Read in another thread about a simliar problem as yours, have you got ezdok installed at all if you have run the config again for it again seems to work

Hy Paul,

 

Not to put too fine a point on it, don't call me defensive, but here's a shot of part of IF's route finder spawning a bunch of concurrent procedures. You recognise the 50 year old Pascal.

 

 

 

Steve

I am sorry but you are going to have to help me here. Which bit of this poorly written and inefficient array copying code do you think involves concurrency?

And this helps the op in what way talk about geting off topic

I am sorry but you are going to have to help me here. Which bit of this poorly written and inefficient array copying code do you think involves concurrency?

 

And this helps the op in what way talk about geting off topic

 

Yes, forums initiate and branch discussions of all kinds unfortunately.

 

The route finder objects must communicate during their searches or become inefficient. You're way out of your depth now, which seems a shame after your friendly chat off thread.

 

I suggest you drop it Paul, you lost this one. And besides, I chopped off the inefficient bit with the photo.

Hi Pete, you are right, this topic has gone way off track. I don't think the OP will object too much since their Q was answered on the first page or so. A brief summary of this digression to save you the boredom of reading is that SteveW was singing the praises of how well FSX was coded and what a great basis it would make for any future flight Sim like he was going for an interview! I challenged him on some of his assumptions and though it got a bit boring and nerdy, and some of it went offline, I had thought he had accepted the possibility that FSX contained room for improvement. He then came back with the unidentified code snippet above which he cliamed was an example of how well FSX exploited multiple processors. The fact that the code snippet is simply a loop that make copies of the contents of arrays, and does so in way I would not accept from a trainee, is apparantly proof that I do not understand just how well FSX is written.

 

Code review - Not interesting to anybody who is not a nerd. Not interesting to most people who are nerds...

1) D := max(MaxBranches, JArray[NextRoute,0]) ;

simpler, faster, more meaningful, less prone to error, less prone to typos

2) Comment the purpose of the loop

3) C is a constant value, move it out of the loop.

4) Nobody cares what the value of C is, they use the constant CList[C] is so take it out of the loop as well.

5) WaypointList.Count * 2? Why times 2? Do not use magic numbers without a comment.Better still, do not use magic numbers.

6) Why write zeros to every element if on the next line you are going to replace the zeros with the actual values?

7) ##### are you trying to with TCrawler?

haha, don't get so excited You've obviously got abolutely no idea what it does, there's not nearly enough in view. It's actually a screenshot I happened to take mucking around with a screen grabber way back. It's the code I was using to test the theory, the production code is pointers. If you like I can come over and we'll sit down and make a better version?

 

You say MS FSX is poorly written I doubt it. You bring up concurrency out of thin air, I answer you, now you pose more questions, I answer you. But all in all it's been a complete waste of time.

 

Belay that Paul, I think it is fair to say we would not get on.

...here's a shot of part of IF's route finder spawning a bunch of concurrent procedures...

... You bring up concurrency out of thin air...

Belay that Paul, I think it is fair to say we would not get on.

This time, I agree with you.