WARNING: THIS IS A TEST

THIS DOES NOT CONTAIN NEW TYRE PHYSICS OR THE NEW GRAPHICS SYSTEM

PLEASE TEST BEFORE YOU POST

PLEASE... NO OFF TOPIC FEATURE REQUESTS!


Hello Racers,

Here is a new test patch: 0.7D48

Please read the list of changes below.

0.7D48 is compatible with 0.7D
- You CAN connect online with 0.7D
- You CAN play replays from 0.7D

Please back up or rename your LFS.exe from version D so you can revert to it if necessary.


Changes from D to D48:

Interface:

A small map is now displayed at Layout Square if there is a layout
New display in F9 / F10 views shows estimated laps given fuel use
Engine health (with colour code) is displayed in F9 / F10 views
F9 / F10 extra displays are now switchable (Options - Display)
Speedo and tacho are moved UP if required for extra displays
CT display now uses dot matrix font if translation allows it
Driver / fuel buttons in garage are now only shown if relevant
Speed at redline is displayed beside each gear ratio in setup
Simple versions of F11/F12 displays are now available during an SPR
A message shows the name of any mod that can't be loaded in an SPR
Four-character mod names are shown in results table instead of MOD
Downforce tab is now shown for all vehicles
- previously was only for those with adjustable wings
- shows an estimated maximum speed based on wind resistance
- note: the estimate does not consider rolling resistance
FIX: Crash when two events on calendar used same event image
FIX: Calendar time could be wrong near start of daylight saving
FIX: Small camera movement on releasing LMB after 2-button rotation
FIX: Chat text in mods screen is now in front of interface buttons
FIX: User names that start with '.' now correctly displayed in chat
FIX: Crash if /track command was used while generating AI path info
FIX: AI skill level always used Latin codepage in F11/F12 menus
FIX: Engine brake reduction had no effect for EV but was visible
FIX: /setlap command error if name coloured and number 4 chars long
FIX: Replays auto-named with special characters could appear wrong

Controls:

A force feedback display is shown below the pedals (bottom right)
FIX: Mouse wheel gearshifts are now equivalent to 100ms keypress

Game:

Possible to reset if an approaching vehicle is moving slowly enough
Reset is now possible during a pit stop if the state is "finished"
Speed limiter (at 80 km/h) can be manually enabled if no pit lane
Auto gear shift: downshifts are now done at slightly lower rpm
FIX: Auto shift *up* did not work if max power rpm above redline
FIX: Driver swap enabled very high speed limiter if no pit lane

Mods:

An EV charge/discharge power bar in place of the clutch bar
- only visible if Options - View - Show pedals is enabled

A new "Cleanup" mode in the mods screen
- you can select to keep latest mods and test mods
- there is not yet a feature to keep replay mods

Support for new options set per vehicle instead of by race class
Support for "hub" subobject that moves and rotates with a wheel
Support for new pit speed limiter flashing light option
One wheel drive and no anti-roll if wheels are staggered
Click Skin ID in garage colours tab to copy ID to clipboard
Hold CTRL in Garage: Mods button becomes Test (direct to Test mode)
Opening mods screen is prevented if a rating request is in progress
FIX: Mod with 27 character name appeared in mods screen Test mode
FIX: Crash if mod had more than 64 materials

Dashboards:

Engine damage light on dashboard is now available if set in editor
Support for new speedo and tacho style options (see editor notes)
Support for dashboard backing texture system, text colours, opacity
Can also set background colour without supplying a backing texture
New needle pivot texture works better on light coloured dashboards
Dashboard brightness should now be the same as in the editor
- this update also affects the RB4 and MRT5 (recently updated)
FIX: Text size on dashboard more closely matches text in editor
FIX: Brightness of multi function display now matches the editor

New steering model for bikes:

Improved handling and braking ability
- Feet down steering model up to 7 km/h
- Low speed model only from 7 km/h to 18 km/h
- Interpolated model from 18 km/h to 36 km/h
- High speed model only above 36 km/h
FIX: Steering glitch between feet down model and low speed model

AI vehicle control:

Improved braking prediction so less running wide at corners
- considers brake balance (which is not ideal for every corner)
- can result in better lap times due to improved line following
AI braking prediction now takes account of engine braking
AI can now ride motorbikes (a bit slowly due to safety margin)
AI will drive more gently when off track on a bad surface
Bikes slow to avoid taking off over large humps in the road
Avoid unnecessary downshifts by looking ahead to see if needed
FIX: Sometimes could reach a maximum speed and stop accelerating

AI misc:

Distance to vehicle considered dangerous now depends on length
Distance to vehicle considered safe is reduced at low speed
- should prevent long vehicles hitting the brakes on green light
- gaps between vehicles may be smaller when speed is below 20 m/s
AI can enter configs with no path (but will not drive)
AI can now enter the game with an object (to just sit there)
Better collision avoidance when close behind or beside others
Reset is available even after engine switched off after long wait
Message history is no longer enabled for AI path generation
FIX: AI can now reset if in contact with a stationary vehicle
FIX: Errors in fuel calculation related to "Refuelling allowed"
FIX: It was possible for the fuel calculation to report 0 stints
FIX: A hang generating path for a mod with "Max up" wrongly set

AI in pit lane:

Target speed 1 km/h slower in pit lane to avoid speeding by mistake
- was possible for a powerful car to overspeed shifting 1st to 2nd
Improved driving in pit lane when close behind other drivers
Avoid excessive downshifting when approaching speed limit zone
Approx 1 second safety margin entering pit lane to avoid speeding
Use speed limiter or throttle to avoid wheelspins causing speeding
Smoother transitions switching between main path and pit lane path
FIX: Choice of pit stop box was wrong (bug introduced in 0.7B)
FIX: Slow start / stuck in pit stop if max torque at very low rpm
FIX: Some mods would brake too gently and miss the pit stop point
FIX: Some mods would overshoot their pit garage when parking
FIX: Can now reset at the end of a pit stop (e.g. fallen bike)

AI overtaking:

Various improvements to improve the overtaking decisions
Overtakes are considered on a group instead of individuals
Better estimate of the possibility and duration of a pass
Pass decision from low speed now allows for acceleration
When planning a pass time is allowed to pull in after pass
More distant consideration of other vehicles at high speed
There should be fewer dangerous overtakes in braking zones
FIX: AI could get pointlessly stuck behind a slower vehicle

Regional downloading system:

We now have 3 download locations for mods (NL/JP/US)
Faster downloads if you are in N/S America or Asia/Oceania
Locations in Asia and Oceania will download mods from Japan
Locations in North and South America will download from USA
Download redirection is handled automatically by our server
Regional downloads can be disabled by a new Misc Option
Yellow redirect message is shown the first time you are redirected

Graphics:

Dust colour on grass and dirt tracks now uses a dirt colour
- previously used average colour of surface which looked odd
- smoke and dust acquire lighting colour from car's location
FIX: Mudguard / handlebar / trailing arm subobject could disappear

Physics:

Improved bike physics (affects lean angle and tyre forces)
Pit speed limiter now based on drive speed instead of world speed
- prevents wheelspins (e.g. at RO) pushing car over the speed limit
FIX: Narrow cars were sucked in when near fence or narrow barrier

Audio:

Tone variation limited to 0.99 to prevent an engine sound bug
Switched off experimental "Prevent clipping" option by default

Multiplayer:

Improved setting of tyre state after receiving a position packet
- previous location of tyre contact is better estimated (for forces)
- most noticeable when viewed car had not been on screen for a while
- e.g. after tabbing to another car or fast forwarding a replay

Misc option "Full physics for remote cars" is enabled by default
- low res physics previously used for cars other than the 4 nearest
- option approximately doubles CPU usage by physics in multiplayer
- could cause issues at turn 1 with many cars depending on PC power
- use profiler display to check CPU usage with the option enabled
- see profiler by pressing car icon then P in Misc/Graphics options

Engine damage repair in pit stop
- yellow counts as minor damage (6 seconds)
- red counts as major damage (12 seconds)

Team arrow colours on small map are now enabled by a host option
- arrows on non-race small map take colour of first name character
- option is not yet available but is coded as /teamarrows=no/yes

Cancel button and ESC key to cancel the process of joining a host
- the currently downloading skin or mod is allowed to finish first
Temporary (free) hosts are shown without colours in List of Hosts
Stationary cars can now lag for longer (3 seconds) before vanishing
FIX: Remote car using pit speed limiter did not move smoothly
FIX: Crash enabling filter in List of Hosts after all were disabled

InSim:

IS_CPP packet with Time = 0 is instantly processed (not stored)
- allows it to be followed immediately by an IS_CPP with Time > 0
FIX: ZByte was not set in IS_OBH packet

New commands:

/status none|F9|F10|F11|F12|next|prev - sets status screen
E.g. /status next will cycle through the F9 to F12 status screens
(you could assign it to a CTRL+ or ALT+ key and then a wheel button)

/liveset and /pitins - do the functions of F11 and F12 menus

You can use operators:
= (set value)
+= (add to value)
-= (subtract from value)

Examples:
/pitins ftyre = r3 : change front tyres to R3 in pit stop
/pitins rtyre = super : change rear tyres to road super
/pitins fpressure = 1.1 : set front tyre pressure to 1.1 bar
/pitins fpressure += 0.1 : increase requested pressure by 0.1 bar
/pitins cancel : cancel all pit instructions
/pitins tyres always : change all tyres
/pitins tyres 20 : change tyres if wear > 20%
/liveset bbal 60 : set brake balance to 60%
/liveset rarb -= 0.1 : decrease rear ant-roll bar by 0.1

Available options for /pitins:
fuel, tyres, repair, symmetric
ftyre, fcamber_l, fpressure_l, fcamber_r, fpressure_r, fwing
rtyre, rcamber_l, rpressure_l, rcamber_r, rpressure_r, rwing
cancel, fcamber, fpressure, rcamber, rpressure

/pitins pressure commands can accept unit (psi/bar) (no unit = bar)
E.g. /pitins fpressure 30 psi

Available options for /liveset:
bbal, farb, rarb

Multiple commands on single line:

Multiple commands can now be added on a single line which sometimes
can avoid the need for a script file, e.g. to set a button to
change tyres in pit stop, you could use a double command:
/pitins ftyre super /pitins rtyre super

NOTE: some commands cannot be followed by another command:
/say /echo /join /rcm /pass /msg /altf /ctrlf

Maximum length of command and F key text increased to 95 characters
Wider text display in CTRL+ and ALT+ tabs in controls screen

Translations:

Updated translations - thanks to our volunteer translators


INSTALLATION:

A FULL version of LFS 0.7D must already be installed

To install the PATCH using the SELF EXTRACTING ARCHIVE:

1) Move or save the patch into your main LFS folder
2) Double click the patch to extract it to that folder
3) When you see "Confirm File Replace" select "Yes to All"
4) Now you can start LFS in the normal way

NOTE: You can see if the patch is correctly installed when you run
the program (LFS.exe). At the bottom of the entry screen: 0.7D25


DOWNLOAD:

IF YOU ALREADY HAVE 0.7D:
PATCH 0.7D TO 0.7D48 (SELF EXTRACTING ARCHIVE)
https://www.lfs.net/file_lfs.p ... =LFS_PATCH_7D_TO_7D48.exe (1.5 MB)

Quote :

Arrows on non-race small map take colour of first name character

If possible, could this be changed to an ON/OFF toggle option?

-------------------------
That aside, I like these minor updates, specially the manual pitlane limiter one. Very useful for custom pitlanes

Quote from Ibtasim6781 :

If possible, could this be changed to an ON/OFF toggle option?

This may be clear in your mind but to me it raises questions.

1) Are you talking about an option for the server or for users?
2) What are the reason? Aesthetics or gameplay?

We already had some suggestions on the other thread. If possible I would be very happy not to add options. Because (1) this is supposed to be a quick update, (2) every option added is another thing to maintain for ever more and (3) server side options are always more complicated and often cannot be added to compatible versions. So please do be very specific about your request and elaborate on the reason for it.

Semi-related to the maximum speed for gears, I read recently about another display from LFSLazy that can apparently be very useful. An engine damage display on screen.

Further reading:
MandulAA: https://www.lfs.net/forum/post/2013145#post2013145
pantiainen: https://www.lfs.net/forum/post/2013394#post2013394

I'm not saying I'll actually add it to this test patch, but I was wondering if an engine damage % (or the opposite, engine health %) could be displayed in a small box like the CT. I'm not sure if it really needs a number or just a bar like the CT. And it leads me to another question, if engine damage should be repaired in pit stops? It seems unrealistic but it's no less realistic than full suspension and perfect bodywork repair in the pits, so why not allow engine to be repaired too. It's something that can be "better" in racing sims than real life. I'm thinking when you have a 6 hour race and you do one dodgy gearchange, so now you have a weak engine for the next 5 hours. Disappointing and maybe not so bad if you could just pay for it with a pit stop.

I was thinking a small damage % could be included in "minor repairs" and a larger % would lead to "major repairs".

Well that is just a thought. Don't think it's wasted time as it affects the current public version and the version still in development. Also seems pretty easy to do though I haven't looked in the code yet.

Seeing engine damage would be a valuable information,especially for learning drivers so they can actually see what and when leads to that damage. And regarding repairs - yea,LFS mechanics are insanely fast with repairs,so it wouldn't be that different if they were able to fix engine too,however I would suggest to have it as different option in F12 menu and also that in pit it would be a seperate repair section besides minor and major repairs.
And if we start the topic about repairs,maybe in bigger future update it would be better to slow the mechanics down regarding repairs (I assume tyrechange and refuelling are pretty much fine) to give people more "penalty" for not avoiding contacts. Also one other note - if tyres are changed,tyre pressure adjustments should not cost extra time as that's a predone work of mechanics.

Engine damage would definitely be helpful. IMO, if you do decide to repair engine damage on pitstops, then you should also give it its own flag so that it can be used in insims.

Now, I am not really a racer, so i can't say much about it racing wise. But it is a great addition. Its especially helpful to new players to LFS wondering why their car aren't moving (or moving at reduced speeds).

Perhaps show as a percentage? Engine damages usually aren't that much.

Quote from Scawen :

An engine damage display on screen.

Since we have the opportunity to see the heating of the clutch, then I'd like to see the percentage of engine damage or some sort of bar, but at the pitstop I'd like it all to be optional. I think a lot of people want to see their races realistic as possible. Where there is no way to quickly fix the engine. And some others, who not cares about realism, be glad of such an opportunity.

Quote from Scawen :

I'm thinking when you have a 6 hour race and you do one dodgy gearchange, so now you have a weak engine for the next 5 hours. Disappointing and maybe not so bad if you could just pay for it with a pit stop.

If it possible, I'd like all of these things to be separate for the race host and optional. Like repairing on pits: damage to the engine, gearbox, suspension, bodywork, etc. and you check the boxes to enable or not. Someone does not want to have the opportunity to repair the engine and gearbox. But the suspension and body can be repaired. Someone wants to include everything.

And If possible, I would separate engine and gearbox damage. I would attribute incorrect switching of gears to damage to the gearbox. Overclocking on the engine cutoff, or damage to the body in places where the engine is installed (or add a radiator object, if damaged, the engine will gradually gain damage) I would attribute it to engine damage. Because in real the radiator can sometimes be repaired in a short time, and the engine, if it means damage of engine block or someting in cylinder head cannot be repaired in a short time. This already sounds complicated to implement so I don't know if it's worth it.

Quote from Scawen :

could be displayed in a small box like the CT.

more realistic approach would be a "check engine" light e.g.:


In any case I think that value should also be included in the OutGauge then for the gauges to be able to show the damage digitally or as a aforementioned check engine light

engine damage is usefull .. yes we damage the engine during the first hour of an enduro and spent 3 hours to try finish the race ...

also, in the same spirit, what about the possibility to choose repair only "major damage" ? instead of minor +major like actually

Thanks for the feedback about engine damage. It looks like most people would like it displayed (as a number).

About the repairs, and options for servers to allow it, or for users to select whether it should be done or not in pits, InSim output etc. that is massively beyond the scope of this patch. I've got far too much work to do and can't get into things that take many hours to do, even if they are good thoughts you are having.

My suggestion was that, maybe, (and I haven't even checked the code yet) a small amount of damage could result in the already existing "minor damage" time delay and a larger amount of damage could result in the already existing "major damage" time delay.

There's already a damage repair option and that would apply to engine and suspension all with the same option.

That's all I can offer at this time, no interface, no options, just an opportunity for engine damage to be fixed by the super fast mechanics while the other super fast mechanics might be working on the suspension and doing a incredible job fixing the bodywork without a trace.

Quote from Scawen :

Thanks for the feedback about engine damage. It looks like most people would like it displayed (as a number).

About the repairs, and options for servers to allow it, or for users to select whether it should be done or not in pits, InSim output etc. that is massively beyond the scope of this patch. I've got far too much work to do and can't get into things that take many hours to do, even if they are good thoughts you are having.

My suggestion was that, maybe, (and I haven't even checked the code yet) a small amount of damage could result in the already existing "minor damage" time delay and a larger amount of damage could result in the already existing "major damage" time delay.

There's already a damage repair option and that would apply to engine and suspension all with the same option.

That's all I can offer at this time, no interface, no options, just an opportunity for engine damage to be fixed by the super fast mechanics while the other super fast mechanics might be working on the suspension and doing a incredible job fixing the bodywork without a trace.

Sure, i think it could be a solution for time being, then later after big update it should just be in list things to do, as there are other things as well that could be changed with pitstops, not just engine changes that we suģgested, thanks.

Quote from Scawen :

Thanks for the feedback about engine damage. It looks like most people would like it displayed (as a number).

I can confirm that the engine damage was the most requested feature in Detect&Monitor (implemented by reading in memory as no other way).
A gauge like CT would be nice (+ a light when you perform a damaging action as bonus) (and of course from my point of view, an access to this info via insim or outgauge)

Quote from Scawen :

This may be clear in your mind but to me it raises questions.

1) Are you talking about an option for the server or for users?
2) What are the reason? Aesthetics or gameplay?

We already had some suggestions on the other thread. If possible I would be very happy not to add options. Because (1) this is supposed to be a quick update, (2) every option added is another thing to maintain for ever more and (3) server side options are always more complicated and often cannot be added to compatible versions. So please do be very specific about your request and elaborate on the reason for it.

Should have been more specific. Apologies

An option for users to click on. The reason mainly apart from aesthetics/gameplay-wise is that its not very useful outside those specific events (Football, Derby, etc etc) so it looks more of an option to use when in those events. At least thats how I see it

In the end you have the final call whether to do it or not so its understandable you wouldn't want to spend more time on it if possible/can be avoided

I really like the bar for clutch heat, I don't care the exact temperature, I just need to know if I need to be careful. I think engine damage is different as it isn't something that goes away, it think would be nice to make it consistent with clutch heat in the UI. Maybe if both were bars but engine damage could have the number over the bar, or alongside?

About an option to use or not use the name coloured arrows on servers without lap timing:

Quote from Ibtasim6781 :

An option for users to click on. The reason mainly apart from aesthetics/gameplay-wise is that its not very useful outside those specific events (Football, Derby, etc etc) so it looks more of an option to use when in those events. At least thats how I see it

I wonder where it will be seen, other than football? Which servers don't use lap timing?

Cruise servers is one example (though I'm struggling to think of others). Degats pointed out a possible issue, but we haven't heard from anyone if they actually found it a problem or a benefit in reality.

Quote from Degats :

Not sure how good it would be for chases on cruise servers, as it will make it even easier for police to follow where a car is going on the map. Given the highly competitive nature, it would change the balance a bit.

Would be interesting to hear if people like it in cruise servers.

Quote from superlame :

Maybe a good idea is to have the colorful arrow as an option inside Misc?
For the people that think it is too colorful for them, they can switch it back to the default (Pre 0.7D3)
Options - Misc - Enable colorful arrow map?

As you say: Maybe. I hope to hear from people what they actually feel about it.

At the moment we are just talking about solutions to theoretical problems that may exist.

I see two problems with acting too fast:

1) We have not received any feedback at all about what people think about it on servers (if they actually like it or not).
2) The question of server option vs user option. Both seem as valid as each other but it's probably not a good idea to implement both, as they can conflict. Before anyone tells me, yes I know we could have server option "ON / OFF / FREE CHOICE" to avoid actual conflict between two options (or server option "ALLOW COLOURFUL ARROWS IF USER WANTS") but interaction between server option and user options is more complicated than I really want for this simple fun feature.

My job is not to dictate the answer but to assess feedback from people who are actually using it, compare this with suggestions and see what comes up.

Obviously as mentioned I like the easy solution of "no option" (as now) but still need to hear feedback from people using it. Maybe less useful at this point is thinking of options for other people whose opinions we have not yet heard and may or may not like it.

Quote from Flame CZE :

This thread is not a place for general LFS suggestions - keep it test patch related only please.

Sorry for that!

Quote from Scawen :

.
1) We have not received any feedback at all about what people think about it on servers (if they actually like it or not).

For us at TC CityDriving, I think the best option would be if I can control the colour via our host's Insim (sure, if the client option allows it). Provided its technically possible.

I could then think of numerous ways to make use of it: e.g.

- Indicating the player's role (like COP/TOW/MED, same team, same mission, friends (or foes )
- Replicating the original behaviour for Insim controlled races (on cruise servers).
- Indicating the teams in events (e.g. football)


Little edit: If its not possible to have player per player colours, then I'd rather have a option to turn the colours off (as it was before). For a very simple reason: I only need the arrows to see if there are cars in my vicinity or closing up quickly, but it takes too long now to even find my own arrow in that view.

I prefer controlling the player colour by insim.

Indicating teams.
Indicating carclasses.
Ranking.

A another example.
For our Timeattack system with multistage layouts, it could be handy to see which driver is driving on which stage.

I do not know how the insimpacket will look like but for LFSLapper i could create a simple function like:

So for my point of view, i see more benefits to control the player colour by insim.

damn interface in setting become brilliant,thanks Lfs team for update!very useful

I've made this appear beside the CT indicator, just an early test so far.

Naturally it comes out as a "Health" value that starts at 100% and goes down from there (if you downshift too early -> over rev). No change in the physics, this is only a display.

One bad shift affects it quite a lot, so I think one decimal place is enough. Maybe the straight percentage with no decimal place would be OK?

Opinions welcome, maybe I'll release a minor update with this tomorrow morning so you can have a go.

I was thinking the engine symbol could start grey then go yellow then red with more damage. Possibly if pit engine repair is implemented, the colours could line up with "minor damage" and "major damage".

Quote from Scawen :

Naturally it comes out as a "Health" value that starts at 100% and goes down from there

I'm wondering what does this percentage say? If I damage the engine to 90%,do I have 90% of power at each revs range?

Quote from Scawen :

I was thinking the engine symbol could start grey then go yellow then red with more damage.

That sounds like a good idea.

Quote from Scawen :

I've made this appear beside the CT indicator, just an early test so far.

Naturally it comes out as a "Health" value that starts at 100% and goes down from there (if you downshift too early -> over rev). No change in the physics, this is only a display.

One bad shift affects it quite a lot, so I think one decimal place is enough. Maybe the straight percentage with no decimal place would be OK?

In my opinion it already looks good enough, but not quite universal, for the clutch we have a filling bar, and for the engine percentages. Although, it's easy to get used to it.

Quote from Scawen :

I was thinking the engine symbol could start grey then go yellow then red with more damage. Possibly if pit engine repair is implemented, the colours could line up with "minor damage" and "major damage".

I think it would be better, if it is not difficult. I don't know what it's worth on time perspective. I, like many others palyers are interested in that as soon as possible came out update with graphics and physics so if you can save time on this patch to go to a more expected update, I would choose this.

Quote from Scawen :

I've made this appear beside the CT indicator, just an early test so far.

Naturally it comes out as a "Health" value that starts at 100% and goes down from there (if you downshift too early -> over rev). No change in the physics, this is only a display.

I like the icon and percentage display - I think it's a better choice than the textual "CT" for clutch temperature which I'm not sure some new people know the meaning of.

Quote from Scawen :

One bad shift affects it quite a lot, so I think one decimal place is enough. Maybe the straight percentage with no decimal place would be OK?

I don't know if a decimal place is needed - it depends how much an engine damage smaller than 1 % affects the car's performance. It definitely needs some testing.

Quote from Scawen :

I've made this appear beside the CT indicator, just an early test so far.

Naturally it comes out as a "Health" value that starts at 100% and goes down from there (if you downshift too early -> over rev). No change in the physics, this is only a display.

I do like that a lot, although wouldn't engine damage be more suitable to display the actual damage?
So it would display something like 1.5%. But i suppose it doesn't matter too much.

Quote from kristofferandersen :

I do like that a lot, although wouldn't engine damage be more suitable to display the actual damage?
So it would display something like 1.5%. But i suppose it doesn't matter too much.

the way it appears now, it is a "engine health" display, so it shows the engine health
still, i think that might would be interesting to put an option to change that display from helath to damage, like we have different options in the accelerometer indicator