-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unity crashes when playback recorded file #2307
Comments
I updated to the 2.16 version and upgraded the RS firmwares to 5.10.3.0. I can record but the playback crashes everytime in Unity. This is quite a problem cos I would like to use the post production effects that are integrated since the 2.15 version. Only the 2.14 works properly. Tried it on 2 different PC (windows 8.1 and 10). I played the recorded .bag file on the native RS viewer and it worked well. I think the problem could come from the Unity playback system. |
Please help :( |
[Realsense Customer Engineering Team Comment] This issue can be reproduced. Will further check internally. |
thanks |
Hi, Any news of a patch so far ? Best |
+1 for that, having the same issue. Unity 2018.1.6f1 |
I tried again with the 2018.1.6f1 version. The problem is still the same. Is it possible to do something ? |
[Realsense Customer Engineering Team Comment] |
Just tried downloading the source for version 2.14 and compiled the unitypackage, still the same issue. |
[Realsense Customer Engineering Team Comment] What's your unity/firmware versions and test steps? record and playback ros bag file both in Unity? I didn't see this issue on 2.14. |
This issue can be reproduced, we will provide a fix soon. |
@RealSense-Customer-Engineering I'm on Unity 2018.1.6f1, using firmware 05.10.03.00. I had tested previously with a recording made on Realsense Viewer, but now I tested it with a recording made in Unity and it crashed as well, even though it seems that it played back more before crashing. |
@matkatz Do you have any time estimate on this fix? I'm currently working on a project during part of which I won't have access to the physical devices, so the ability to use the recordings would be essential in my workflow. Is there anything we can do to help on this as well? |
@RealSense-Customer-Engineering just an FYI: reinstalled the SDK v2.14.1 and playback is working properly now, so I can go with that until we have the correction for the new versions |
@velenoise You're right. The problem is I would really need to use the filters. They're integrated since the 2.15 version. :/ |
I Simply would like To tell I opened this thread 2 month ago. Do you have the release date of the patch ? Or is there another problem ? |
I had the same problem. In the latest release the issue seems to be fixed. |
[Realsense Customer Engineering Team Comment] How does v2.16.2 work for you? |
Hi, The record and playback seems to work but the RSdeviceinspector.cs script doesn't seems to work. The real interest since version 2.15 is playing with filters. If we can't use them. We came back to 2.14 version. |
I opened the RSdeviceinspector.cs script. Inside there's a fonction : private IEnumerator WaitForDevice() And there is this line : //rsdevice.OnStart += onStartStreaming; I just reactivated this lign. Now it works. |
OK ! Multicam rec and playback now integrated. The unity session is still fragile and crashes from time to time but not systematically when playback. It crashes when I stop the game from time to time. I could use the decimation filter and some other too. Now let's play. Please work on optimising the pointcloud in Unity and stabilising the session. Case closed Thanks FT-XR |
Hi, Thanks |
In the 2.16.3 version, you just need to duplicate the device and the pipeline. Then create a new material for the mapping and link it to the copied elements. |
Hello,
I work on Unity/PC with the latest version (V2.15) of the wrapper.
When I record a file (record mode) and then play it back. Unity crashes.
It didn't happen with previous versions.
What do you think about it ?
Best regards
The text was updated successfully, but these errors were encountered: