Bug Tracker – Bug 1074

Set Red Pain Intensity limits serverside for the client

Last modified: 2018-12-24 09:30:39 UTC
Bug 1074 - Set Red Pain Intensity limits serverside for the client
Summary: Set Red Pain Intensity limits serverside for the client
Status: NEW
Alias: None
Product: Odamex
Classification: Unclassified
Component: Server & Client (show other bugs)
Version: 0.7.x (Old)
Hardware: All All
: P1 enhancement
Assignee: Odamex Bug Reporter
URL:
Depends on:
Blocks:
 
Reported: 2014-05-01 13:04 UTC by Maëllig Desmottes
Modified: 2018-12-24 09:30 UTC (History)
1 user (show)

See Also:

Attachments

Patch for R.P.I control serverside (3.71 KB, text/plain)
2014-05-01 13:04 UTC, Maëllig Desmottes
Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Maëllig Desmottes 2014-05-01 13:04:44 UTC
Created attachment 496 [details]
Patch for R.P.I control serverside

We've talked with capodecima recently, and we've confronted to an element rather disturbing: the Red Pain Intensity usage.

Other ports has the R.P.I set to 0.5, so twice as lower than DooM2.exe or Odamex.
But if the sv_allowredscreen is set to 1, players can have the opportunity to have to not have any sign of RPI, making their game so clear that it's not fun for players.

Hence this addition: We would like that the server has to define the limits of it if the sv_allowredscreen is set to 2 : for instance, with a minimum of 0.5 to a maximum of 1.0 .

Patch is there.

(Btw, off-note, but there is a typo with the sv_allowpwo description (swit>>h<<ching)
Comment 1 HeX_Vulture 2018-12-24 09:30:39 UTC
Recent talk includes redpainintensity defaulting to 0.5 since the vanilla intensity is ridiculous for modern monitors.

Its not vanilla, but it is one of those "we need to make this feel nice" things that Odamex also strives for.