MechLean on 10/12/2003 at 19:36
Looking through the ini, d2u, and exe files in the DXIW folder with a text/hex editor, I've found MANY references to leaning.
LeanLeft and LeanRight are the necessary key commands. There are references to:
DX2Game.d2u(96): MovementState_LeaningLeft,
DX2Game.d2u(97): MovementState_LeaningRight,
DX2Game.d2u(105): MovementState_CrouchLeaningLeft,
DX2Game.d2u(106): MovementState_CrouchLeaningRight
DX2Game.d2u(139): var() float LeanThreshold "The cutoff point for stick based leaning/strafing. This is the percentage of the stick that must be applied to switch from lean to strafe. Ranges: 0.1 - 0.9";
DX2Game.d2u(143): var() float LeanOffset "The offset in Unreal Units on the X axis when leaning.";
DX2Game.d2u(144): var() float LeanTransitionSpeed "The speed in Unreal Units per second to use when transitioning to or from leaning.";
I've since configured my keys so that they include leaning according to the necessary flags. (Double checked to confirm proper notation).
Unfortunately, it seems that one key item is missing, but I'm unable to find what it is. Leaning seems to have as much reference as crouching (minus the visibility changing effects of crouching). It is probably some key hard-coded function that is removed (SPECULATION: probably a hack to avoid object collision bugs).
AI is coded somewhat to be able to lean as well as sit and fake being disabled (these last two might be in the game, but I haven't noticed them yet).
OFF TOPIC: AI looks to be very good (evidence and inference), check AICore.d2u for the very large list. If only they would bark at you more when they decide you're a thief as opposed to a killer, etc.
Overall: No leaning, along with small levels being kept for the PC and AI problems, seem to indicate that the release was forced. So close to being so much better, especially since most of the work appears to have already been there.
MSX on 11/12/2003 at 07:43
Actually there's code for a light gem as well. Course, were missing the graphic for it. Test groups said they were playing the gem... but as you'll notice now ion storm is looking for NEW testers lol. So I'm thinking the old ones got canned or something.
Yeah the game was probably forced. Who knows the answer. The Xbox knows.
The sad part is I'm guessing because they couldn't deliver to the UK their going to get a better version than us north american folks. Which means were probably going to have to download a 400mb patch. Hmm, should I change that to hopefully?
All in all its a sloppy release. Just look at the little card saying special songs are on the DVD. What dvd? The X-box DVD. Yeah that's what I thought. Retarded crap like that just stinks with this release.
I'm not sure why they did this. To the x-box DX is just another game...
Edit: Ah shoot. My point to posting. If you have Raven shield you could scourge up the leaning answer from there. If you don't own it I might be able to send you the ini. Here's an exert from the user ini.
Aliases[8]=(Command="Button m_bRotateCW",Alias="RotateClockWise")
Aliases[9]=(Command="Button m_bRotateCCW",Alias="RotateCounterClockWise")
If its a similar system you could just plug the controls into the user ini.
easterlingman on 11/12/2003 at 13:54
You forget that DX:IW and T3 will be using very similar engines.. there are many references to T3 in the DX2 ini files, but that doesn't mean leaning was ever intended to be part of the game.
MSX on 11/12/2003 at 19:21
Actually they were saying in older interviews that leaning was implemented... same with the light gem. STREAMLINED!
The engine's should be the same... With T3 in (3 months?) they should be playtesting right now. T3 is probibly just a little more mature with bugfixes I'd bet.
MechLean on 11/12/2003 at 22:04
The best explanation I've heard as to what happened with Deus Ex 2 is this:
They starting working on the PC Version first, then concentrated on the XBOX to get it working. Stayed a bit too long with it maybe and Eidos noticed they had an almost finished XBOX game, and noticed that December was coming up, so heavily suggested they get it done by then. The original plan was to go back to concentrating on the PC (for larger levels, slightly different interface, all those things we've been promised). Unfortunately, they promised a simultaneous release of XBOX and PC, and became strapped for time, so we ended up with an XBOX version for the PC.
My apologies if where I have read this is this very same forum.
MSX: Do you have DXIW? I'm wondering if you've tried this already. (Don't have Raven Shield myself).
Azal on 12/12/2003 at 01:16
Quote:
Originally posted by MSX The sad part is I'm guessing because they couldn't deliver to the UK their going to get a better version than us north american folks.
Change "UK" to "rest of the entire fscking world" and you'ld be right.
It beggars belief that, in this day and age, a computer game cannot have a simultaneous global release. Hell, with half an hour and an ISO, they could email it to their distributers in each country - problem solved.
However, given all the apparant problems experienced by PC users, perhaps -in this lone case- a delay is actually for the best.
aville on 12/12/2003 at 03:20
Mmm, i doubt that. The bad thing is that ISA seems to be totally satisfied with the game as it is and stands behind it. It goes without saying that no matter how frank they are, they won't come out and say stuff like "yeah its a console port" or "we didn't give too much attention to the pc version".
I reckon they'll only implement the patch in the, say European version and that will be it. Now if that patch turns out to be a major one with many changes (and a few extra levels perhaps? :D ), remains to be seen. In any case, its sad to be happy about getting little details (like leaning or quicksaving) as a bonus when the original one had them as standard. :nono:
Alamar on 12/12/2003 at 12:02
Quote:
Originally posted by Azal It beggars belief that, in this day and age, a computer game cannot have a simultaneous global release. Hell, with half an hour and an ISO, they could email it to their distributers in each country - problem solved.
It's not quite that simple. For distribution to a non-English speaking country, all the game text has to be translated and in-game speech re-recorded (or sub-titled). Publishers seeing that the US-English version is ready think "Hey, let's release this version in the US, then release the foreign versions in their respective countries once they're translated.". Hence the earlier US release.
Publishers *could* wait until all foreign-language versions are ready before releasing the game, allowing a simultaneous global release. However, since this generates them no additional revenue - and may actually lose them money, since the game might be pipped to the post by a similar product from another publisher - this (almost?) never happens.
Also, unfortunately, the UK gets lumped in with Europe by many publishers, forcing us to wait for the "European" version. Or to import.
Rogue Keeper on 12/12/2003 at 12:30
Do you really think that every new game released simultaneously in non-English speaking countries has a specific language version? Who would put money in it?
For the biggest releases maybe in Germany, France, Italy, Japan...
But not in the rest of the world.
It's normally a job for fans from these particular countries to make a translation to their own language after some time.
MSX on 12/12/2003 at 17:43
Quote:
Originally posted by MechLean MSX: Do you have DXIW? I'm wondering if you've tried this already. (Don't have Raven Shield myself).
As I've stated in the past. Me and unreal code do not get along. Though I've been mucking around and see if I can get something going. I keep getting error messages in the console so I'm not attaching things(you know if ti doesn't downright crash). I hoped it would be as simple as making key alias for it like so:
Aliases[26]=(Command="MovementState_LeaningLeft",Alias="LeaningLeft") then adding the key its attached too ... and so forth. No beans.
Try download the RS demo(if your on dialup I guess thats a bit easier said than done).
