Field report: a remote player had smooth gameplay but in 3RD-PERSON with NO gauges. Cause: view mode + gauges are CLIENT launch flags, not something the relay/console can enforce -- and join.bat set neither, so remote players booted in the game's desktop default (external camera, no MFDs). The operator's own local launch sets both (the app's 'Start in cockpit' + 'Dev gauges' checkboxes, on by default), which is why the operator saw the correct view but remote players didn't. The pod is a first-person cockpit with MFD gauges and no '3rd person' at all, so cockpit is the right default for players. join.bat/join_lan.bat now set BT_START_INSIDE=1 + BT_DEV_GAUGES=1. (Players can still press V to toggle the external camera.) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
34 lines
1.1 KiB
Batchfile
34 lines
1.1 KiB
Batchfile
@echo off
|
|
rem BT411 -- join the operator's LAN game (auto-discovers).
|
|
rem Joining over the INTERNET? Use join.bat instead.
|
|
cd /d %~dp0
|
|
if not exist "build\Release\btl4.exe" goto badpath
|
|
if not exist "content\OPERATOR.EGG" goto badpath
|
|
set BT_RELAY=auto
|
|
set BT_LOG=join.log
|
|
set BT_START_INSIDE=1
|
|
set BT_DEV_GAUGES=1
|
|
cd content
|
|
..\build\Release\btl4.exe -egg OPERATOR.EGG -net 1501
|
|
echo.
|
|
echo The game has exited. If you did NOT quit on purpose
|
|
echo (crash, or it never connected), send the operator the
|
|
echo file content\join.log so they can see what happened.
|
|
echo Otherwise the session may not be up yet -- try again.
|
|
pause
|
|
exit /b
|
|
:badpath
|
|
echo.
|
|
echo ==================================================
|
|
echo ERROR: this file is not in the right place.
|
|
echo.
|
|
echo It must sit in the EXTRACTED game folder, next to
|
|
echo the 'content' and 'build' folders.
|
|
echo.
|
|
echo Fix: right-click the .zip - Extract All, open the
|
|
echo extracted folder, and run this file from THERE.
|
|
echo (Do NOT run it from inside the zip.)
|
|
echo ==================================================
|
|
echo.
|
|
pause
|