Scolring - Forum

Bonjour,

Quelle est la carte graphique utilisée ? Le pilote est-il à jour ?
Vous pouvez tester de passer openspace3d en directx pour contourner le problème.

Sur la version portable, ouvrez le fichier usm.ini dans notepad.
Modifiez OpenGL par DirectX à la fin du fichier et relancez os3d.

Hello,

some video tutorials are planned but are not ready yet ^^

Here the fastest way to use the VR components in OS3D for any head set :

- Import your model.
- In the plugITs groups tab > right click and choose "import dynamic template" > "Generic VR" > "Vr controllers" >"Hands VR controllers - hands tracking enable"
- position the "dummy_start_pos" to set the initial player position.

Test and export the app on the quest, pico...

Welcome back

first you'll have to use a raspi 3, raspberry 4 is not yet supported.
Then you can use standard augmented reality marker with pictures to identify an image and trigger the explanations.
For the robot you can find electronic examples in the RPI plugiITs documentations

Hello, you can use the mouse plugIT to get the 3D position projected in scene.
And then update the position of a node from the mouse position using an object position plugit.

hehe
oui le pathfinding est une grosse partie, le plus complex est de trouver un algorithme compatible avec le moteur physique.
Peut être qu'une 1ere évolution serait d'utiliser un moteur physique plus générique comme bullet par exemple.

Le truc avec le instantiate c'est qu'il charge les resources et les scripts. en fonction de la complexité de ces éléments cela peut être plus ou moins lent a charger / décharger. Les ressources sont aussi placées dans un nouveau groupe et elles sont donc dupliquées. Cela pour permettre la modification d'un modèle sur un changement de texture ou de matériaux par exemple.
Il faudrait en effet réfléchir à un plugIT items qui prendrait un modèle 3D et des nœuds de placement, il se chargerait de dupliquer le modèle. Avec des effets optionnels comme la rotation et gérer le 'pickup" / "reset".

Pour MacOS, j'ai encore un vieux Mac mini, j'attend un modèle plus récent (pas sur qu'il soit M1) pour pouvoir tester et compiler dessus.

en tout cas tu peux lui demander de t'expliquer le code d'un plugIT ^^ il comprend que c'est pour OpenSpace3D.
Impressionnant quand même vu que je ne lui ai pas donné de context.

This code appears to be written in OpenSpace3D, a scripting language used to create 3D environments and games.

The code defines a number of functions that perform different actions when called.

The "deleteOb" function is a callback function that is called when an instance of the plugin is deleted. It simply returns 0.
The "cbDisable" function is a callback function that is called when the plugin's "Disable" action is triggered. This function takes in several parameters, such as the instance of the plugin, the sender of the action, the action itself, any additional parameters, and a "p" variable. Inside the function, it uses the "state" variable from the "p" variable and checks if it is already disabled. If it is, the function ends, otherwise it will set the state to 0, gets the session view and default viewport, and disables the SSAO (Screen Space Ambient Occlusion) effect. Then it sends a "Disabled" event to the plugin.
The "cbEnable" function is similar to the "cbDisable" function, but it enables the SSAO effect instead of disabling it when the "Enable" action is triggered.
The "cbSetState" function is called when the "Set state" action is triggered. It takes in a parameter and if it is not empty or nil, it will check if the parameter is less than or equal to 0 and call the "cbDisable" function or the "cbEnable" function accordingly.
The "newOb" function is a callback function that is called when a new instance of the plugin is created. It gets the initial state of the plugin from the instance's parameters, gets the session view and default viewport, sets the SSAO effect to the initial state, and registers the "Enable", "Disable", and "Set state" actions with their corresponding callback functions. It also sets the "deleteOb" function as the instance's delete callback.
The "IniPlug" function is called when the plugin is initialized, it registers the "newOb" callback function, sets the plugin editor to "dynamicedit" and returns 0.
In summary, this code is a plugin for OpenSpace3D that allows the developer to enable/disable the SSAO effect on the default viewport and provides actions to control the state of the effect.

If the scene rendering freeze with D3D11, check that the 3D models have texture coordinates and normals in mesh.
if you assign a material with light or texture on the model that don't have this informations, this will make the rendering to fail.

Hello, OK I will check that

Hello,

the commit is about optional OpenXR extensions like hand tracking or passthrough for now.

OS3D extensions are just plugITs

Thanks for the report, indeed I don't think I will be able to correct the D3D11 display Bugs on old demos for now, it must be because of the mimap generated in textures.

I'll check for the freeze anyway.

I think the release will wait for the first week of 2023

Hello,

The DirectX11 renderer involve that 3D models must have Texture coords and normals if the generated shader use them, otherwise the rendering fail.

What is the date of your graphic driver ?

also I could not identify the play / stop action in the log, did you do it ?