ScriptureCasterDocumentation
Troubleshooting
The projector is not found, the window does not fit, text looks wrong, NDI will not start — and what to do about each.
Start here
ScriptureCaster.exe --selftestRun this on the machine that has the problem. It reports the translations loaded, the screens Windows can see, their sizes, whether any uses display scaling, the smallest size the window needs, and whether NDI is available. Most problems are visible in that output.
The projector is not found
Press F5 to re-detect.
If the self-test reports only one screen, Windows has not extended the desktop: Win+P → Extend. Duplicating the display gives Windows one screen, and the app cannot then take the projector separately.
Projectors that go to sleep sometimes drop off. Wake it, then F5.
The verse appears on the wrong screen
Settings → Ecrane / Screens — set the row to a specific display rather than Automat. Automatic mode takes the first screen the control window is not on, which is wrong if you have three displays.
The window does not fit
The self-test prints the smallest size the window needs and each screen’s size. If the screen is smaller than that, either:
- reduce Mărime butoane / Touch button size in Settings, or
- set that display to 100% scaling in Windows
Display scaling is the usual culprit: at 125% everything is enlarged, including the space the window needs.
Text is cut off on the projector
The output fits text to the box every time it changes, so this normally means the maximum size is set very high and the margin very low. Try Margine 5% and a maximum size around 9%.
If a specific verse looks wrong in one translation but fine in another, the source file may have that verse merged with its neighbour — see the note about versification below.
Two languages are out of step
Some Bible files number verses differently, or merge two verses into one. When the two translations disagree, the app shows what each file actually contains, and marks a verse that is missing in one of them.
The bundled Cornilescu has this in 1 Petru. Importing a better copy of the same translation fixes it — the app is showing the file honestly, not making a mistake.
NDI will not start
Check Settings → NDI first: the tab says whether the NDI library loaded. Nothing has to be installed for it — the library ships with the app — so if that line reports it is unavailable, the download was incomplete and unzipping it again is the fix.
If it says it is ready but no receiver sees the stream, the usual cause is the network rather than the app: NDI discovery does not cross subnets or VLANs, and some corporate wifi blocks the multicast it uses. A wired connection on the same switch as the receiving machine is the quickest way to prove it.
If the stream appears but is black in your switcher, check the NDI source’s alpha setting — with a transparent background the frame is mostly clear, and a switcher told to ignore alpha shows nothing.
Nothing here matches
Send us the details — including the --selftest output if you can.
It usually says exactly what is wrong.