You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using DOD with REHLDS. with sv_use_entity_file 2
I have stripped all the entities from the original dod_avalanche.bsp as I want a custom list later.
Leaving the bsp with just the entities:
{
"wad" " too long to type all
"mapversion' "220"
"MaxRange" "4096"
"sounds" "1"
"skyname "ava"
"message" "Operation Avalanche"
"classname" "worldspawn"
}
or the map would not load. (Some not needed but left anyway)
The dod_avalanche.ent file contains the original bsp ents to load, so the map should look like the original.
When doing it this way the map loads and the entities seem to load by typing 'reslist' shows them, however only the models do not render in the game client.
I am wondering why, is this because some models are model indexes numbers like *248 etc in DOD and not always named .mdl files?
⚠️ Meta-information
Linux server, windows client
📄 Relevant log output
The text was updated successfully, but these errors were encountered:
👉👈 Contact Details (optional)
[email protected]
🤔 What happened?
I am using DOD with REHLDS. with sv_use_entity_file 2
I have stripped all the entities from the original dod_avalanche.bsp as I want a custom list later.
Leaving the bsp with just the entities:
{
"wad" " too long to type all
"mapversion' "220"
"MaxRange" "4096"
"sounds" "1"
"skyname "ava"
"message" "Operation Avalanche"
"classname" "worldspawn"
}
or the map would not load. (Some not needed but left anyway)
The dod_avalanche.ent file contains the original bsp ents to load, so the map should look like the original.
When doing it this way the map loads and the entities seem to load by typing 'reslist' shows them, however only the models do not render in the game client.
I am wondering why, is this because some models are model indexes numbers like *248 etc in DOD and not always named .mdl files?
📄 Relevant log output
The text was updated successfully, but these errors were encountered: