View Issue Details

IDProjectCategoryView StatusLast Update
0008021New Feature Requests[All Projects] Generalpublic2017-06-18 20:57
ReporterSHC//SniperAssigned To 
PrioritynormalSeverityfeatureReproducibilityN/A
Status newResolutionopen 
Summary0008021: [Request] Function to disable visual vehicle damage
Description

Currently there is no actual way to disable the sync and damagabilty of vehicle parts (doors, bumpers, etc.) without a workaround. Therefore I would appreciate to have a function implemented to turn visual vehicle damage on/off.

TagsNo tags attached.

Activities

arranTuna

2014-02-02 13:59

manager   ~~0020140

Last edited: 2014-02-02 14:01

View 2 revisions

Have you tested onClientVehicleDamage?

Edit: Just tested it myself and yes the parts get damaged and fall off.

SHC//Sniper

2014-02-02 20:09

reporter   ~~0020142

Last edited: 2014-02-02 20:09

View 2 revisions

https://code.google.com/p/mtasa-blue/source/detail?r=6107

Ccw just confirmed that extraordinary high CPU usage of "58_Vehicle_parts_state_sync" (performancebrowser -> Packet usage) is related to vehicle parts not being synced very efficiently. r6107 should now significantly lower CPU usage; a per-vehicle function to disable damage sync could still be useful in order to reduce unnecessary sync.

SHC//Sniper

2014-02-03 14:07

reporter   ~~0020143

Just tested out setServerConfigSetting("alt_veh_parts_state_sync",1) with the latest revision and it increased CPU usage by x2; obviously there must be something wrong with it.

ccw

2014-02-03 23:21

administrator   ~~0020152

Retry with r6113

Issue History

Date Modified Username Field Change