Recent content by ravachol

I don't know... has someone tried to use the bigger resolution patch with these tweaks? I don't know exactly what this patch does to the engine but I don't see why it wouldn't work. Easy. Not really: it seems someone has found where the program checked for this limit...

It depends what has to be done, I'm not an expert when it comes to directx programming. It would require some research in this field if I wanted to add/alter some functionnalities. On the other hand, if it's only "light" tinkering, it could be quite easy. It really depends on what needs to be...

What I can say after looking at the code: Since the ddraw.dll and dinput.dll are loaded via an api call, it's possible to make proxy dlls that are located in the current directory (I mean it's easier than if the dlls are loaded when the executable is loaded into memory). When the dll is...

To keep the original gameplay, it seems necessary to make use of the engine. Unfortunately, you don't have access to some data that seem essential (r/w access to the fuel level and location of the car). Creating a new car system from script isn't a bad idea but I'm not sure how you would handle...

It's possible to add some fuel to the car from a script (it's done via the metarule function, there must be a macro defined to use it). To remove some fuel, I think you can use a negative value. But I don't know of any way to get the fuel level from a script.

Trying to find the value by searching it in an hex editor won't do it (unless being very lucky). First, you should try to see how the game reacts (can you still earn xps after level 21? if so, can the xps go above the theorical ammount for level 22 but just don't level up). It's pretty clear...

An instruction out of its context doesn't mean anything else than what it does (here: "compare the value in eax with 0xD"). It's probable that this value was a constant in the original code: when you write a program, you usually define constants and use them instead of their values (it's...

Hi, it has been some time since I've last come here. With what you show here, there's no way to tell what these variables are holding. To find out what these vars are, you have to study the code that uses them (how is the variable initialised? where did the value a variable was initialised...

I'll make a new patch when I have the time, Mulligun sent me another algo: ((((base_damage*dam_mult)/2)*cbt_diff_mod)/100-dmg_tresh/dam_div-(((((base_damage*dam_mult)/2)/cbt_diff_mod)/100-dmg_tresh/dam_div)*(ammo_dr_adj+dmg_resist)/100) )/2 (it's the same algo I already implemented except...

1- Yes, I work on the 1.02d US exe 2- I'm not sure there will be anything "final", I just release patches (or infos) for each issue I fix or addition I make. There shouldn't be any conflicts between the patches (just ignore the message about the wrong CRC when you apply more than one patch)...

Ok, I looked at these two perk, if the bug only comes from the fact that range modifier are based on PE*2, this fix should work: http://www.megaupload.com/?d=X5SME08B (however, it needs some testing). About the pathfinder perk: the problem seems to come from the fact that values for terrains...

- Isn't the max range for throwing weapons calculated from the character's strenght? Well, maybe I'll check. - You're talking about this: http://modguide.nma-fallout.com/#Engine009 aren't you? I had alook at these a while ago and I think it's pretty complete, other actions of the perks are...

Ok, here's the patch that change the algo: http://www.megaupload.com/?d=M5ZBTNL4 (needs testing, I may have made a mistake). Glovz: most of theses traits/perks modifies directly the stat(s) they affect so it's not needed to check for them, the function I'm working on isn't the one where it's...

Yes, you're right, the variable I called ammo_dr_adjust isn't just the ammo_dr_adjust. It's (like in your corrected algo) the damage resistance of the target plus the ammo_dr_adjust. It's also possible for the dmg_resist value to be reduced to 40% of its value and dmg_tresh to 72% of its...

So far, the formula for calculating damages is: (((base_damage*dam_mult/dam_div)/2)*cbt_diff_mod)/100-dmg_tresh-(((((base_damage*dam_mult/dam_div)/2)/cbt_diff_mod)/100-dmg_tresh)*ammo_dr_adj)/100 base_damage is a random number in range of weapon damages plus an eventual bonus if you have a...