tiger@sound.net on 21/3/2006 at 04:12
Thanks, New Horizon, but that's sad news.
(Btw, the first version of Quake started all of these "alias mods" for me.)
Using basic alias, with rebinding logic, you can do a small world of game-mods.
Like above, when I simply added two easier "movement modes", as basic toggles-switches, and aimed especially at your PC keyboard-and-mouse users.
(Ps, for Postal2 STP, I added a lot of different mode-exits or "escapes" within that Normal alias.)
So, I guess when my T3 shows-up, I'll just be another strange DS thief, who is either crawling around or he is up and running around. :(
***
Since T3 is not UnReal then these two in-game fixes will probably not work?
Pause=obj garbage|flush|Pause
(This seems to cleanup some slow-running and twitchy stuff in Postal2STP.)
And we can use the spacebar to exit this Pause mode, btw.
***
tiger@sound.net on 21/3/2006 at 10:34
And I'm very glad that you posted it, S_Hole, because this seems to work great at very low resolutions (down to 640x480 32bit color) and for a test, with the game-brightness turned all the way, up. . . So, MUCH THANKs! :thumb:
tiger@sound.net on 21/3/2006 at 10:48
Quote Posted by Jahandar
If you don't like the weird tinted look you get when you zoom with your mechanical eye (I do, but it may annoy some people), you can remove this effect by editing you DEFAULT.INI file.
Look for the [CameraOverlays] section.
It looks like this...
[CameraOverlays]
EnableCameraOverlays=true
CameraOverlay_0__t=MechEyeOverlay
You can either set EnableCameraOverlays to false, or set CameraOverlay_0__t to 0. Both will do the trick, but the latter has the least chance of effecting anything else in the game.
(BTW, Jahandar, I am trying to stay away from possible game-play problems with some mods and enhancements because I'm new, I only have the demo and I don't want to ruin my first game-experience when I get T3, this week.)
But your mod as, "CameraOverlay_0__t=0", seems damn near perfect, mate!
And it gave me some very entertaining views of those T3 guards. THANKs! :thumb:
tiger@sound.net on 22/3/2006 at 04:25
(From Mentalepsy's list on the first page.)
Quote:
- Allow the 'Stats' option to be accessed from the objectives menu (ie, at all times), instead of just the end mission menu.
This Stats option might be pretty important for a lot of new players, who are attempting to learn what T3 Ghosting is really all about?
Because I had this somewhat amusing bit of anti-ghosting confusion, while I was playing the castle within the T3 Demo.
[SPOILER]While in the room's doorway, at the very top of the tower, I watched as an easily scared "Lady In Waiting" proceeded to kill that very tough guard, who is usually patroling the tower's stairs. (But, now, he was trying to find me, with her persistance, btw.)[/SPOILER]
And, honestly, I really wanted to congratulate her, right there and then!
But then, I almost died laughing at the anti-ghosting "results" of her actions.
(Because I, myself, didn't hurt a soul or leave a body, around, to be found.) :cool:
***
Btw, I just did a general search for the T3 demo.
But I couldn't find a message that got into its unusual happenings or problems?
Usually, I am enjoying a fine and fast-moving game with the demo, at about 35 FPS to high 40s, until I run into their weapons room, that very obvious armory with lots of swords, boxes and four special outside-light sources. And then, suddenly, I'm doing some sort of slow motion jogging within that room? (This starts at 10 FPS and then slides down to 7, even.) :confused: And yes, I have just updated my graphic-drivers and re-installed T3, simply to see a zero change.
***
jtbalogh on 25/3/2006 at 09:43
Regarding books:
1. Turn the page of a book by clicking anywhere on the bottom left or right side of the screen and not just using the arrows. The middle and top half are not available since hardcoded into T3 regardless of the INI settings << EDIT: wrong as stated in next post.
2. Turn pages with a single click instead of a double click. Sometimes clicking on the arrows a few times required a double click which is annoying. WARNING: must wait for page to turn and redraw before turning again or else a double click is required. Pages are heard turning but may not always.
3. Lower buttons to bottom of screen under book. Move previous button to left of screen since stupid to have at right side.
Code:
In T3UI.INI,
[PrevPageButton]
Placement_X=LEFT
Placement_Y=BOTTOM
Pos_X=100
Pos_Y=-25
Pos_Z=-5
Scale_X=1.0
Scale_Y=1.0
Scale_Z=1.0
ButtonPressX=1 ; 0=double click, 1=single click
ButtonPressY=1
ButtonPressZ=1
AutoUnpress=FALSE
UOffset=0.50 ; same for both buttons
VOffset=0.875
BBOffset_Left=-100 ; larger overlay
BBOffset_Right=200
BBOffset_Bottom=-100
BBOffset_Top=600 ; high numbers do not work since maximum remains at bottom of page
[NextPageButton]
Placement_X=RIGHT
Placement_Y=BOTTOM
Pos_X=-100
Pos_Y=-25
Pos_Z=-5
Scale_X=1.0
Scale_Y=1.0
Scale_Z=1.0
ButtonPressX=1 ; 0=double click, 1=single click
ButtonPressY=1
ButtonPressZ=1
AutoUnpress=FALSE
UOffset=0.50 ; same for both buttons
VOffset=0.875
BBOffset_Left=-200 ; larger overlay
BBOffset_Right=100
BBOffset_Bottom=-100
BBOffset_Top=600 ; high numbers do not work since maximum remains at bottom of page
New Horizon on 26/3/2006 at 03:57
Quote Posted by jtbalogh
Regarding books:
1. Turn the page of a book by clicking anywhere on the bottom left or right side of the screen and not just using the arrows.
The middle and top half are not available since hardcoded into T3 regardless of the INI settings.Not true, this can be changed in the .ini file as well. Just requires some experimentation. I have books, letters, and scrolls divided straight down the middle in T3EnhancED. You can click on either side to turn the pages.
Here are my settings.
Code:
In T3UI.INI,
[PrevPageButton] ;**
Type=ButtonActorWindow
Rot_Pitch=16384
Rot_Yaw=-16384
Placement_X=Center
Placement_Y=Center
Pos_X=-110 ;75
Pos_Y=150
Pos_Z=-575 ;575
ActorVisibleName_Normal=ScrollArrow
Active=VISIBLE
ActorVisibleSkinIndex_Selected=1
ActorVisibleSkinIndex_Pressed=1
ActorVisibleSkinIndex_Normal=0
ButtonPressX=0
ButtonPressY=0
ButtonPressZ=10
UOffset=0.25
VOffset=0.875
ButtonSoundSchema_Selected=ui_highlight_a
ButtonSoundSchema_Pressed=ui_bookpage
BBOffset_Left=-100 ;20
BBOffset_Right=100 ;5
BBOffset_Bottom=-400 ;15
[NextPageButton] ;**
Type=ButtonActorWindow
Rot_Pitch=-16384
Rot_Yaw=-16384
Placement_X=Center
Placement_Y=Center
Pos_X=75 ;-110
Pos_Y=150
Pos_Z=-575 ;575
ActorVisibleName_Normal=ScrollArrow
Active=VISIBLE
ActorVisibleSkinIndex_Selected=1
ActorVisibleSkinIndex_Pressed=1
ActorVisibleSkinIndex_Normal=0
ButtonPressX=0
ButtonPressY=0
ButtonPressZ=10
UOffset=0.5
VOffset=0.875
ButtonSoundSchema_Selected=ui_highlight_a
ButtonSoundSchema_Pressed=ui_bookpage
BBOffset_Left=-100 ;5
BBOffset_Right=100 ;20
BBOffset_Bottom=-400 ;15
tiger@sound.net on 26/3/2006 at 07:46
Excuse me, New Horizon, but what of this?
Quote:
...............................................................................................
XBOX - Move the thumbstick just a little to walk slowly and very quietly.
PC - Use WALK to move slowly and very quietly.
Use CREEP to move even more slowly and be completely silent.
To me, this basically shows that our PC version, that I just got, is lacking some very nice XBOX controls for our more "natural game" enjoyment. And by now, that should have been modified, as latching-mode keys, like our current Crouch mode. (And they really should have used that 1.1 patch for more then simply fixing their T3's level of difficulty "mistake".)
(And why am I complaining?) ;)
That Crouch mode naturally fits-in with creeping around the Rutherford Castle.
But it felt very strange, and even a bit silly, crouching around the streets of South Quarter with "normal folks" simply walking around me, mate.
(And No. . . Holding Shift or Ctrl, all the time, does not feel "natural".) :erg:
(And yes, I have seen all those marginal "speed-adjustment attempts".)
And if T3 wasn't so XBOX oriented, with the lack of aliases and such, I would have simply fixed it, in my first message above, like I have done with the Quake series from their very beginning, folks. :confused:
Heck, with Quake, I would have turned that Couching-mode key into a four-mode toggle-key containing Run, Walk, Creep and Crouch. And then I probably would have used an optional Say (for UnReal) or Echo (for Quake) command, per mode, for some temporary screen-text to tell the player what mode they are currently in.
(And then, I would have extended my new "Normal" alias, above, to set the normal Run mode, with a normal view, perhaps and then reset my four-mode key to Run and we're basically DONE!) :)
