Search Results: 480 messages were found

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

The Merovingian is looking for talented fans to make him a forum signature image. The image must be non-animating .gif, or .jpg format.

Submissions must be posted to this thread by 10:00am PST, Friday, February 24th. The winning submission becomes the property of SOE, and will be hosted on our servers. This is a volunteer fan contest, and no reward will be implied or given beyond recognition for your effort on these forums. SMILEY

Thanks, and good luck!

Message Edited by Rarebit on 02-13-200611:15 AM

Niobe is looking for talented fans to make her a forum signature image. The image must be non-animating .gif, or .jpg format.

Submissions must be posted to this thread by 10:00am PST, Friday, February 24th. The winning submission becomes the property of SOE, and will be hosted on our servers. This is a volunteer fan contest, and no reward will be implied or given beyond recognition for your effort on these forums. SMILEY

Thanks, and good luck!

Message Edited by Rarebit on 02-13-200611:15 AM

The Architect is looking for talented fans to make him a forum signature image. The image must be non-animating .gif, or .jpg format.

Submissions must be posted to this thread by 10:00am PST, Friday, February 24th. The winning submission becomes the property of SOE, and will be hosted on our servers. This is a volunteer fan contest, and no reward will be implied or given beyond recognition for your effort on these forums. SMILEY

Thanks, and good luck!

Message Edited by Rarebit on 02-13-200611:14 AM

Scheduled for tomorrow.

Scheduled for tomorrow.

On a fairly regular basis, I see people casually remark on the forums that the way the Meson Rifles are distributed in the One Zero (medium level) and Zero One (high level) constructs is "bugged." I'm sure this is done innocently enough, but few things can irk a developer more than players spreading, albeit unintentionally, negative misinformation about the game, particularly when it's something that the developer took some pains to straighten out months and months ago, and when the misinformation is promulgated by well-meaning veteran players who ought to know better than to point the bug stick before double-checking the facts.

I think the confusion probably arises from the naming convention used for these weapons. From the names, you might assume that the power curve for Meson weapons would go like this:

Light Meson Rifle
Light Meson Rifle Mk II
Meson Rifle
Meson Rifle Mk II
Heavy Meson Rifle
Heavy Meson Rifle Mk II

Or maybe like this:

Light Meson Rifle
Meson Rifle
Heavy Meson Rifle
Light Meson Rifle Mk II
Meson Rifle Mk II
Heavy Meson Rifle Mk II

But, in fact, it goes like this:

Light Meson Rifle
Meson Rifle
Light Meson Rifle Mk II
Heavy Meson Rifle
Meson Rifle Mk II
Heavy Meson Rifle Mk II

Why? Well, these guns were made way before I was involved in that part of the project, so I don't really know. But here's what the guns actually do:

Light Meson Rifle (4 DPS, 5% stun)
Meson Rifle (9 DPS, 5% stun)
Light Meson Rifle Mk II (9 DPS, 10% stun)
Heavy Meson Rifle (11 DPS, 5% stun)
Meson Rifle Mk II (11 DPS, 10% stun)
Heavy Meson Rifle Mk II (11 DPS, 12% stun)

As you can see here, the important thing to realize is that the Mk I and Mk II series overlap: while each series tends to ramps up in terms of DPS and stun chance from Light to Heavy, in terms of the most standard measurement, DPS, which affects every shot, the Heavy Meson Rifle (Mk I) is more powerful than the Light Meson Rifle Mk II. If you want to keep the guns straight in your head, it might help to think of them in terms of their stun chance: the Mk I series has a 5% stun chance, while the Mk II series has a 10-12% stun chance. Also keep in mind that we wanted the Taskmasters to have a greater chance to stun. So, because DPS and stun chance (particularly for the Taskmasters) are really what we're concerned about as far as power distribution is concerned, for some time now the weapons have been used/dropped by the construct NPCs as follows:

One Zero:

Light Meson Rifle (4 DPS, 5% stun)
-- Laborer (level 26)

Meson Rifle (9 DPS, 5% stun)
-- Soldier (level 30)

Light Meson Rifle Mk II (9 DPS, 10% stun)
-- Taskmaster (level 40)

Zero One:

Heavy Meson Rifle (11 DPS, 5% stun)
-- Laborer (level 40)

Meson Rifle Mk II (11 DPS, 10% stun)
-- Soldier (level 46-50)

Heavy Meson Rifle Mk II (11 DPS, 12% stun)
-- Taskmaster (level 60)

I hope that clears things up.

Scheduled for Monday.

Scheduled for Monday.

Scheduled for Monday.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

In trying to look something up for CoolIceT this morning I happened across a few useropts settings that can change the behavior of the in-game screenshot function. If you guys already know these, then just call me silly.

Please note that we do not officially support these commands, so use at your own risk.

First, these must be entered, singly or in whatever combination you want, in a "useropts.cfg" text file in your game directory (the one your screenies get saved to by default). They might be case-sensitive, I'm not sure. Here are the commands and their default values:

ScreenShot_Filename_Base = "./screenshot"

This can set the name of the root filename of your screenshots. The default saves them as "screenshot_0.jpg," "screenshot_1.jpg," etc, in the same directory as your game client. I tried

ScreenShot_Filename_Base = "./screeny"

and sure enough, it started saving out my screenshots as "screeny_0.jpg," "screeny_1.jpg," etc.

Now, I'm guessing that you can also change the directory they're saved to by messing with that "./" part at the beginning, but I didn't try that myself.

ScreenShot_JPG_Quality = 85

This sets the quality level of your jpg screenshots. If you want smaller files (but blurrier images), lower the number. If you want sharper images (but potentially much larger files), raise the number.

ScreenShot_Pan_Enable = 0

This is where things get...a little weird. Set this to 1, and then when you press the usual screenshot key, instead of just one screenshot, the game will take a series of them. They are taken from what the game considers your character's exact middle, which is somewhere around navel height (doesn't matter if you're standing or sitting, it's always at the same height relative to the ground at your feet). I suggest you sit or go invis or both, unless you just want a lot of images of the inside of your RSI.

Also, it seems that for reliable results with panning screenshots, you have to run in Windowed mode (check the box in your Video Options panel) while taking them.

If you just set the setting above to 1 and press the screenshot key, you'll get a bunch of distored screenshots of seemingly random angles. That's because the default settings are rather bizarre. In fact, I could really only get one specific set of options to give me non-distorto screenshots for a horizontal pan group (didn't try vertical). Here are the panning options and their default values:

ScreenShot_Pan_FOV_X = 120
ScreenShot_Pan_FOV_Y = 45
ScreenShot_Pan_Segs_X = 4
ScreenShot_Pan_Segs_Y = 2

What I finally got to give me decent images of a horizontal pan was:

ScreenShot_Pan_FOV_X = 360
ScreenShot_Pan_FOV_Y = 30
ScreenShot_Pan_Segs_X = 9
ScreenShot_Pan_Segs_Y = 1

This results in nine screenshots, taken as if a camera was rotating in a circle at your waist, taking screenshots at regular intervals.

You'd think that those options would let you change the number of screenshots and so forth, but when I tried any other values, I got distortions. If you guys want to experiment, well, good luck, and remember that these are unsupported options.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

Scheduled for tomorrow.

This is another useropts.cfg parameter. See this post for more details on the useropts.cfg file, if you don't know what that is.

This setting is not supported! Use at your own risk.

A long long time ago, someone asked me in the Ask the Devs thread if there was a way to turn off the light around the character at night, so that you could get screenshots in nice dark darkness. I didn't know how to do that at the time, but eventually I found out that it can be done with certain useropts settings that control that light around your character at night.

PlayerFX_LightPool_Proj_Angle = 1.8
PlayerFX_LightPool_Radius = 5
PlayerFX_LightPool_Bright_Scale = 0.915

If you set

PlayerFX_LightPool_Bright_Scale = 0

then the light will be gone. The other parameters tweak the size of the illuminated area, more or less.

This is a modification to your useropts.cfg game option file to achieve a wacky visual effect. For more about the useropts.cfg file, see here.

This option is unsupported. Use at your own risk.

The useropts line is

wr_envdaylength = 3600

At least I think that's the default. The number is the number of seconds a day lasts. If you lower it to, say, 20, you'll see the sun and moon racing through the sky, ambient light changing, your shadow racing circles around you, and so forth. Like what happened at the end of beta, if you were around for that.

Conversely, raising the number slows the weather's time down. So if, for instance, you logged in to the game and found it that nice blue day we get once a game-time week, you could log out, jack up the number (I usually just hold 9 for a while, ie 99999999999999999999999), and then go back in and enjoy the weather for as long as you wanted, until you jacked out again.

This will, of course, get your weather out of sync with everyone else's. The weather will resync every time you rejoin the server.