More Useropts Options

**EndlessVoid**

Wow... Thanks, Bayamos.
I'm gonna start playing with these, and I'll post my settings if I can figure out how to get a densely-populated city (cars and people) that doesn't have a ton of guys walking through one another.

Ideally, I'd like it to look like the first screenshot on the main page (the Jade Room one).

- Void

Warboy

Bayamo wrote:
Whoa, did not see this post Void. Will do, *bookmarks*

And it seems HackView still works, just play with the values - around 700 is ubersparkly.

how did you get it to work? mine isnt working still....

**Riac.**

OMG U ALL H4X0R$ !!!!!!!!!!!!!!!! :smileysurprised: pretty cool hax tho i will b atempting em all

Message Edited by supersdcurge on 05-09-2006 12:13 PM
Message edited by Riac. on 05/09/2006 03:13:04.

zeroone506

Bayamo wrote:

zeroone5069: Hmm. Always wanting something tricky with the sky/ground, eh? Overbright calls two effects from what I can tell - the glow and the blur, with some antialiasing thrown in. Because it's a set effect, I doubt you can actually split the effect into separate parts. The option to achieve what you want, if possible, would be to override the ground reflections (still active just hidden) while leaving the bright sky effect on. If this is possible, these are the parameters that would be your best bet. I'll start sifting through them to see if any work once I've finished my History paper

That blur was the reason why I complained about ground reflections or suggested day/night cycle changes -- now I've discovered the over-bright setting and all my complaints are like swept away. However, changing the sky back to over-bright would be an interesting combination, in my opinion. Thanks a lot for the commands, although they're kinda complicated... could you remind me, do I have to change it from 0.0 to 1.0 or what was it again? I'm kinda lost there.

From what I've read about others' attempts to change the world tint, I heard the sky still (at least partially) had the old colour while the world changed as they had intended. That led me to the assumption that the sky and the world were ruled separately, although I might've got something wrong.

**Dragonram**

I've recently (not 15 minutes ago) just started using these useropts thingies and they rule! I have to ask though, when using: RenderBulletTimeOnly
You said to use it with: AlwaysDoBulletTime
So would I put one on top of the other or do they need values? If so what values would they be? :smileyhappy:

Also I tried using the:
CameraMinDist = 50
CameraMaxDist = 1000
CameraHeightOffset = 0.70
CameraHeightOffsetSitGrnd = 0.025

But it doesn't appear to have done anything...:smileysad:

Any help is much appreciated :smileyhappy:

- Ð

**Bayamos**

In general, you can tell the nature of the parameter by the wording used in its name. When there's a word like "Always" or "Only," it's safe to assume that a boolean variable should be used (1 = true, 0 = false).

Thus,

RenderBulletTimeOnly = 1
AlwaysDoBulletTime = 1

I'd also stick this one in there, which you can override if necessary by Ctrl-C'ing to "Scripted."

AllowBulletTimeCamera = 0

As for the Camera parameters, MaxDist and MinDist dictate how close or far away you can zoom from your RSI. You appear to have the default values assigned to the camera parameters. If you crank MaxDist up to 25000 or so, you can get some awesome aerial shots, like this. Unfortunately, sticking a negative value in MinDist does not allow you do zoom in past your RSI for a first person view. CameraHeightOffset's is described as "the Camera's focal point as a factor of the half extents." The parameter's default value is 0.70, so that's why you're not seeing any change. Assigning it a value of 0.00 will shift the camera to your feet, 1.0 will put it at your head, 1.5 or so will give you a "Tall First Person" look that's lower than the Hyperjump First Person method. And as for the SitGrnd HeightOffset, you're modifying it by 25 thousandths... no wonder you're not seeing any change SMILEY

Hope this helps SMILEY

**Dragonram**

Bayamo...you need some kind of specialist title man, you rule! Thanks a lot :smileyhappy:

- Ð

**Aquatium.**

Dragonram wrote:
Bayamo...you need some kind of specialist title man, you rule! Thanks a lot :smileyhappy:

- Ð

I 2nd that!!!

Bayamo your really helping a lot of people with what you post.

Masta-Dues

Ive got a question, do these configs work any diff in CR2?

Main reason i ask is mine no longer works.

Also what are the main ones that help so i could redo mine.Like zoom dist lag 100% screenshots etc etc.The need to have ones.

Thanks:smileywink:

**Bayamos**

The vast majority of useropt commands still operate exactly the same in CR2. Of course, with every update there's changes to the list of parameters - some are set to server-side-only, some have aspects modified on the server. When there's an event, serverside wr_rez_events = bluesky1 or whatever is part of what determines how the game sets things up.

To answer your question though... almost all parameters work the same. The exceptions are parameters that deal with the combat system prior to CR2. To my dismay, the useropt parameters which worked on QA to display combat rolls and show the old hotbar queue animation system are no longer settable by the client.

As for camera features though, everything should be working exactly the same. MaxCameraDistance or whatever it's called is still going for me, prefetch radiuses still preload areas while I hardline somewhere, and the screenshot_qualitysomething one still works the same. It's only combat stuff which was changed.. so something is weird with your useropt file.

Some important parameters copypasted from my file:

# Prevent .bik intro movies from loading. If parameters 5 and above delay=1, Blue Sky vids do not play.
Splash0 = ""
SplashDelay0 = 1
Splash1 = ""
SplashDelay1 = 1
Splash2 = ""
SplashDelay2 = 1
Splash3 = ""
SplashDelay3 = 1
Splash4 = ""
SplashDelay4 = 1

# Minimum and maximum allowable distances for the camera.
CameraMinDist = -500 (doesn't let you zoom in thru char though)
CameraMaxDist = 99999

dl_slod_initloadradius = 400000 (these are a bit overboard, if you're not taking panoramic screenies or filming a vid, there's no need for the values to be up here :0)
dl_slod_prefetchradius = 400000
dl_ext_prefetchradius = 160000
dl_int_prefetchradius = 120000
dl_prop_prefetchradius = 200000

# Old Preload distances (raised temporarily for MS9) [Bayamos's more detailed version]
dl_ext_initloadradius = 50000
dl_int_initloadradius = 5000
dl_prop_initloadradius = 5000
dl_floorheight = -350

ScreenShot_JPG_Quality = 100

# Matrix Code, use in conjunction with MatrixView if set true.
WR_MatrixView_Min_T = -1.0
WR_MatrixView_Max_T = 0.0

#Anti-Alias
AntiAlias_Level = 1
AntiAliasFSOverSample = 12
AntiAliasFSQuality = 12

#Determines how long the client waits for a query window - duel, team, etc.
ScreenRestoreWait = 30

Hope these work out for you :0 If you still experience problems, feel free to email your cfg file to [email protected], and I'll take a look at it.

And Dragon/Void, right now I'm just hoping to get RSI Idealist someday SMILEY

And I think Raijinn is kinda busy... doing whatever he does ^^

Message Edited by Bayamo on 05-17-2006 08:02 PM
Message edited by Bayamos on 05/17/2006 16:02:36.

**Othinn1**

How do you find all these useropts settings? I haven't even found half the amount you have, and it sounds like you have enough settings to fill a large book.

AmbrielSyntax

Bayamo
Code Artist
posts: 1058
Registered 12-20-2005

**Dragonram**

AmbrielSyntax wrote:
Bayamo
Code Artist
posts: 1058
Registered 12-20-2005

I concur with Ambriel, Raijinn if you're reading this do it!!! :smileyvery-happy:

- Ð

**Bayamos**

Othinn1 wrote:
How do you find all these useropts settings? I haven't even found half the amount you have, and it sounds like you have enough settings to fill a large book.

Hehe... it is, sorta. Code can be like a book too, if you know how to read it SMILEY

It's fairly easy to find parameters, and resourceful players should figure out the method if they put their minds to it. Finding the right way is one thing, actually retrieving parameters from in between huge messes of code is another.

I've stated before my position on this topic: The devs have said there's admin-only commands that they don't want players knowing. I've seen such commands in the same place I get the useropts (one of the locations, at least). There are useropt parameters which are potentially exploitable, and could be misused (HackView / MaterialBuild / NoTextures cheating to see players in sneak, etc). Some parameters could potentially be mis-set, after all it's a huge list and it's kinda easy to let a parameter be client-settable when it should be server-side only. And there are some like that, Void knows which one I'm talking about. Displaying the old hotbar queue window would make it ridiculously easy to do the Double EFK or Double Sidekick sploit in CR2, MaxServerDistSqr would eliminate rubberbanding. Those specific parameters have been recently been set to server-side only, but there are others that are potentially bad. Some even have to do with Consistency and CT Rolls, and actual combat stuff... while I went through most of them quickly to make sure there's no huge problems, I don't think the devs want players having a list of all the settings. Rarebit has said some department or other will eventually give him a list of all client-settable parameters, so yeah. Until then, I'll try to help you guys out by finding and posting specific requests :0

**Dragonram**

That's it...:smileyindifferent: I'm PM'ing Raijinn asking for you to be made a specialist rank, you truly do deserve it my friend :smileyhappy:

- Ð