Sketchup 64 bit?
-
It more like related to this....
...or to be more exact...
But the answer is definitely in there...
-
@aerilius said:
I don't think it's economical to maintain two or more core engines (old for free, new for pro). Whatever will be further differentiating the Pro version, it will neither be single vs. multicore nor 32bit vs. 64bit or any other performance improvements at the core level. It would contradict the "SketchUp as a platform" plan.
So it could be Pro toolsets, importers, model&project management (xrefs?)... cloud and mobile services that free users wouldn't need...
.... but was the Free version really intended as a platform? I thought it was more a case of Google facilitating their wished for GE building populators of which their millions!
-
@solo said:
Hmmm, I dunno guys, we may be completely off here, maybe Trimble needs a lighter version of Sketchup, maybe even an ARM based version, judging by what I see from Trimble this might be their vision.
That look like a GameBoy golf game from the early 90's....
Big fish, little fish, cardboard box.....Jeff?
-
@solo said:
Hmmm, I dunno guys, we may be completely off here, maybe Trimble needs a lighter version of Sketchup, maybe even an ARM based version, judging by what I see from Trimble this might be their vision.
ARM based version would be ok.. but if they're requiring a proprietary device in order to run sketchup, i'm outz... pretty much positive about that..
(edit-well, i guess an ipad is a proprietary device too.. but it can do a heck of a lot more than run one program)
[edit2].. unless of course, the trimble device is something so amazing that it's a must have item.. but if that were the case, trimble would be in the wrong business to begin with..
-
-
@mike lucey said:
... but was the Free version really intended as a platform? I thought it was more a case of Google facilitating their wished for GE building populators of which their millions!
That isa platform already. True that not fully exploited but a platform. Just think of Building Maker integration, Street view texturing and all that crap (I do not really mean crap but since the locations with this data were so limited, it has never become a breakthrough).
Now it's another question, what they needed this platform for. Their GE and mapping services (which are great BTW - just SU could not cope with the growing demand).
-
@gaieus said:
Now it's another question, what they needed this platform for. Their GE and mapping services (which are great BTW - just SU could not cope with the growing demand).
i think they (google & other mapping services) just came to realize they can use satellite imagery to get better data than the 'millions of people drawing their neighborhood' approach..
now, if the 'millions of people' were actually drawing the innards of said buildings, then we'd have something of more value but sketchup->google earth was mainly showing the outer shells.. and the satellites can do that better/faster/more controllable etc..
[edit- or maybe they're using airplanes instead of satellites? regardless....)
-
@unknownuser said:
but was the Free version really intended as a platform?
I meant they put efforts in having one platform (on top of which different tools can be added), and since John said they would still offer a free version, I assume it uses the same engine.As for ARM: Blender is already there... (but as we have found out above, SketchUp does not follow where Blender goes.)
-
@unknownuser said:
...
i think they (google & other mapping services) just came to realize they can use satellite imagery to get better data than the 'millions of people drawing their neighborhood' approach.....and not to forget lidar scans
(Possible one good reason why Google and Trible did found eatch others)Perhaps need of some massive point cloud handling will in some point trigger 64 bit switch on SU.
-
@jbacus said:
This stuff is difficult to understand. I don't think we're beating a dead horse if there are still misconceptions floating around the community about the real benefits of 64bit computing.
The 64bit version is crucial for all rendering engines that are truly integrated DLLs into SketchUp and talk with it through SketchUp C++ SDK.
We would love to see extremely complex models rendered directly Inside SketchUp, but there is a limit how much one can fit into 32bit memory range, regardless how efficient instancing or other memory optimizations related to displacement,relight,repaint,etc. are in a rendering engine.
SketchUp wouldn't necessarily have to display such a complex content. This is being addressed by proxy systems already present in several rendering applications. Unfortunately those really integrated are choking at some point.
The 64 bit solution would also require a "real" SketchUp SDK, not only a way to export or read SKP files. This is very unfortunate that we developers have to "break" into SketchUp through a use of undocumented Ruby methods and a creation of Ruby extensions.
-
@unknownuser said:
This is very unfortunate that we developers have to "break" into SketchUp through a use of undocumented Ruby methods and a creation of Ruby extensions.
I don't normally condone breaking and entering, but in this case I thank you as your SU2TH, as it is frigging awesome, too bad I still need to port into Studio when SU buckles under minimal load (minimal by standards of evey other modeling app available)
-
@tomasz said:
@jbacus said:
This stuff is difficult to understand. I don't think we're beating a dead horse if there are still misconceptions floating around the community about the real benefits of 64bit computing.
The 64bit version is crucial for all rendering engines that are truly integrated DLLs into SketchUp and talk with it through SketchUp C++ SDK.
We would love to see extremely complex models rendered directly Inside SketchUp, but there is a limit how much one can fit into 32bit memory range, regardless how efficient instancing or other memory optimizations related to displacement,relight,repaint,etc. are in a rendering engine.
SketchUp wouldn't necessarily have to display such a complex content. This is being addressed by proxy systems already present in several rendering applications. Unfortunately those really integrated are choking at some point.
The 64 bit solution would also require a "real" SketchUp SDK, not only a way to export or read SKP files. This is very unfortunate that we developers have to "break" into SketchUp through a use of undocumented Ruby methods and a creation of Ruby extensions.
Would love to get a reaction to this from jbacus or another Sketchup developer
-
I've just posted this a few hours ago but I think my post belongs here, and kind of ignoring all said before...
Q:why would you want a 64 bit?
A:to handle and render big models
Q:can I do it?
A: FU$%& YES YOU CAN!!!!
thank to Daniel Pistelli who wrote a patch to allow 64 bit users to use more ram
basiclly what he explains is that 32 bit aplication have a limit of ram given by the OS 2gb and the rest is reserve for the system this patch does the magic
I've tested and F.Y. it works
so what you need?
1:sketchup any version I guess (I've tested on
2:plenty ram(4 at least 6 for big models)I have 8gb oviosly 64 bit OS
how to install it? actually patch it.
1: go to http://www.ntcore.com/4gb_patch.php and download 4gb_patch.exe (yes this is the oficial site)
2:unrar the file run it as an administrator if any(rigth click/run as an administraror)
3:a pop up windows comes, so search for the sketchup.exe under your program filesx86
and done
belive me it works flawless, I love it and works also for any other 32 bit aplication now I can render as 3d max with realistic grass and there are no more crashes on vray!!! so good luck and happy renders and sorry my bad english. -
This is not needed any more as SU has already made large address aware which means it can use up to 4Gb of memory on a 64 bit system - but for many people, this is still not enough so for this particular issue (rendering large scenes with many, high resolution materials etc. inside SketchUp) a true 64 bit version seems to be the solution.
Advertisement