Sketchup 64 bit?
-
It's less about leaking and more about throwing bones.
-
ThomThom has been one of the most adamant supporters of converting SketchUp to 64bit... I'm sure he'll let us know when it comes out... </sarc> Until then I'll concentrate on other matters. Like how many more plugins I can stuff in this fat hawg.
-
@solo said:
It's less about leaking and more about throwing bones.
Even a blind dog stumbles across a bone now and then!
-
imo:
calling for the suTeam to let us know what we'll see in the next version doesn't really 'fix' anything.. for one, all we do is basically move the timescale around a bit.. (i.e.- we all know what's coming in su9 so now we're sitting around talking about su10 instead.. same thing only we're left projecting even further into the future)..
for two though.. if i put myself in their shoes and people were barraging me with stuff like "do your project my way.. tell me what i want to know about it.. etcetc" .. i'd seriously be like STFUMFS!
[edit] well, actually.. if they were my clients.. i'd feel a lot more open to including them in the process..
[/edit]i mean, they do it their way and a compromise between users would be a lot more than just letting us know what's to be included in the next version.. other developers which are more inline with suggestions in the thread have a completely different approach all together which allows the users to actually be an integral part of the development process.. and i can appreciate those approaches but if i'm being honest, I myself would probably go more the route of how the suTeam does it.. I don't want people all up in my project.. it's my project you know and i generally want to have a good amount of control over it...
now, where my approach leaves the people actually using the stuff i build... i dunno.. is it the best design for them? possibly not.. am i satisfied with it? usually..
but if i didn't do it my way to begin with, it probably wouldn't even of happened...hmm.. that's ^ supposed to be saying something.. not quite sure i nailed it though..
[EDIT] anyway.. all things considered, i think Solo has the best idea..
come on.. throw a dog a bone every now and then..
-
You failed.....epically
STFUMFS
The STFU part i get but the MFS? Is that what I think it is? Like the old Prince song?
-
@rich o brien said:
You failed.....epically
STFUMFS
The STFU part i get but the MFS? Is that what I think it is? Like the old Prince song?
hahah
it's some pretty hardcore cussing going on there.. you got the milder parts at least
[but the S is only there to make the MF plural]
-
@Jeffrey
Coulda just used gobshitesI don't think many here are asking for 'what's next?' In fact the main participants are licenced power users...
It's morphed away from 64bit to a more 'We need A to be fixed because it's a big flow blocker' or 'why is B still rumbling around 4yrs after asking to fix it'
I'd love an opportunity to vent, discuss and provide exceptional data to a dev. Thomthom often sees videos I capture for various little snippits I think SU should achieve outta the bag. These aren't crazy far flung ideas but basic modeling needs that benefit users.
A good brainstorming session far outweighs a pitch and critique type scenario. Even if 80% of the ideas suggested were binned that 20% is worth more than the 100%.
At least in my mind it is....
I love watching people modeling in SU. It's the most valuable experience to see a power users perform complex task through a series operations. Now imagine getting to see that from a dev's perspective. It might spark an idea, introduce a new convention or just be a liberating experience for both parties.
It's a great way to build momentum. You really need to move past the 64bit argument and get down business of not critiquing but brainstorming.
-
I agree Rich, it's not about one thing or what we think is the answer to everything, at least not for me, I just want SU to be a little more robust, handle a little more of what I throw at it, grow with me and not me grow out of it.
-
@solo said:
I agree Rich, it's not about one thing or what we think is the answer to everything, at least not for me, I just want SU to be a little more robust, handle a little more of what I throw at it, grow with me and not me grow out of it.
can people outgrow the software? ...yes, absolutely..
something else i see happening though is that it's not always a case of outgrowing it.. it's more a case of realizing there are easier (sometimes A Lot easier) ways to do what you're trying to do..
and for an app being generally touted as 'easy', it's not really so.. -
@rich o brien said:
I'd love an opportunity to vent, discuss and provide exceptional data to a dev. Thomthom often sees videos I capture for various little snippits I think SU should achieve outta the bag. These aren't crazy far flung ideas but basic modeling needs that benefit users.
+1 to that. Watching other people work gives me new ideas to my own workflow. I wish. There was more people making videos while they model with SketchUp. I feel there is more material out there for other packages.
I have watched a few videos from Rich when he model, testing my plugins. He makes lots of comments while he model about what could be better which helps me greatly. But I also find great value in just watching as even just that gives me many ideas for new tools.
-
@unknownuser said:
something else i see happening though is that it's not always a case of outgrowing it.. it's more a case of realizing there are easier (sometimes A Lot easier) ways to do what you're trying to do..
and maybe 'easy' is the wrong word here.. faster is more the right word..
and in some cases, a lot faster.. (due to a more robust toolset)*i mean, the biggest user concern in sketchup is seemingly it's speed..
but why does speed have to always be about how many calculations sketchup can make in one second?
re: free vs pro..
wanna make a key distinction between the two? suFree maintains todays vanilla tools.. pro has a pro toolset..you get to keep the SU is easy&simple&slim concept via the free version.. but the term pro typically says the user desires a more powerful set of tools and they'd also be more willing&able to learn and use more tools..
[and the pro version would have the option to run the normal toolset mode as well.. but you get the importexports and layout etc..]and in my mind, "that's what plugins are for" just doesn't quite cut it.. i don't think the devs had this in mind at the time but when they made solid tools (a tool that was once a premium plugin became a native tool), they showed us the difference between a plugin and an official tool.. their version is +100.. (but that doesn't mean stop there on the solid tools boys.. they can still get a little more luv
).. -
I dónt know about 32 or 64 bit
What I think is that the Pro version has to get much faster for exploding and saving , if it wants to stay alive .If that means that the SketchUp core has to be modified deeply and that that costs a lot of money ,
well then
that would be the difference between Pro and Free .
I would not mind to pay more for that , at all .
But the next version has to address the speeding issue , quite a lot .
I think . -
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...
-
If they switch to 64 bit, don't they then have to maintain both the 32 bit and the 64 bit code? There are still lots of 32 bit machines out there. so its not a simple upgrade to the code and move on. Its adding an entire other code base to maintain. Sure they code's will be fairly similar, but still, that sounds like a logistical headache. I wonder how other companies handle that.
-
@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...
Absolutely true.
@chris fullmer said:
If they switch to 64 bit, don't they then have to maintain both the 32 bit and the 64 bit code? There are still lots of 32 bit machines out there. so its not a simple upgrade to the code and move on. Its adding an entire other code base to maintain. Sure they code's will be fairly similar, but still, that sounds like a logistical headache. I wonder how other companies handle that.
This is true, too. However I am starting to wonder how they will be beta testing a "legacy 32 bit version" in a year or two. Most of the beta testers also use SU professionally which means they need to keep up with hardware changes more than just grandpa who got my old machine to play with.*
OR they will only release new versions on the 64 bit platform after a while?
*To make sure I do not mean to hurt any grandpas here: it was this month when I finally got rid of my 32 bit XP as my main "production machine" and switched to a 64 bit Win 8. And even this was only because my computer crashed and I needed a complete reinstall (with some hardware changes, too, as my HD and video card got completely wrecked).
-
For some simple programs, 32bit versions and 64bit versions can be compiled from the same code base (just a switch when starting the compiler).
For SketchUp it would obviously require more work and switches and maybe parts of the codebase specific for a 64bit version. Once that is done one can produce SketchUp for both architectures but of course it adds to the complexity and requires more testing (beta testers can install 32bit SketchUp on a 64bit hardware, or virtualize it to keep it separate from their production environment, but who know if there are issues that appear only on a true 32bit hardware).
-
announce a time when 64bit will happen..
when that time comes, everything is 64bit from then on out..
'legacy' 32 bit versions are still available though no longer updated/supported(on the mac side, i don't really see much of a problem though.. i might be only slightly exaggerating when i say EVerybody is on 64bit machines)
-
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.
-
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!
Advertisement