Raspberry Pi VSG installation #1019
-
|
I run flight simulation software using OSG and would like to port the software to VSG on a Raspberry Pi 4B. I ran update and upgrade on my RPi, so it is fully up to date. I also run lots of OpenGL v4 on the RPi. I meticuously followed the instructions for Unix from https://vsg-dev.github.io/vsgTutorial/SettingTheScene/BuildingVulkanSceneGraph
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 14 replies
-
|
I don't have any experience with the Rasberry Pi, but... Can you run any Vulkan programs, such as vulkaninfo or vkcube that comes with the SDK? If so, run vsgdraw under gdb and see what the problem is. How did you install assimp? What version? |
Beta Was this translation helpful? Give feedback.
-
|
This is what I see when I run vulkinfo and vkcube. ========= ~/Projects/vsgXchange>vkcube Do you have a compatible Vulkan installable client driver (ICD) installed?
|
Beta Was this translation helpful? Give feedback.
-
|
libassimp-dev is version 5.0.1-ds0-2 |
Beta Was this translation helpful? Give feedback.
-
|
A number of questions to answer, which makes for a difficult to follow for others. Could you post one topic per thread in future to help other more easily find/read/reply. Thanks. I'll reply with one topic per post now to avoid the shush of issues causing more tangled thread. With the typo, does the follow diff look fix the error(s) you've spotted? Simply changing ${D_LIBRARY_PATH} to ${LD_LIBRARY_PATH} $ git diff
diff --git a/1_SettingTheScene/BuildingVulkanSceneGraph.md b/1_SettingTheScene/BuildingVulkanSceneGraph.md
index 669533c..fb4e836 100644
--- a/1_SettingTheScene/BuildingVulkanSceneGraph.md
+++ b/1_SettingTheScene/BuildingVulkanSceneGraph.md
@@ -19,7 +19,7 @@ First we'll set up some environment variable, for ease of use you may wish to pu
export INSTALL_DIR=~/Install
export PROJECT_DIR=~/Projects
export PATH=${PATH}:${INSTALL_DIR}/bin
-export LD_LIBRARY_PATH=${D_LIBRARY_PATH}:${INSTALL_DIR}/lib
+export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${INSTALL_DIR}/lib
# env vars that are used to find example data, and locating where to cache files downloaded from HTTP during database paging
export VSG_FILE_PATH=${PROJECT_DIR}/vsgExamples/dataI have checked this into vsgTutorial, if there are further typos let me know, or just submit a PR to the appropriate repo. |
Beta Was this translation helpful? Give feedback.
-
|
Correct, that was the typo. My errors occured after I corrected the typo. |
Beta Was this translation helpful? Give feedback.
-
|
For OpenFlight support you'll need to use osg2vsg which you'll need to build the OSG, then osg2vsg, then build vsgXchange as it will then pull in osg2vsg if it's available. This is quite a few hoops to jump through unfortunately as Assimp doesn't have a OpenFlight loader. Longer term I'd like to see an OpenFlight loader implemented for the VSG itself, rather than required osg2vsg. osg2vsg also needs a rewrite as was written in the early days of the VSG project and doesn't take advantage of all the modern VSG features like vsg::ShaderSet/GraphicsPipelineConfigurator to create subgraphs. The vsgXchange::assimp loader does use vsg::ShaderSet/GraphicsPipelineConfigurator so is more flexible, extensible and supports all the modern features like PBR, lighting and shadows. Another route for the OpenFlight support would be to build osg2vsg and then convert the .flt files to .vsgb and then load the .vsgb files in your flight simulator application. This would avoid need to link to the OSG/osg2vsg at runtime. As for getting things working on the Raspberry Pi, I don't have one myself, but I know others that are using the VSG on it. Hopefully they'll chip in here with how to get things to run smoothly. The vsg::Exception being thrown by vsgdraw is probably down to the Vulkan instance or device failing to be created. This would most likely a driver setup issue. Try running: vsgviewer vsgExamples/data/models/lz.vsgt As it'll catch the vsg::Exception and report the message to the console. Running vsgdeviceselection should also report more info. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, you suggestions to move from OSG to VSG are along the lines I intend to follow. This is the output from vsgviewervsgviewer vsgExamples/data/models/lz.vsgt
|
Beta Was this translation helpful? Give feedback.
-
|
You'll need to get standard Vulkan applications like vulkaninfo running first, then once you've sorted out the driver issues move on to the VSG examples. FYI, VkResult value -7 is VK_ERROR_EXTENSION_NOT_PRESENT: The Vulkan docs on VkResult: |
Beta Was this translation helpful? Give feedback.
-
|
and that means that the drivers are not installed, see my earlier suggestion |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I am running VSG based apps, including assimp loaded models, on an rpi 4 so it is possible! I would like to help to get the VSG up and running on your side. Let's take it step by step and could you provide means to reproduce your issue? What OS, version, etc are you using? I am using Raspbian 11 64 bit About curl, you need to install the dev package, I install libcurl4-openssl-dev |
Beta Was this translation helpful? Give feedback.
-
I am running the current Raspberry Pi OS (not Raspian) which is based on Debian. It is a 64-bit implementation.
|
Beta Was this translation helpful? Give feedback.
-
|
Since I experienced issues with assimp from the repo, I am building and installing assimp from source code |
Beta Was this translation helpful? Give feedback.
-
|
you also need to install package mesa-vulkan-drivers on raspbian 11 |
Beta Was this translation helpful? Give feedback.
-
|
The VSG doesn't emit this warning, so it'll be the driver itself flagging itself. I don't know what drives are available on the Pi so I'll have to defer to others and yourself. It may be that the driver is fine and over time will become conformant and this issue could go away, or perhaps other drivers will be available work seamlessly. W.r.t Xcb vs Wayland, I implemented src/vsg/platform/xcb/Xcb_Window.cpp early in the VSG project as that's what most prevalent on Linux/Vulkan examples back in 2018. I have looked at Wayland/Vulkan implementations in the past year and it looks relatively straight forward to implement a Wayland_Window.cpp, I haven't had the free time to implement it, but if no one else gets to it I will eventually get round to it. Could be a while though as my current tasks list is rather full. |
Beta Was this translation helpful? Give feedback.
-
|
fwiw I always see this warning too but so far I have not experienced any issue. But I have to say that I am not yet using advanced shaders or so |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the tips. =====
|
Beta Was this translation helpful? Give feedback.
-
|
This looks like an assimp version issue as it looks like mName isn't supported by the version of assimp you have on your system. It may be possible to add a #ifdef assimp version check to disable the use. Alternative you try updating or a more modern version of assimp. |
Beta Was this translation helpful? Give feedback.
-
|
I downloaded assimp from github and it builds correctly. I can now build and run vsgXconv. I will now install OSG and osg2svg and see how I go with translating OpenFlight .flt files and textures. Thanks for the suggestions. |
Beta Was this translation helpful? Give feedback.
A number of questions to answer, which makes for a difficult to follow for others. Could you post one topic per thread in future to help other more easily find/read/reply. Thanks.
I'll reply with one topic per post now to avoid the shush of issues causing more tangled thread.
With the typo, does the follow diff look fix the error(s) you've spotted? Simply changing ${D_LIBRARY_PATH} to ${LD_LIBRARY_PATH}
$ git diff diff --git a/1_SettingTheScene/BuildingVulkanSceneGraph.md b/1_SettingTheScene/BuildingVulkanSceneGraph.md index 669533c..fb4e836 100644 --- a/1_SettingTheScene/BuildingVulkanSceneGraph.md +++ b/1_SettingTheScene/BuildingVulkanSceneGraph.md @@ -19,7 +19,7 @@ First we'll set up …