Rhino 8.2: Bug in Push Pull?

[bimolicense (Bimo Adi Prakoso)]

Hi All.

I’d like to report a possible bug in latest Rhino SR (8.2).

Push Pull seemed to work well using Rhino 8.0 with duplicated object under recorded history. It broke the history in Rhino 8.2.

[theoutside (Kyle Houchens)]

thanks- seeing that here too.

https://mcneel.myjetbrains.com/youtrack/issue/RH-79305/push-pull-history-boken

[Stephen_McL (Stephen)]

Hi there,

Has anyone else used the PushPull function and then a split second later the whole design disappears?

Using a Mac

Thanks

[theoutside (Kyle Houchens)]

no, can you reproduce this or is it random?

[Stephen_McL (Stephen)]

Hi Kyle,

It happens every time I work on a complex design that has been BooleanUnion in Rhino 7.

It does not happen when I BU 2 simple shapes.

I did a video of it happening but it is too large to attach.

Thanks

Steve

[Stephen_McL (Stephen)]

Hi Kyle,

Video for you.

[theoutside (Kyle Houchens)]

I’m wondering if there is some history weirdness going on… try historypurge = all

if not, can you make a smaller part that fails and send it to us so we can get it to the dev team?

[tshine]

I get the same disappearing act when the tool tips show up on a floating palette. V. annoyig.

[theoutside (Kyle Houchens)]

can you send the surfaces from that file so I can get them to the dev team for debug?

send to tech@mcneel.com

[theoutside (Kyle Houchens)]

that feels like a different problem, can you send a file and a screen recording of your issue as well?

send to tech@mcneel.com

[tshine]

The disappearing happens randomly with every or most files. Quit and restart clears it for a while.

I included this in a long list of bugs previously. All the rhino windows disappear, but R8 is still running. My grey finder screen becomes visible. The windows are restored by clicking in R8 icon in the dock. Here is the video:

“Sorry the file you are trying to upload is to big” - I’'ll email it.

Here is the prior post:

Rhino 8 Bug Report

Here is a list of bugs from using R8 (8.2.23346.13002, 2023-12-12) on MacOS (13.6.3) as they happened - no particular order: Commands line autocomplete is center justified, should be left justified as in R7. I typed “Ext” and got this: [Text should be left justified] The “esc” key does not dismiss the "Show panels…‘’ pop-up window. Only by clicking off the panel can it be dismissed. [esc doesn't dismiss show panels] The “Panel” panel is missing making paneling difficult. ["Panel" pa…

[tshine]

Attachments available until Feb 14, 2024

Video and sys info:

Click to Download

David Copperfield.mov
25.3 MB

Click to Download

Untitled.txt
5 KB

[theoutside (Kyle Houchens)]

I’m on sonoma on an M1 max processor and cannot repro this behavior on my machine, is updating your OS an option for you? If so, I’d be curious to see if it’s an OS or rhino issue.

this is definitely a different issue than the OP. Please open a new thread for this issue or continue it via our tech support email tech@mcneel.com so we do not hijack the OP post.

[tshine]

Updating is not possible, but more posibly related palette/container funkiness here:

Tear off palettes (containers) are sadly orphaned in R8 (8r4)

Containers (palettes/tear-off tools) become orphaned when a windows is closed, leaving behind a sad, empty round rect blotch. Tear-off toolbars also change with multiple windows. This is new to R8 for Mac. On R7 the tear-off toolbars were persistent, parented to the menubar not the window. In R8 they are parented to the ?window, leading to strange behavior. [orphan]

[bimolicense (Bimo Adi Prakoso)]

Is anyone still experiencing this bug? My rigs are still giving the same broken history when doing PushPull. The version is Version 8 SR5 (8.5.24072.13001, 2024-03-12). Tried to uninstall it and reinstall Version 8 (8.0.23304.9001, 2023-10-31), Pushpull works again without breaking the history.

However Version 8 (8.0.23304.9001, 2023-10-31) generates incorrect output scale when printing layout as PDF.

[Joshua_Kennedy]

Hi, PushPull is supposed to break history. PushPull changes the polysurface enough that history descendants can’t reliably track pieces on it. While in this case Duplicate doesn’t need to know about the individual pieces of the polysurface we haven’t made it smart enough to keep track after PushPull.

[bimolicense (Bimo Adi Prakoso)]

Hi Joshua.

Really appreciate the reply.

Strangely with Rhino 8.0 (8.0.23304.9001, 2023-10-31), PushPull never broke the history when I experimented with these scenes.

If it’s meant to be like that while it was having no issue, I believe all of would miss the feature when it gave more than it was meant to function. I still have hope that you awesome developer guys to keep PushPull the way it was functioning and showing. Why break it when it’s actually not broken?

[Joshua_Kennedy]

Those are really fantastic models and renders! Super cool to see how PushPull being used! Thanks for sharing

@bimolicense

Why break it when it’s actually not broken?

Well unfortunately it was broken or at least caused issues elsewhere. This is the issue that prompted the change. Something like Copy is fine but DupBorder would jump around the object as it was PushPull’d. Then any extrusions created from that duplicated border would also act strangely.

With PushPull what history commands were you using that I broke? It’d be nice to see what different commands I can possibly handle. I opened an issue here to investigate some solutions. Hopefully I can figure something out.

[bimolicense (Bimo Adi Prakoso)]

Thanks Joshua. The whole building construction and its interior were creating using PushPull as I experimented with modeling technique and the scene are all in geometries, even the plants and tree. Using PushPull, I managed to construct the house (plants and trees are from libraries) including the material mapping and emissive light objects in 2 hours with some pizzas and apple juice

The interior scene was quite easy to finish as I was experimenting with AMD ProRender for both scenes. Rendering result in ProRender is amazing. However, ProRender Library Material with Caustic would immediately crash Rhino when rendering the scene.

PushPull instantly breaks history in Rhino version later than 8.0.23304.9001, 2023-10-31, but works totally fine in 8.0.23304.9001, 2023-10-31. It will break the history in a simple case of just creating a cylindrical hole on a cube, using circle on a cube’s surface, while duplicating the cube.

I actually have a Wishlist which contains:

1. PushPull will never break the history
2. Latest AMD ProRender, fully implemented in Rhino 8, as it carries amazing potentials.

The solid requirement for AMD ProRender is, we gotta have at least 6GB of graphics memory. Not telling that 4GB doesn’t work, but when it requires more than 4GB graphics memory, Rhino will immediately exit. It works just fine with my RTX A5000.

[Joshua_Kennedy]

@bimolicense

The interior scene was quite easy to finish as I was experimenting with AMD ProRender for both scenes. Rendering result in ProRender is amazing. However, ProRender Library Material with Caustic would immediately crash Rhino when rendering the scene.

Funnily enough, I did the ProRender integration for Rhino too. Which material specifically in the library is crashing?

@bimolicense

Latest AMD ProRender, fully implemented in Rhino 8, as it carries amazing potentials

What features are missing?