ConsoleCommand discussion

General discussion of the port and Doom-related chat.
User avatar
Ænima
Addicted to Zandronum
Posts: 3582
Joined: Tue Jun 05, 2012 6:12 pm

RE: ConsoleCommand discussion

#41

Post by Ænima » Thu Mar 07, 2013 5:18 pm

NeuralStunner wrote: On the subject of data saving and abuse, is it possible to call Autosave every tick and thrash the user's drive? Or is there a safety on this function already?
There's a max of 3 or 4 autosave slots, I think. Once a map uses autosave0.zds through autosave3.zds, it goes back to 0 and overwrites it.
Reinforcements: midgame Survival joining/respawning
Doom64: Unabsolved: Doom64 + Diablo II
ZandroSkins: a pack made by our community
AeniPuffs: 3D blood and bullet puff effects, free to use for your own mods
Squad Radio: a WASD-based radio chat menu, add your own custom sounds!
Mercenaries (on hold)
Image

User avatar
Hypnotoad
Retired Staff / Community Team Member
Posts: 528
Joined: Tue May 29, 2012 8:50 pm
Location: Britland

RE: ConsoleCommand discussion

#42

Post by Hypnotoad » Thu Mar 07, 2013 5:25 pm

NeuralStunner wrote: Settings (DMFlags/renderer/&c.) which a map requires to work properly should be added to MapInfo.
Not sufficient, some mods do not have maps in themselves (designed to run with any map wad of choice) but still need certain flags to work properly on any map.

One solution is to have dmflags and such set in the gamemode lump, or to provide specific acs functions to change dmflags and compatflags.

Watermelon
Zandrone
Posts: 1244
Joined: Thu Jun 28, 2012 9:07 pm
Location: Rwanda

RE: ConsoleCommand discussion

#43

Post by Watermelon » Fri Mar 08, 2013 2:31 am

Is it unreasonable to have a flag to disallow openGL rendering? It gives people quite the advantage and allows concentrated ssg shots when vertically looking up/down (which is a HUGE benefit in various CTF maps)

User avatar
Ænima
Addicted to Zandronum
Posts: 3582
Joined: Tue Jun 05, 2012 6:12 pm

RE: ConsoleCommand discussion

#44

Post by Ænima » Fri Mar 08, 2013 2:44 am

Watermelon wrote: Is it unreasonable to have a flag to disallow openGL rendering? It gives people quite the advantage and allows concentrated ssg shots when vertically looking up/down (which is a HUGE benefit in various CTF maps)
IIRC, a "limit GL freelook" flag was implemented a while back for that very reason. It limits your maximum/minimum pitch to that of a software user.
Reinforcements: midgame Survival joining/respawning
Doom64: Unabsolved: Doom64 + Diablo II
ZandroSkins: a pack made by our community
AeniPuffs: 3D blood and bullet puff effects, free to use for your own mods
Squad Radio: a WASD-based radio chat menu, add your own custom sounds!
Mercenaries (on hold)
Image

Qent
Retired Staff / Community Team Member
Posts: 1424
Joined: Tue May 29, 2012 7:56 pm
Contact:

RE: ConsoleCommand discussion

#45

Post by Qent » Fri Mar 08, 2013 3:45 am

I would not like that at all. Couldn't you let SW users shoot straight up or down, even if you can't render it?

Watermelon
Zandrone
Posts: 1244
Joined: Thu Jun 28, 2012 9:07 pm
Location: Rwanda

RE: ConsoleCommand discussion

#46

Post by Watermelon » Fri Mar 08, 2013 3:55 am

Ænima wrote:
Watermelon wrote: Is it unreasonable to have a flag to disallow openGL rendering? It gives people quite the advantage and allows concentrated ssg shots when vertically looking up/down (which is a HUGE benefit in various CTF maps)
IIRC, a "limit GL freelook" flag was implemented a while back for that very reason. It limits your maximum/minimum pitch to that of a software user.
CL_OldFreeLookLimit which is supposed to do that doesn't even work, I set it to true and I could still aim straight down.

EDIT: Apparently that only works for software and only for looking up, not down... is there a GL one?



Qent wrote: I would not like that at all. Couldn't you let SW users shoot straight up or down, even if you can't render it?
I have no idea how this would be accomplished based on my knowledge of how the hacky software rendering is done.



I think the best solution is to make CL_OldFreeLookLimit work again (if it ever did), and then to allow the server to force it on the clients with a dmflag if the host should so choose. That way everyone can keep openGL
Last edited by Watermelon on Fri Mar 08, 2013 3:58 am, edited 1 time in total.

Qent
Retired Staff / Community Team Member
Posts: 1424
Joined: Tue May 29, 2012 7:56 pm
Contact:

RE: ConsoleCommand discussion

#47

Post by Qent » Fri Mar 08, 2013 4:34 am

Why would rendering be a problem if you don't even render it?

Watermelon
Zandrone
Posts: 1244
Joined: Thu Jun 28, 2012 9:07 pm
Location: Rwanda

RE: ConsoleCommand discussion

#48

Post by Watermelon » Fri Mar 08, 2013 5:38 am

It'd be impossible to tell if you're aiming down or not, though I wonder what would result if the limit was removed. It'd be a cool thing to test

User avatar
Ænima
Addicted to Zandronum
Posts: 3582
Joined: Tue Jun 05, 2012 6:12 pm

RE: ConsoleCommand discussion

#49

Post by Ænima » Fri Mar 08, 2013 11:17 am

Watermelon wrote: It'd be impossible to tell if you're aiming down or not, though I wonder what would result if the limit was removed. It'd be a cool thing to test
You can do it with mods that use "recoil" (aka SetActorPitch). Everything just looks super stretched and distorted due to the Y-shearing.
Reinforcements: midgame Survival joining/respawning
Doom64: Unabsolved: Doom64 + Diablo II
ZandroSkins: a pack made by our community
AeniPuffs: 3D blood and bullet puff effects, free to use for your own mods
Squad Radio: a WASD-based radio chat menu, add your own custom sounds!
Mercenaries (on hold)
Image

NeuralStunner
 
Posts: 42
Joined: Mon Jun 04, 2012 6:14 pm
Location: Plain Sight
Contact:

RE: ConsoleCommand discussion

#50

Post by NeuralStunner » Sat Mar 09, 2013 12:36 am

Ænima wrote:There's a max of 3 or 4 autosave slots, I think. Once a map uses autosave0.zds through autosave3.zds, it goes back to 0 and overwrites it.
Not really what I was looknig for: A system to prevent too many disk writes in a short period.
Blzut3 wrote:Only in the Doom community does one find something so obviously broken and then claim it's a feature.

User avatar
Torr Samaho
Lead Developer
Posts: 1543
Joined: Fri May 25, 2012 6:03 pm
Location: Germany

RE: ConsoleCommand discussion

#51

Post by Torr Samaho » Sun Mar 10, 2013 8:59 am

Watermelon wrote: Is it unreasonable to have a flag to disallow openGL rendering?
Yes.
Ænima wrote: IIRC, a "limit GL freelook" flag was implemented a while back for that very reason. It limits your maximum/minimum pitch to that of a software user.
No, AFAIR such a thing never existed. We can talk about adding such a flag though.
Watermelon wrote: I think the best solution is to make CL_OldFreeLookLimit work again (if it ever did), and then to allow the server to force it on the clients with a dmflag if the host should so choose. That way everyone can keep openGL
cl_oldfreelooklimit does exactly what it's supposed to do:
98a changelog wrote:! - Increased Software's freelook to +-56 degrees (in otherwords you can now look up as much as you could down). This is done to reduce the advantage of OpenGL. The old limit can be restored with the new CVAR cl_oldfreelooklimit (default false). [Blzut3, Torr Samaho]

Post Reply