That's why XP is bottlenecked.  Rendering is dependant on CPU which is primarily single core. 

Edited July 29, 20232 yr by Greazer

1 hour ago, brinx said:

The stubbornness to admit it's a bug and not a feature is just silly.

Its both isnt it. I doubt they will ever totally remove them since weather is random.

16 minutes ago, soaring_penguin said:

Efis007 update was humor, not a defence for LR. IF you took his post as a reason to attack X-Plane fans, you do have a problem…

Attack who, just raised a question, I dont see and missiles flying.

4 hours ago, Greazer said:

That's why XP is bottlenecked.  Rendering is dependant on CPU which is primarily single core. 

I think your comments and opinions would be better kept to yourself when you know little to nothing about the internal workings of X-Plane.  Particularly whether or not the CPU or GPU renders specific elements of X-Plane 12, or how many cores it uses.  

Posting negative opinions (which is all they are), for the sake of appearing like you know what you're talking about, when you obviously don't, doesn't add any weight to your credibility or your arguments.  

My advice.  Stick to making videos and announcing your plans to buy software that isn't even released yet. Along with the hardware needed to run it.

 

Edited July 29, 20232 yr by GoranM

There are no right or wrong opinions. People are entitled to express their thoughts. If there are incorrect statements that’s another thing. Explain what is wrong rather than tell the poster to stay away.

22 minutes ago, Ray Proudfoot said:

People are entitled to express their thoughts.

Indeed they are.  Exactly why it's my opinion that he doesn't delve into topics he knows little about, like rendering pipelines in X-Plane.  

As Brian mentioned here, he keeps coming back and posting the same things, like a broken record.  

Edited July 29, 20232 yr by GoranM

4 hours ago, Greazer said:

That's why XP is bottlenecked.  Rendering is dependant on CPU which is primarily single core. 

Actually, its the physics and simulation that are dependant on the CPU, and windows home that is primarily 2 to 4 cores.

-> and rendering is dependant on the physics and simulation.

If a plane is moving through the sim world at 50 samples per second, there is simply no way to render it faster than that.

you could render the same position multiple times like many games do, and claim super l337 performance.

But you will still only ever see 50 frames a second.

As I understand it, part of them getting FAA certified requires them to not lie about how many frames you see.

Halo often ran at something like 6 fps on the XBOX when measured by that standard (while fps counters claimed many more) there is at least one video around YouTube dissecting it.

Because you can actually see it:

This is something I learnt from Laminar/XPlane, so while I don't expect everyone to know it, it should be more widely known.

Edited July 29, 20232 yr by mSparks

@goran, your comments are duly noted. @Greazer, backup your claim with proof. If you are unable to then accept with good grace your statement was incorrect and withdraw it.

31 minutes ago, GoranM said:

Indeed they are.  Exactly why it's my opinion that he doesn't delve into topics he knows little about, like rendering pipelines in X-Plane.  

As Brian mentioned here, he keeps coming back and posting the same things, like a broken record.  

Very reason i banned myself till things got a little more sensible. Kinda.

Stuff We Are Working On - X-Plane Developer

FSElite Interview: Laminar Research - X-Plane 11 Vulkan and More - FSElite

The future: in the future the rendering node graph will also let us render different parts of the frame using different CPU cores

X Plane is not supporting proper multi core at the moment, as mentioned by lead Dev.

Other sim is getting proper multi core and a benefit of 5-10x times performance.

I'm sure hoping they can fix this in XP!

Edited July 29, 20232 yr by Greazer

2 hours ago, Greazer said:

Stuff We Are Working On - X-Plane Developer

FSElite Interview: Laminar Research - X-Plane 11 Vulkan and More - FSElite

The future: in the future the rendering node graph will also let us render different parts of the frame using different CPU cores

X Plane is not supporting proper multi core at the moment, as mentioned by lead Dev.

Other sim is getting proper multi core and a benefit of 5-10x times performance.

I'm sure hoping they can fix this in XP!

Apart from both links being over 3 years old, ie, half way through the X-Plane 11 run, did you read the very first statement you posted and do you understand what it even means?

Again, if you're going to post opinions, you need to post them with current evidence to back them up.  If not, you will be called out on them.

Edited July 29, 20232 yr by GoranM

36 minutes ago, Greazer said:

Other sim is getting proper multi core and a benefit of 5-10x times performance.

Actually if you read more, thats what the last bunch of betas are aiming at. And xplane has for a long time supported mulitcore, just like the other sim as you put it, uses them for texture loading and i believe for ai planes. All the latest releases are headed to "multi threading" which for any one with a little nous would understand is not a simple task.

6 hours ago, soaring_penguin said:

Efis007 update was humor, not a defence for LR. IF you took his post as a reason to attack X-Plane fans, you do have a problem… .

I have to correct, my comment was about flying carpet’s input that it is a feature, not a bug. 

Anyway, back on topic.

this little snippet 

Quote

The biggest change to X-Plane 12.06 is not one you can see: we’ve converted the main rendering pipeline from 12.0 (which was hand coded) into a rendering node graph.

is the #1 reason I was hyped for 12.06.

Spat my coffee all over my screens when Ben let that bombshell slip a few months ago. I knew virtually no one would appreciate its significance, and of course, new tech doesn't always pay off or live up to expectations, so I (mostly) kept my mouth shut about it.

I also had (and have) a lot of uncertainty around how good the hand coded one was, its clearly not terrible, because for the most part XP scene performance is solid, they demolish all the others in terms of render distance for example.

what is it?

The nodegraph - or more commonly called scenegraph, is a data structure that is designed to tell you what you can safely ignore (and therefore not waste time calculating).

Moving to a fully automated nodegraph makes this much more reliable and flexible.

The last time I implemented one (too many years ago to stomach), it reduced compute time for scene compilation from 3 hours to 1.5 seconds... (anyone who used the quake 2 mapping tools may remember that, but afterwards it was like that time sink never existed and the world moved on).

That is potentially the implications of this change. It should fix issues we've noted like the complex water structures at EHAM, allow them to add a ton more close up detail, and gawd knows how much other cool and important stuff.

I'm almost too excited about what comes next to think about it. (but you know I will)

Not meant to start a fire but the core utilization of XP12 is also bothering Austin himself.
Click here for an interview with him from a few weeks ago https://youtu.be/Hk6Hb2QkhtI?t=924

 

Edited July 29, 20232 yr by peroni

@mSparks I am also looking forward to what this change will bring. I can fathom what this data structure does and I am impressed. I worked for a software company that did graphical displays. I was SW test guy and I was always amazed by what the graphics guys produced. I bet they do something like this today, makes sense.