As TIG has said, some other plugin is telling SketchUp to load that (missing) file. Do a text search of the files in your plugins folder looking for a string containing that filename.
Posts
-
RE: Plugin load residue, ruby
-
RE: Sketch up to a new pc.
The license allows you to install on two computers provided they are for the same person (i.e. not shared with others). If you are installing the same SU version, you can just copy the contents of the plugins folder across after installing SketchUp.
-
RE: Dinner, anyone?
Hard to be certain due to perspective, but the legs look like knee-clonkers to me! Nice model and render, though.
-
RE: Dimension Lines - Text disappears
I agree with the others: you have some classic examples of what happens when you don't use SketchUp's layers correctly.
For example, everything visible in scene 3A is in a single (unnamed) container Group that references Layer3. However, all but one of its nested entities reference Layer2. The dimension at the right edge references Layer0. This means you will see all of the contents of the Group only if Layer0, Layer2, and Layer3 are visible. The dimension line at right in scene 3A is also obscured because it is foreshortened due to the view angle and then mostly blocked out by the white space around the dimension text. Orbit a bit and the line becomes visible.
But this messed up nesting causes strange effects between scene 1A and scene1B. Scene 1A does not show the aforementioned Group at all because Layer3 is not visible. When scene1B turns on Layer3, the only part of the Group that appears is the nested dimension that references Layer0! The rest references layer2, which is still not visible.
Scenes 2A and 2B do not show any of the contents of the Group because Layer3 is not visible.
Also, you have copied most of your Groups 3 times at the identical position and size, referencing each copy to a different Layer. This causes the visual impression that you are looking at the same thing when you switch scenes when you are actually looking at a different copy!
-
RE: Scroll button zooming while orbitting in pro 2014
This sounds like an issue with your mouse, its drivers/settings, or your mouse technique, not with SketchUp per-se. That is, for some reason SketchUp is receiving multiple mouse input events when you press the button. Check what the system settings for the mouse are, they may be interfering with SketchUp. Can you borrow another mouse to see whether the problem is with the hardware? I don't know why you see this with newer versions but not with SketchUp 8 - perhaps they tuned up something in the GUI that used to drop almost-simultaneous mouse inputs...
-
RE: El Capitan
I've been running SU Pro 2015 on El Capitan for a couple of months on a mid-2012 MBPr. I've had no problems with SketchUp itself. I very seldom use Layout, so I can't speak personally about it, but I've seen some reports of a few issues there.
For some time now, Trimble has devoted relatively little of its developer resources to Mac. Many issues, complaints, and seemingly arbitrary differences from Windows have sat unaddressed for a long time. Until/unless that changes, I wouldn't hold my breath waiting for support of Metal, as that would likely require substantial branching between the core graphics code on Windows and Mac. SketchUp long ago chose OpenGL for its portability.
-
RE: [?] Importing layers from another SU file.
Yes, unused layers are purged during the import.
-
RE: Using SmartDrop
This sounds like the component has the glue-to behavior set. Open the Components window, click the little house icon to see "In Model", select the component and then select edit in the component window. If you see Glue To set to anything except "None", you need to change this to eliminate the glueing behavior. Note: if you originally draw the component up against another face, this behavior is set automatically unless you unselect it in the create component dialog.
-
RE: Is there an action log plugin available?
SketchUp builds an "undo stack" of every transaction in a model session, but so far as I know the only way it is exposed in the API is through a single-step undo method. That is, there is no supported way to inspect the stack to see what is captured on it.
-
RE: Created 8 scenes, none of them work
Um, not to insult, but @hellnbak, do you update each scene after you change the camera? If not, none of your changes will be remembered!
-
RE: Flags for onMouseMove
Here's my output from a modified version of the event reporter John was using. It covers all the combinations of mouse moves with one or both buttons pressed as well as any of the four modifier keys. I added printout of the hex and decimal values of the flags because I find that easier to understand than trying to subtract the decimal values all the time.
Key Tool Activated. "MouseMove" Flags; 256 (0X000100 = 0b000000000000000000000100000000) "LButtonDown" "MouseMove" Flags; 258 (0X000102 = 0b000000000000000000000100000010) "LButtonUP" "RButtonDown" "MouseMove" Flags; 264 (0X000108 = 0b000000000000000000000100001000) "LButtonDown" "RButtonDown" "MouseMove" Flags; 266 (0X00010A = 0b000000000000000000000100001010) "LButtonUP" onKeyDown; Key code; 131072 ( VK_SHIFT or CONSTRAIN_MODIFIER_KEY or CONSTRAIN_MODIFIER_MASK ) "MouseMove" Flags; 131328 (0X020100 = 0b000000000000100000000100000000) onKeyUp ; Key code; 131072 ( VK_SHIFT or CONSTRAIN_MODIFIER_KEY or CONSTRAIN_MODIFIER_MASK ) onKeyDown; Key code; 262144 ( VK_CONTROL ) "MouseMove" Flags; 262401 (0X040101 = 0b000000000001000000000100000001) onKeyUp ; Key code; 262144 ( VK_CONTROL ) onKeyDown; Key code; 524288 ( VK_ALT or VK_MENU or COPY_MODIFIER_KEY or COPY_MODIFIER_MASK ) "MouseMove" Flags; 524576 (0X080120 = 0b000000000010000000000100100000) onKeyUp ; Key code; 524288 ( VK_ALT or VK_MENU or COPY_MODIFIER_KEY or COPY_MODIFIER_MASK ) onKeyDown; Key code; 1048576 ( VK_COMMAND or ALT_MODIFIER_KEY or ALT_MODIFIER_MASK ) "MouseMove" Flags; 1048840 (0X100108 = 0b000000000100000000000100001000) onKeyUp ; Key code; 1048576 ( VK_COMMAND or ALT_MODIFIER_KEY or ALT_MODIFIER_MASK ) onKeyDown; Key code; 131072 ( VK_SHIFT or CONSTRAIN_MODIFIER_KEY or CONSTRAIN_MODIFIER_MASK ) "LButtonDown" "MouseMove" Flags; 131330 (0X020102 = 0b000000000000100000000100000010) "LButtonUP" onKeyUp ; Key code; 131072 ( VK_SHIFT or CONSTRAIN_MODIFIER_KEY or CONSTRAIN_MODIFIER_MASK ) onKeyDown; Key code; 262144 ( VK_CONTROL ) "RButtonDown" "MouseMove" Flags; 262409 (0X040109 = 0b000000000001000000000100001001) onKeyUp ; Key code; 262144 ( VK_CONTROL ) onKeyDown; Key code; 524288 ( VK_ALT or VK_MENU or COPY_MODIFIER_KEY or COPY_MODIFIER_MASK ) "LButtonDown" "MouseMove" Flags; 524586 (0X08012A = 0b000000000010000000000100101010) "LButtonUP" onKeyUp ; Key code; 524288 ( VK_ALT or VK_MENU or COPY_MODIFIER_KEY or COPY_MODIFIER_MASK ) onKeyDown; Key code; 1048576 ( VK_COMMAND or ALT_MODIFIER_KEY or ALT_MODIFIER_MASK ) "LButtonDown" "MouseMove" Flags; 1048842 (0X10010A = 0b000000000100000000000100001010) "LButtonUP" onKeyUp ; Key code; 1048576 ( VK_COMMAND or ALT_MODIFIER_KEY or ALT_MODIFIER_MASK ) onKeyDown; Key code; 131072 ( VK_SHIFT or CONSTRAIN_MODIFIER_KEY or CONSTRAIN_MODIFIER_MASK ) "RButtonDown" "MouseMove" Flags; 131336 (0X020108 = 0b000000000000100000000100001000) onKeyUp ; Key code; 131072 ( VK_SHIFT or CONSTRAIN_MODIFIER_KEY or CONSTRAIN_MODIFIER_MASK ) onKeyDown; Key code; 262144 ( VK_CONTROL ) "RButtonDown" "MouseMove" Flags; 262409 (0X040109 = 0b000000000001000000000100001001) onKeyUp ; Key code; 262144 ( VK_CONTROL ) onKeyDown; Key code; 524288 ( VK_ALT or VK_MENU or COPY_MODIFIER_KEY or COPY_MODIFIER_MASK ) "RButtonDown" "MouseMove" Flags; 524584 (0X080128 = 0b000000000010000000000100101000) onKeyUp ; Key code; 524288 ( VK_ALT or VK_MENU or COPY_MODIFIER_KEY or COPY_MODIFIER_MASK ) onKeyDown; Key code; 1048576 ( VK_COMMAND or ALT_MODIFIER_KEY or ALT_MODIFIER_MASK ) "RButtonDown" "MouseMove" Flags; 1048840 (0X100108 = 0b000000000100000000000100001000) onKeyUp ; Key code; 1048576 ( VK_COMMAND or ALT_MODIFIER_KEY or ALT_MODIFIER_MASK ) onKeyDown; Key code; 131072 ( VK_SHIFT or CONSTRAIN_MODIFIER_KEY or CONSTRAIN_MODIFIER_MASK ) "LButtonDown" "RButtonDown" "MouseMove" Flags; 131338 (0X02010A = 0b000000000000100000000100001010) "LButtonUP" onKeyUp ; Key code; 131072 ( VK_SHIFT or CONSTRAIN_MODIFIER_KEY or CONSTRAIN_MODIFIER_MASK ) onKeyDown; Key code; 262144 ( VK_CONTROL ) "RButtonDown" "RButtonDown" "MouseMove" Flags; 262409 (0X040109 = 0b000000000001000000000100001001) onKeyUp ; Key code; 262144 ( VK_CONTROL ) onKeyDown; Key code; 524288 ( VK_ALT or VK_MENU or COPY_MODIFIER_KEY or COPY_MODIFIER_MASK ) "LButtonDown" "RButtonDown" "MouseMove" Flags; 524586 (0X08012A = 0b000000000010000000000100101010) "LButtonUP" onKeyUp ; Key code; 524288 ( VK_ALT or VK_MENU or COPY_MODIFIER_KEY or COPY_MODIFIER_MASK ) onKeyDown; Key code; 1048576 ( VK_COMMAND or ALT_MODIFIER_KEY or ALT_MODIFIER_MASK ) "LButtonDown" "RButtonDown" "MouseMove" Flags; 1048842 (0X10010A = 0b000000000100000000000100001010) "LButtonUP" onKeyUp ; Key code; 1048576 ( VK_COMMAND or ALT_MODIFIER_KEY or ALT_MODIFIER_MASK ) Key Tool Deactivated. -
RE: Flags for onMouseMove
On Mac the flags are a (undocumented in SU) bit-map. Experimentally, 10 (2 decimal) is left button, 1000 (8 decimal) is right button. It's never been clear to me what they meant you do to with a bit-map that isn't documented!
-
RE: Full Screen on a Mac
On El Capitan it does exactly what you describe: global menu bar and dock hide.
-
RE: SkpMake crashes
When turning off hardware acceleration fixes a SketchUp problem, that is pretty sure proof that there is a problem with either your graphics hardware or its driver software. With it turned off, some operations in SketchUp will be slower. I would recommend that you see if your seller will let you trade the graphics card for one from NVidia.
Regarding the little man (or other figure), he is included in the standard template files distributed with SketchUp. To get rid of him, simply open a new file, delete him, and then File->Save as Template ( not sure how that translates to French, Enregistrer comme modèle?). Set the edited version as your default Template.
By the way, if you don't submit your BugSplat you can rest assured that Trimble will never address your problem because they will never have heard of it!
-
RE: SkpMake crashes
@erzane said:
slbaumgartner >yes I get a BugSplat (pls see attached file''
what does ''submitted the BugSplats to Trimble'' means?It means click the button at the bottom labelled "Envoyer le rapport d'erreur".
-
RE: SkpMake crashes
I can't say for certain if this is your situation, but as a rule the ATI graphics drivers are not as compatible with SketchUp as those from NVidia. The FireGL cards are actually not so good for SketchUp (your vendor likely does not know SketchUp specifically and recommended this card based on other apps).
When it crashes, do you get a BugSplat? If so, have you submitted the BugSplats to Trimble with enough identifying information that they can get back to you?
-
RE: Accessing File Locations defined in Preferences from Ruby
On a Mac the default folders appear to be kept in ~/Library/Preferences/com.sketchup.SketchUp.VVVV.plist (where VVVV is the version number starting with 2014). This is also where items written and read as defaults using the SketchUp Ruby API methods are stored. However, I have never found a way to read them via the Ruby API. The relevant keys are at root level in this plist, and Sketchup.read_default requires a first-level dictionary name as its first argument. I suppose you could resort to a low-level direct read akin to what TIG describes for the Windows registry, but I haven't tried that.
Edit: The values can be accessed via a system command such as
defaults read com.sketchup.SketchUp.2015 Sketchup.DefaultFolder.Models
That's not as tidy as an in-Ruby solution, but it should work.
Edit#2: On the Mac, these are reset by SketchUp as most recently used. So far as I know, there is no way for a user to specify them or to keep them stable.
-
RE: Accessing File Locations defined in Preferences from Ruby
The Mac does not have equivalent preference settings to the Windows file locations. That panel is completely missing from the preferences. I have no idea why...
-
RE: Enlarge Materials Color Wheel?
Indeed. But then the rest of the Mac Materials editor is a mess...
