Some context: A driving simulator with a visual system composed of a set of 3 screens (left/front/right) to provide a large field of view. Hardware is composed of 3 PC with per PC one RTX 4090 and a FHD screens physically counter clockwise rotated, 55’', screen panel size: 1209,6 mm x 680,4 mm.
In the attached archive, I’ve build a basic nDisplay sample project, but some nDisplay settings and usage may be obscure to me. This project is used with 4 different nDisplay configuration files. My main issues are in the top two:
Usecase #1 MONOHOST_FINAL: first step, 3 nodes running on one host. All the windows are launched stacked on the center of the screen ignoring x/y position set in *.nDisplay setup AND on launch commandline. I don’t understand find why? check OneHostThreeNodes.ndisplay file.
Usecase #2 MULTIHOSTS_FINAL: final step, 3 hosts with each one node. The 3 hosts are launched. Primary front host has a black window and left/right hosts has correct images and FOV. Moving the play camera on the primary front host spreads correctly its location on left/right viewports. Why the front host windows does not display any rendering ? check ThreeHostOneNode.ndisplay file.
Steps to Reproduce
Everything is described in README.txt files in the attached archive.
Log files will come soon.
Hello Stephane,
I suppose issues in the command line, I put together bat files based on Switchboard launch strings.
Please find attached sample project with MONOHOST_FINAL config and Launch Monohost.bat file that works well on my end.
I tried launching multihost (replacing ips to 127.0.0.1) as well which works well on my end too and primary output looks okay. Could you please try launching with the Switchboard and share logs if problems persist?
I would also recommend using newly created project from nDisplay template instead of template itself.
[Image Removed]Let me know if that helps!
best,
vitalii boiko
> 2/ Note that on one PC the position of the three windows ..
Not sure why different PCs behave differently, but if you are able to find the delta that causes it we’d be interested in knowing in order to repro.
> 3/ .. I’m stuck at 86% at launch ..
If you could post logs (or an insights trace using command line) we could take a look. Let us know if you need help with this.
> .. “nDisplay Launcher” ..
It was originally made for local launches only, not for installations. e.g. for profiling performance before deployment, and also internally used for QA and debugging purposes. The official nDisplay launcher is Switchboard.