Sketchup 2013 issues
-
@unknownuser said:
hey Frederik
you can try setting your AA via the ruby console.. enter this:
Test.set_AA_method(4)it will probably echo back 0 meaning your AA was previously set to 0.. relaunch sketchup and it will be set to 4x (or whatever # you choose to enter in the console.)
Wow, that's interesting. Should've known some years ago..
However on Retina displays Anti Aliasing has become irrelevant (in both CAD and Games applications). In fact it looks better now with the setting "0".. -
I am having this error....any idea where it is coming from?
-
Is it this one?
http://extensions.sketchup.com/en/content/grid-toolThink I have that installed - not seen any errors though.
-
thanks...that was the one. I do not recall installing it but after installing it now no more error report.
-
@gareth said:
@jiminy-billy-bob said:
@gareth said:
Jeff, that's the minimalistic look...!
Haha ! I laughed hard
i chuckled too.....but I always laugh at my own jokes...!!well, your follow up joke is a good one too
-
@archheni said:
Wow, that's interesting. Should've known some years ago..
However on Retina displays Anti Aliasing has become irrelevant (in both CAD and Games applications). In fact it looks better now with the setting "0"..fwiw, i keep my AA at 0.. and i don't even have a retina display yet.. i still have another year or two with my current mbp (i hope
) -
@unknownuser said:
@archheni said:
Wow, that's interesting. Should've known some years ago..
However on Retina displays Anti Aliasing has become irrelevant (in both CAD and Games applications). In fact it looks better now with the setting "0"..fwiw, i keep my AA at 0.. and i don't even have a retina display yet.. i still have another year or two with my current mbp (i hope
)I found that upping the AA by this method made my previous Mac SU image "jump" all the time. Change view then it gives a view and then the FOV seems to jump forward slightly. As annoying as the bad AA. And I think it slowed performance.
On the Retina display the edges are TOO FINE and I can hardly tell if something is selected. Even the face highlight is faint.
-
@pbacot said:
I found that upping the AA by this method made my previous Mac SU image "jump" all the time. Change view then it gives a view and then the FOV seems to jump forward slightly. As annoying as the bad AA. And I think it slowed performance.
On the Retina display the edges are TOO FINE and I can hardly tell if something is selected. Even the face highlight is faint.
really?
I thought there was a su update for the retina displays?
or maybe by 'update', it just meant that the app would work on the displays though not necessarily optimized for them? -
@unknownuser said:
@pbacot said:
I found that upping the AA by this method made my previous Mac SU image "jump" all the time. Change view then it gives a view and then the FOV seems to jump forward slightly. As annoying as the bad AA. And I think it slowed performance.
On the Retina display the edges are TOO FINE and I can hardly tell if something is selected. Even the face highlight is faint.
really?
I thought there was a su update for the retina displays?
or maybe by 'update', it just meant that the app would work on the displays though not necessarily optimized for them?Here is a screen shot. At the default zoom the png looks stronger than the original Retina. If you click on the image it is way stronger (magnified) and not representative.
-
@pbacot said:
Here is a screen shot. At the default zoom the png looks stronger than the original Retina. If you click on the image it is way stronger (magnified) and not representative.
hmm.. i'm not quite sure you can post a screenshot from your retina screen then have non-retina viewers see what it's really like.. for instance, the picture you posted is over 16" wide on my monitor at full size (which is already wider than your entire display even though you're only showing us a cropped portion of it)
it looks ok as far as the selection highlights /edge sizes are concerned..
but on your screen, i imagine it's much smaller and finer looking[edit] oh.. right.. i guess you were already saying something similar in your post.. but yeah, on a retina screen, the edges etc should be wider in px size than what they are on my screen.. but i guess sketchup is displaying everything at the same px size regardless of which display is being used.
-
RAL colo(u)rs are not working. They do not show up in the Material Browser, although they are at the same place in both Versions.
attached is the .skm
-
Because SketchUp 2013 will probably have created all of this folders/subfolders with the default Windows permissions - which are limited for everyone - including admins ! you might have an issue...
You will probably have [rightly] given FULL permissions to all users in Properties > Security > Edit... for your Plugins folder... letting you install and 'manage' plugins effectively.
BUT please remember that when you add files to the folders for Materials, Components, Styles etc these folders also need to have FULL permissions... otherwise Windows can fool you into thinking you have installed them... BUT in fact they have gone into a 'Compatibilities Files...' subfolder in the VirtualStore...
Having a link saying that in the top-bar of a Windows Explorer window for a folder is a serious clue... -
It doesn't appear to be a permissions issue. I have the same result and I know all my permissions are set correctly.
I added the Ral to SU8 and it happily works, I was then able to create a new collection from there back into the 2013 Materials folder. So it is a work around but it does work.
-
Thanks Box. I was sure to set the permission to all my folders. But the workaround is welcome. Thanks to both
-
I copied all of my Material subfolders from v8 into v2013... and so far they all work fine...
Including the RAL set...
I have unfettered permissions to all files/folders in my 'SketchUp 2013' folder... -
Could you make that very complicated lattice by hand faster ?
If you find a tool 'ridiculous' then don't use it.
It's not like you 'bought it'
I'll look at LatticeMaker - it could/should perhaps get a slight speed improvement in v2013 -
@tig said:
Could you make that very complicated lattice by hand faster ?
If you find a tool 'ridiculous' then don't use it.
It's not like you 'bought it'
I'll look at LatticeMaker - it could/should perhaps get a slight speed improvement in v2013Hi TIG, please don't misunderstand. I fully appreciate your immense efforts in improving SU's capabilities as a modeler over the years with your numerous contributions. And I, like many others here, enjoy using your incredible useful tools (including this one)..
I simply don't understand why it takes such a long time to execute it?
What are the bottlenecks..Ruby scripting? SU's single core limitation!? -
I finally found some time to do some plugin testing in SU13. In most cases I haven't noticed any speed improvements but one of your plugins TIG, Lattice maker, takes now even longer than before to execute.
And it already consumed a ridicules amount of time prior to the new release (Please see attachment for more details)..
To create a lattice out of an organic shape it takes me 13min and 20s in SU8 to finish the task..while in SU13 it takes slightly more - legendary 14min and 8s for the very same operation..I know this plugin hasn't been updated for a while now and I'm not sure if that's part of the reason that it takes aeons to complete any operation, but it's worth to mention that the very same task can be done in real time (!) in Modo with an inset + thicken command, no matter how complicated the shape is.
It's also generally problematic that during heavy script operations Sketchup is always in a "frozen state" which means one can only stop the ongoing process by doing a force quit of the application itself.
Now here would be my humble requests to the Sketchup Dev team and/ or Plugin dev's for the next SU release:
- Please let plugins execute faster (I mean much, much faster!)
- Please implement the possibility to stop any ongoing plugin operation without having to force quit SU
- Maybe also some sort of timer could be integrated to estimate plugin execution time.?
FYI, my hardware specs are rather new: 2,7 GHz Intel i7 Quadcore; 16GB Ram, SSD
-
The number of entities added into a context affect SketchUp's processing time of all calls manual and API.
Each has to be assessed for intersection, merge etc.
As the numbers increase the time rises almost exponentially as more and more entities are involved...
Also if the refresh of the graphics is not switch d off that has an effect too...
Using a
model.start_operation('xxx', true)
is the fastest way of processing - especially in v2013...
I need to check that LatticeMaker has those all set right...Edit: bum!
Although it does because 13 is taken to be < 7 [alphanumerics!] it skips it.
I'll PM you a test updated version - can you retry and see if the time improves...It's now updated to v1.3 in the main thread...
-
If we are to trust the tool, "Test time display". Then would be "Sketchup 2013," a bit faster. Whether this also has an impact on the plugins I can not judge.
Advertisement