Iam making a model (it is 12mb) in sketchup and when I want to start enscape to render, it loads a few moments and then sketchup and enscape crash, it happens with this project nothing else, then I try another smaller one and it renders without problems and in quality ultra
Every time I am working on a heavy model (around 200 MB which is a regular model size in pro usage) and feeling heavy on SketchUp, when I try to get an ultra-quality render I get this error and escape crashes.
I used to get this error and I think there was sth wrong with the version of the GPU and Windows updates which I think I resolved, but after a while, the error has come back, and exactly when it gets close to a deadline it keeps crashing. I had a very important presentation last night and unfortunately, I had to export all files in High-quality instead of ultra-quality. The weird situation is that I tried again today and everything was good I could export some good ultra qualities but after a couple of shots the error popped up again. I always try to export a test in HD size before going to a higher size but this error keeps popping even on HD image size.
note: The error always happens on ultra mode / the size of the image does not matter(at least on HD and above) / sometimes I do not get the right colors and reflections even when the render is going okay.
I have a 3070 8gb GPU and my models are HEAVY... in size, poly count, lots of lights and lots of vegetation proxies
And I never turn off RT
the only thing I turn off is Raytraced Sun Shadows and Rest Mode
It was never like this when I'd previously tried RT so, 1, hats off to the Enscape team for making such improvements and 2, the dunce hat for me for assuming it was STILL a memory hog and not trying it out sooner,
hypercube please send feedback with log files included and we'll be able to tell you more about what's going wrong.
If things improved with turning off ray-traced sun shadows it's indeed hinting on that it might be memory related, especially if you have lot's of high poly geometry in your project. Another cause of high memory consumption with rt shadows is animated vegetation (as it requires unique geometry for each animated asset) - setting wind strength to 0 might also help in this case.
Paul Russam glad to hear you're seeing improvements. There have indeed been a lot of quality improvements exclusive to hardware ray tracing in the last releases It does require more memory than the software ray tracing implementation, as it simply considers more geometry for GI and reflections.
I just tried the cordoba method (especially thanks) and it looks like it is doing well. That's sad I have to turn ray traced shadow off... but way better than crashing every time, especially in critical situations.
PS2: restarted Enscape on tried RT on again and started from a very low size like HD and moved to the top(ultra HD) and worked fine again. It is like we are talking about some other serious issue, not the RT only.
An instance path can only be opened if the instances are not locked. This also include instances of the same component definition that are not on the given path. A definition cannot be edited if any of its instances are locked.
Since changing the active entities in SketchUp also changes what coordinate system is used, entities can't be modified in the same operation as the active entities changes. The API handles this automatically by starting and committing transparent operations as needed.
Add a text note to the Model. The position of the note is given as relative window positions between 0 and 1. For example, the following command would create a note that start 1/10 of the ways down the screen from the upper left corner of the window.
the AttributeDictionaries object associated with the entity, or nil if there are no attribute_dictionary objects associated with the model. Care must be taken if nil is returned, for example: invoking attribute_dictionaries.length will throw a NoMethodError exception, not return 0.
Returns the Sketchup::AttributeDictionary object that is specified by name. If the model does not have an attribute dictionary that corresponds to name, returns either nil, or a creates an attribute dictionary. If the optional second argument is true, and there is no attribute dictionary that corresponds to name, a new attribute dictionary is created.
When given an array of IDs, an array is returned with a 1:1 mapping to the input arguments. This array may contain nil values if some ids were not found. You cannot look up a mix of entityIDs and GUIDs in the same call.
The get_attribute method gets the value of an attribute that in the AttributeDictionary with the given name. If no value is associated with key, or if the model does not have an attribute dictionary specified by name, the optional third parameter will be returned.
the value for a given key in the given dictionary if a value exists; the default value if a defaultvalue is provided and the value does not exist; nil if the value does not exist and no defaultvalue is provided.
The guid method retrieves the globally unique identifier, in the form of a string, for the Model. The guid will change after the model is modified and saved. The Model guid is stored with the SketchUp file; it will not change if the file is moved to another computer.
The latlong_to_point method converts a latitude and longitude to a Point3d object in the model. It does not actually work with a LatLong object, but operates on a 2-element array. The returned point will always be on the ground (z=0).
A ray is a two element array containing a point and a vector [Geom::Point3d(), Geom::Vector3d()]. The point defines the start point of the ray and the vector defines the direction. If direction can not be normalized (e.g. direction = [0, 0, 0]), direction is taken as a point the ray intersects.
first value is a Point3d where the item that the ray passed through exists. The second element is the instance path array of the entity that the ray hit. For example, if the ray hits a face that is contained by a component instance the instance path would be [Component1]. If the ray hit a
An optional boolean, added in SU8 M1, indicating whether or not to consider hidden geometry in intersect computations. If this flag is not specified, it defaults to true (WYSIWYG) - i.e. hidden geometry is not intersected against.
The select tool is activated if you pass nil to the select_tool method. You must implement the SketchUp Tool interface to create a tool, prior to calling this method, and then instance the tool implementation and pass the object to this method. If you attempt to set the select_tool to nil in the initialize method of a tool you have written, it will be ignored.
This method retrieves a Selection object for the model, containing the currently selected entities. The entries in the selection list are not necessarily in the same order in which the user selected them.
The default datum is WGS84. You can use the method list_datums to get a list of all of the datums supported in SketchUp. If you pass an invalid datum to set_datum, set_datum returns the default datum.
Starting with SketchUp 7.0, there are three additional booleans that one can pass in when starting an operation. It is recommended to always set disable_ui to true. It's left to false for default for compatibility reasons.
if set to true, then SketchUp's tendency to update the user interface after each geometry change will be suppressed. This can result in much faster Ruby code execution if the operation involves updating the model in any way.
Deprecated! if set to true, then whatever operation comes after this one will be appended into one combined operation, allowing the user the undo both actions with a single undo command. This flag is a highly difficult one, since there are so many ways that a SketchUp user can interrupt a given operation with one of their own. Use extreme caution and test thoroughly when setting this to true.
if set to true, then this operation will append to the previous operation. This is particularly useful for creating observers that react to user actions without littering the undo stack with extra steps that Ruby is performing.
I have a SketchUp model which I have created by importing three other model files. I want to update one of the three underlying model files. If I edit the model and physically import again, I have to spend the time to physically positioning the model again. Is there way to change the underlying model and the higher level model gets updated automatically?
Whenever you make changes to the aComponent.skp file, all you need to do is go into your workingFile.skp and find the component you loaded (I made one called weirdThing here) in the OUTLINER, not the Component window.
Not sure if this is a programming question or user question, but if it's programming question then you can use DefinitionList#load to load the new SKP file, then use ComponentInstance#definition= to replace the instances for the definition you want to replace.
While SketchUp doesn't link models and you can't automate changes from one model to another (without a plugin anyway), there is a way to replace a component with a different one. Are you comfortable using the Ruby console? If so, do the following (note that this assumes your objects are components!):
That should replace the old component with your new one. You can now delete the object you imported earlier. It would probably be a good idea to purge your model too.Note the replacement uses the old instance's coordinate axis location. As long as these are the same model, just with some edits, you shouldn't have any trouble.
Hello, I imported a Sketchup file in Revit by first exploding it in Revit > export to 3D Cad > putting all on same layer en exploding > import in Revit. When I want to make a section through this model and my building, the section of the sketchup model appears very weird....
So my question is how can I make proper sections in Revit with the sketchup model in the background?
In the image you can see that the brown lines are the sketchup model, my building is partly selected (blue). I actually made a section through my building, but sketchups model stays in front of it....
+
I see lines, yellow, which are not visible in sketchup because I erased them with shift+erase. Why do I see them in revit?
3a8082e126