Sometimes we run into bugs in production, we are not able to send anything as per company policy.

In these cases, should we report the issue, whether we have repro steps or not? If we have repro steps, the support wants to see a hip file to see the issue more clearly or avoid following a lot of steps.

If we don't have a repro case, as developers I still think it's useful to let them know a particular issue where they could identify it even without a repro case given the problem is explained clearly and especially if a solution/fix is included in the email.

So should we file bugs for these? Because without a scene file, these won't pass through the support onto the developers. So I think we are still losing out on valuable information on these that would be useful to the developers.

After all it takes time to file bugs, when most people just ignore it.

In most cases as a developer, I can still use this sort of information to identify issues and fix them.

Hey Man,

Obviously taking time away from your production is to be determined on a case by case basis. In many studios we are paid to produce images, not run quality assurance on software.

That said, I try to do everything in my power to streamline my work, and bug tracking and logging is definitely one of the most efficient ways to do this. I frequently send files, or reports to SESI about bugs that come up day to day. If I can't send a file, I'll send a step by step example for how to reproduce the bug. If I can, I may strip down a scene to just a few polygons if this helps.

Sidefx has a great support team, and they will work with you to try and track the issues down.

-j

Yes, you should still log a bug even if you can't provide a scene file. As long as you can reproduce the issue and give us step by step instructions it's all good.
That being said, if you can't reproduce it without a scene file, chances are we won't be able to either, but it's still worth logging a bug. You might want to mention in the bug that you're banned from contributing a hip file of any kind.
If your company is on our Annual Upgrade Plan, you can log the bug directly into our database. Contact your SideFX account rep for access if you don't have it already.
Thanks!

Thanks guys. I always mention that I am banned from sending anything from work, otherwise I always provide scenes from home when I can.

I just think sometimes it's useful to get this info to the developers. I will check the AUP thing, because that would be useful to get this seen by the devs and if they think it's not useful, they can close it.

jacob clark
In many studios we are paid to produce images, not run quality assurance on software.

It's worth noting that bugs do sometimes get squashed in under 2 days by SideFx, so sometimes to produce images it pays to send in the bugs.

Ok it seems like submitting bugs via company is a length process that goes through a lot of forms because of NDAs. So I will post the bug here so the developer can see and possibly fix the issue.

Flatten Padding of Particle Fluid Surface SOP doesn't always work

Sometimes when you use flatten and padding, you get an line/edge between the original surface and the padding. It's not water level issue, but actual indendation between the surfaces.

I just dived inside the HDA and fixed the issue by setting:

4 * particlesep

from the original:

2 * particlesep

in ./FLATTEN/erode_bbox node

But basically “2 * particlesep” doesn't work for every case.

You can log bugs directly with SideFx via the Support menu. You don't need to use the Company account.

Yes I know but they don't log this unless I have a scene file or repro steps, which I don't.

the bug will still be logged even of you don't have a scene file
it WILL NOT be logged if you post it to this forum.

I don't know if it's logged, as I don't have a bug ID like others, only submit ticket ID.

I think you get a ticket, then when support confirms that it is a valid issue etc, they add it to the DB with an ID#

That's what I mean. It wasn't confirmed to be a valid issue because I don't have a scene file so this bug will not reach the developers.

Either way I did everything I can.

what was the submit ticket ID?
I'll check to see what it's status is.

#38290

looks like we'll need a file or a way to reproduce on this one…