-
Notifications
You must be signed in to change notification settings - Fork 98
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
Unity3D backend crashes randomly or on scene load. #28
Comments
This crash seems to be unity related. Could you please post the unity player log? |
|
Looks like something is going NULL in the renderer. Does |
I just ran it and it look successful. (unless I needed to let it run longer) here is the output (besides the funny teapot image window that is)
|
Nvidia Driver info: |
Are you using Ubuntu 16.04? Which GPU are you using? |
Description: Ubuntu 16.04.5 LTS Geforce RTX 2070 |
Hi @MattAxG, Sorry for the wait. This is actually a non-trivial issue to solve. We're trying to replicate the issue on our side so that we can provide you with a solution. Our current hypothesis is that you have a specific nvidia driver/vulkan API combo that has a hidden bug. We've got the following combinations to work: Ubuntu: 16.04 and Nvidia Driver: Best, |
@MattAxG can you verify your FlightGoggles version from the splash screen? It should say |
v2.0.0 |
OK, we're going to try to isolate a few variables. Could you please try downloading this linux binary and running it? It will not connect to ROS, but it will tell us if the renderer is broken or the ROS interconnect. Note, it might take a while to load. |
Done. Captured the terminal output here: Here is the There was also some scroll in the terminal that might be useful here |
Were you able to see an image with this executable? Were you able to look around with the mouse? It’s hard to tell from the output whether you were able to see the scene. |
That was the first run, it behaved very similar to the v2.0.0 release, open for a few seconds then closed. I did run it again by double clicking the icon in the file manager instead of launching by command line. This gave me about 4 minutes of "flying around" before the window closed. |
Here is the Player.log for the longer run. |
Do you think it is related to either [V2] [Unity 2017.4] Post-Processing Stack causes crash on Linux with latest Nvidia driver #592 |
Hi @MattAxG, This issue is a bit odd. With the debug build, you have been able to run the Unity3D backend for up to 4 minutes before crashing. This suggests that the error is coming from some hardware/software/driver interaction specific to your OS install or development environment setup. The difference between running the executable from command line and double clicking the executable is also concerning. Perhaps something odd is happening in your In the We're going to build another set of binaries for you using a different version of Unity3D to see if that fixes the issue. Stay tuned! In the meantime, you might want to install this framework on another computer or hard drive. It is very possible that another computer/OS install would work. Best, |
Sadly @MattAxG, I don't think that the issues you linked apply to this issue. We are using unity3d version |
Hi @MattAxG, We were able to reproduce an error similar to your original error using Unity3D version To run this with the existing ROS framework, please run the downloaded binary and then run Best, |
Hello. I had the same issue @MattAxG is describing. I jus tried the binary you provided in the last comment and now I am able to get reliable rendering for more than 4 minutes. I have been running it for 20minutes and seems to have no problem. Input from keyboard is working. My system is: Vulkan smoke test passes just as described by @MattAxG. rostopic echo for /uav/camera/left/image_rect_color and /uav/camera/left/ir_beacons is now publishing messages for each. I should mention that I have Unity3D Version 2018.3.0f2 (6e9a27477296) Personal installed in my computer. Since it seems to be an issue related to Unity I though this info might be helpful. |
Wonderful, thanks for the feedback Juan!
…On Mon, Feb 11, 2019 at 10:01 PM Juan ***@***.***> wrote:
Hello. I had the same issue @MattAxG <https://github.com/MattAxG> is
describing. I jus tried the binary you provided in the last comment and now
I am able to get reliable rendering for more than 4 minutes. I have been
running it for 20minutes and seems to have no problem. Input from keyboard
is working.
My system is:
Intel® Core™ i5-8400 CPU @ 2.80GHz × 6
GeForce GTX 1050 Ti/PCIe/SSE2
NVIDIA-SMI 396.37 Driver Version: 396.37
Ubuntu 16.04.5 LTS
Vulkan smoke test passes just as described by @MattAxG
<https://github.com/MattAxG>. rostopic echo for
/uav/camera/left/image_rect_color and /uav/camera/left/ir_beacons is now
publishing messages for each.
I should mention that I have Unity3D Version 2018.3.0f2 (6e9a27477296)
Personal installed in my computer. Since it seems to be an issue related to
Unity I though this info might be helpful.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOwrotf1iRCbDsrnSs8Frn6vlRyqEf2ks5vMi5vgaJpZM4ayrZR>
.
|
Hi, I am experiencing the same issue with the following system: Intel Core i7-4790K I will try the new binaries tomorrow when I get the chance. Just wondering, would upgrading Vulkan to 1.1.73 help, or is the cause of the problem not related to Vulkan? I believe I'm on Unity3D Version 2018.3.0f2 just like @juanmed. Also, I noticed in my player log that my Vulkan renderer is set to [Intel(R) Haswell Desktop] instead of my GTX 980 Ti. Do I have to configure it to use my GPU somehow? Thanks! |
I don't believe this issue was related to Vulcan. The player log suggesting that the Vulcan renderer is set to intel sounds concerning. Are you sure |
Hi @varunmurali1, yes I am sure nvidia-smi sees the GPU. I can upgrade to a newer driver, but could you please suggest a version that is known to work? Thanks. |
I am currently using nvidia-410. Could you please try that version? |
Hi I have same issue. My system is: Vulkan smoke test passes well. Do I have to upgrade nvidia driver or GPU? |
I suspect that a GTX 750 Ti will not be able to successfully render using FG. Typically, you want to use a GPU with >= 4 Gb VRAM. We are considering the possibility of releasing a version that will be able to render on less capable GPUs by sacrificing quality. Please stay tuned for this! |
I have been working with this version for a few hours. Seems to be perfectly stable. Thank you for the quick help. |
That’s fantastic to hear! Glad it works for you. |
@koolmoo have you had any luck with the new non-multithreaded binaries or with the new NVidia driver? |
@Winter-Guerra I updated the drivers to 410.78, but I'm not sure how to run the new binaries. Do I just run the FlightGoggles.x86_64 executable from wherever I unzipped it, or do I need to copy all the contents to catkin_ws/devel/lib/flightgoggles and overwrite the existing files? I tried just running the executable, but the program closed as soon as it opened. Then I ran Let me know how I should proceed. Thanks! |
Looks like it is crashing on startup @koolmoo. Could you please post the player.log of the new executable? The location of the log is in the terminal printout. You can run it from anywhere and then use the same roslaunch command you used above. |
Hi all I'm having the similar issue as @koolmoo with a crash at startup. My setup is: I've tried Nvidia drivers 384.130 and 410.78 ( The output I get is: |
Yeah I definitely think @jeffcyu and I have the same problem. Here is my player log for reference: Thanks! |
@jeffcyu @koolmoo I noticed something from both your player logs, you appear to be using the multi-threaded unity executable, not the single threaded version. Can you run the new executable after setting the environment variable Since this issue appears to be unrelated to the original problem with multi-threading could I suggest that we open a new issue with Vulkan failing to select the GPU but instead defaulting to the Intel icd? |
Hello, I had same issue. |
@varunmurali1 Hey that did it! After setting that environment variable and running the new binaries, the FlightGoggles simulator opens and shows a "waiting for client" screen. My player log now says that the Vulkan renderer is my 980 Ti GPU. Also, running the external renderer command opened ROS with the simulator image displayed. Thanks so much! Quick side question: I heard there was a way to use Xbox controllers for teleoperation, but is it possible to connect an RC transmitter (e.g. FrSky Taranis) to control the drone? |
@yonghee93 @koolmoo glad it works for you. @koolmoo At this time, RC transmitters are not supported, sorry. |
The fix with the new binary works! Thanks @varunmurali1 |
Great! Glad it works! |
Hello, Previously I reported I had the same issue as @MattAxG. Using the v2.0.0_no_multithread binary I am able to connect and fly the drone ONLY when launching teleopExample.launch. When I try to launch core.launch there seems to be an issue and RViz keeps display "No Image" indefinitely. This repeatable. While the v2.0.0_no_multithread binary is running, if I relaunch and close teleopExample.launch it alwasy connects and works, whereas the same process with core.launch never works and displays "No image". This are my log files: I am not sure if this is the correct place to write this. Let me know if I should open an new issue. |
Hi @juanmed, it looks like the dynamics and render engine were waiting for control input before starting. Sorry about that, I've pushed a patch that fixes this issue a few days ago. Here are some commands that should get you up and running. cd ~/catkin_ws/src
wstool update
roslaunch flightgoggles core.launch In the future, please make a new issue for new issues. This is not the correct thread for this. |
Hi. Thanks for the indications. Also, I found it is necessary to rebuild the workspace in order for it to work, so the commands that worked for me were: cd ~/catkin_ws/src wstool update cd ~/catkin_ws/src/flightgoggles catkin clean flightgoggles catkin build roslaunch flightgoggles core.launch After this both core.launch and teleopExample.launch were working. Thanks. |
I have tried downloading this executable and running it, below is the last few lines of the trace
Am I doing something wrong? Kindly, help! |
Hi, I'm just getting started with Flgihtgoggles.
My setup is; The Player.log like produced says the driver is incompatible but I don't have clue how to go about fixing that or if that even is the issue. `Desktop is 3840 x 2160 @ 60 Hz (Filename: Line: 634) ~ Any help would be great, thanks |
@benkmoore What is the driver version you're using? You can check that using Also, make sure it satisfies the requirements mentioned here |
Hey @venky-intel, 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] I can't find my exact graphics card in the vulkan compatibility list but the GeForce GTX 750 Ti is closest to it and is compatible so if that is ok then I think my system meets the requirements. In additional drivers section of Software & updates I'm currently using: But it also has an option to select NVIDIA binary driver - version 384.130 Any advice? cheers |
Hi @benkmoore, Please try using the Nvidia binary driver. The open-source driver is not distributed by Nvidia and is generally incompatible with high-end 3D graphics rendering. Please also make sure that you are using flightgoggles renderer binary versions v2.0.3 or v2.0.4-b1 and have installed If you are still having trouble, please open a new issue. Your issue does not seem related to this thread. Thanks, |
When launching via
roslaunch flightgoggles teleopExample.launch
or with
roslaunch 'flightgoggles teleopExample.launch use_external_renderer:=1
... the renderer will appear but close almost immediately.
The following message is returned.
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
When launching without the use_external_renderer:=1 argument you can also see the following messge
[uav/flightgogglesRenderer-6] process has died [pid 19209, exit code -6, cmd /home/myws/catkin_ws/devel/lib/flightgoggles/FlightGoggles.x86_64 __name:=flightgogglesRenderer __log:=/home/myws/.ros/log/a8fef8a0-2c98-11e9-90f2-002522d2019b/uav-flightgogglesRenderer-6.log].
log file: /home/myws/.ros/log/a8fef8a0-2c98-11e9-90f2-002522d2019b/uav-flightgogglesRenderer-6*.log
When I dug into the log file it pointed me to another log (Player.log) in the unity3d.
Player.log
Possibly related:
When I attempt to run the roslaunch flightgoggles core.launch instead I get similar behavior to the other ticket "RViz says "No image" #27"
The renderer (FlightGoggles unity window) stays open but continues to show the "waiting for connection from client"
The third_person_drone_follower.rviz window continues to show "No Image"
rostopic echo for /uav/camera/left/image_rect_color and /uav/camera/left/ir_beacons show no messages for those topics.
The text was updated successfully, but these errors were encountered: