Sometimes it’s not what we say. Sometimes it how we say it, the delivery of the message.

Sent you guys some info privately and filed bug report.

Literally 15 min in Solaris, just messing with materials in material linker (AMD materials and editing them). Dozens of errors thrown. After 15 min of just adjusting shaders, all my snapshots disappeared and all the rules in material linker disappeared...

We're talking basic, basic stuff.
I'm on win11 and RTX3090TI... all updates from Windows, latest NVidia studio drivers, build 20.5.328. Damn, I even once again renamed my home directory (and had to recreate all my desktops, viewport settings, shortcuts).

Here's another random sht... I have been rendering solaris scene. Working fine, no issues. Went to Save, yes, save, saved this as another scene file a different name (same directory)... Snapshots disappeared, all nodes have '!' on them now. With 'failure to cook template geometry'. No crashes, just "Invalid source /obj/TERRAIN/convertheightfield1/repeat_end1.
(Error: Failure to cook template geometry.)." When I quit Houdini and restart - seems to load fine.

Just brutal. I haven't been able to use Solaris for more than 10-15 minutes without crashing or some sort of issue.

Nodes stop to cook, Karma freezes at 99 and have to force restart Houdini, can't undo nodes deletion (e.g. material linker), segmentation faults, material linker rules disappear... it literally feels like alpha. Less stable than initial Solaris release.


According to QA, when I send them my system details - everything looks fine..

Problem is - I can't just repro most of it... it just randomly goes to sht after doing basic stuff for 10-15 min.

I'm actually going to go back to H20 as Solaris in H20.5 is completely unusable for me.

alexeyvanzhula1984

LukeP
On the other side - this thread was really about Solaris instability that I have been experiencing.

Yes, I wouldn’t want to write this in this thread, but I saw responses from developers here, so I couldn’t hold back. When I create threads about issues, I generally don’t get any responses. Maybe I touch on uncomfortable topics, or maybe they just find me unpleasant—who knows.

Keep talking about them. SideFX is very responsive. You'll get a response eventually (which is usually a closed thread, but if you're lucky you might get a forum ban!)

raincole

alexeyvanzhula1984

LukeP
On the other side - this thread was really about Solaris instability that I have been experiencing.

Yes, I wouldn’t want to write this in this thread, but I saw responses from developers here, so I couldn’t hold back. When I create threads about issues, I generally don’t get any responses. Maybe I touch on uncomfortable topics, or maybe they just find me unpleasant—who knows.

Keep talking about them. SideFX is very responsive. You'll get a response eventually (which is usually a closed thread, but if you're lucky you might get a forum ban!)

Everything has already been said.

Thanks for the bug reports. With a proper bug with your system info and steps to reproduce the issue, the bug can be assigned to someone and our developers can nail down the issue and fix it. This is the way.

Forum posts, however, are not the place to report bugs. I'm pretty sure most of you know this by now (it's in a sticky note at the top of each forum that says READ THIS FIRST) but are posting bugs in the forums anyways, likely out of frustration and in an attempt to raise the priority of an issue. This is not the way. This thread is now locked. Further posts in this vein will not just be locked. They will be deleted. Repeat offenders will be banned.