Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem
I agree that load drop can really be used by cheaters when moving over the most challenging sites. Anyway, I can't say I completely approve of your anti-cheating method :-) I think, it would be better to use "Spawn load origin" command adjusting coordinates. For example, to shift the drop point a bit farther back with the default number of dropping logs left unchanged.
Thanx, I check my errors.
About XML command :
This is knowledge from oovee discussion board at http://www.oovee.co.uk/forum/topic/13012-new-steered-trailer-for-long-logs/
This is not bug, but antiexploit :)
Many players before hard terrain drop cargo, cross obstacles and pack cargo again. This is nasty cheat.
Also, I found too many _noinherit="true" commands in your long load xml, in a wrong place .
Another point is spawn load origin command. Try to adjust these coordinates, not copy/paste from original file.
One more point: why did you change impact type of load cdt from “Foliage” to “Truck”? Leave it as it originally was.