https://www.creaform3d.com/en/handheld-portable-3d-scanner-goscan-3d

Have you checked the price of such a wonderful device. Several tens of thousands of dollars. The one that
Asobo uses is ~$86,000...

18 minutes ago, n4gix said:

Have you checked the price of such a wonderful device. Several tens of thousands of dollars. The one that
Asobo uses is ~$86,000...

For Warren Buffet that's chump change.

Having done some research Rob, I've learned that even a relatively simple object such as a seat can generate up to a half-million polygons. My mind cannot even conceive of how poly heavy a typical old-school cockpit would tally up!

I remember reading an article. It must have been at least a couple of years ago about a new rendering technology for gaming etc. that did not use polygons at all. If I remember correctly the code literally just produced all the pixel on the screen in the right place at the right time. It was supposed to revolutionize gaming with incredibly realistic visuals and performance. Haven't seen any about it since. Unfortunately, I cannot remember what it was called

9 hours ago, n4gix said:

Having done some research Rob, I've learned that even a relatively simple object such as a seat can generate up to a half-million polygons. My mind cannot even conceive of how poly heavy a typical old-school cockpit would tally up!

A naive question, Bill. I hear you but isn’t P3D your frame of reference which notoriously is weak at optimizing the use of the CPU/GPU pair and all the CPU cores ? 

6 hours ago, domkle said:

A naive question, Bill. I hear you but isn’t P3D your frame of reference which notoriously is weak at optimizing the use of the CPU/GPU pair and all the CPU cores ? 

It truly doesn't matter all that much in the final analysis Dominique if the problem is actually one of not being able to export and compile such a massive mess of mesh to begin with!

Prior to P3D v4.x modelers had to break up the model's mesh in to slightly less that 65k of vertex points in order to successfully compile a model (.mdl) file. The 'cure' for this problem was to clone the FSX/P3D Material with slightly different parameters and split the collection of objects using that Material into sets of vertex points of < 65k groups.

Even though that hard vertex size limit is no longer a compiling bottleneck, modeler's still need to remain frugal while designing the mesh objects. A great deal of this depends on the extent of the modeler's knowledge of the CAD program's various tools and other tricks of the trade to eliminate pointless complexity.

27 minutes ago, Rob_Ainscough said:

Why do you keep returning to this when I've shown numerous videos this "belief" is NOT the case?  Do you think I "fake" videos or something?  This perception is a result of end users NOT balancing their system graphics (and add-ons) settings within the limits of their hardware (all hardware from low end to high end has limits and finding the balance is key).

 

Cheers, Rob.

Do I keep returning to what ? I don’t remember having raised this issue before and as I said it was a naive question,  not an attack against P3D 😂 ! Bill’s answer was to the point.

Anyway, thank you for the laugh. It may come as a surprise but I don’t watch your videos.  My mistake, I am sure. 


 

13 minutes ago, Rob_Ainscough said:

You'd rather just "believe" ... does laughing help?

And your statement is "notoriously" inaccurate and what does this have to do with 3D modeling and 3D scanners?

Cheers, Rob.

Yes, yes, whatever you say

11 hours ago, Rob_Ainscough said:

I like your videos, especially the LSGK to LIMW ... you have some stutters that can be worked out but overall very nice.

Cheers, Rob.

Well, thank you, appreciated (really!)