www.tombraiderforums.com

www.tombraiderforums.com (https://www.tombraiderforums.com/index.php)
-   Software Development (https://www.tombraiderforums.com/forumdisplay.php?f=55)
-   -   FLEP custom patches: updates, testing and discussion (https://www.tombraiderforums.com/showthread.php?t=196854)

Lwmte 28-01-13 22:45

FLEP custom patches: updates, testing and discussion
 
FLEP (FLExible Patcher) is a revamped and updated derivative of TREP's custom patches module. It is compatible with TRNG version of tomb4.exe (excluding 1.2.2.7+).

NOTICE FOR TRNG 1.2.2.7+ users:
As it was said earlier, FLEP development is now halted, because Paolone is active again with TRNG updates. Development will remain stopped at least until open-source TRNG version is released. Even if FLEP could be made fully compatible with 1.2.2.7, there is no point in it - because if another closed-source TRNG update will come out, most likely it will break compatibility again.



Latest FLEP version: 1.1.44 (1 Feb 2013)
Custom patch set updated: 1 May 2020


Installation instructions:

1. Download zip archive with FLEP program itself (red button above).
2. Download zip archive with custom patch set update (green button above).
3. Unpack them and put both flep.exe and patches.flp in the same folder with tomb4.exe.
4. Launch FLEP.
5. Do all the changes you want, then press "Modify" button.

P.S.: Unlike TREP, you don't need to manually save preset to store your patch settings, as FLEP automatically saves it to flep.cfg file on exit. However, it's recommended to use presets as a back-up of your settings, in case you accidentally erase or reset flep.cfg to default.

IMPORTANT: custom patch set file (green one) updates more frequently than patcher executable.

Quote:

Originally Posted by HeinzFritz (Post 7542198)
I think you all know it already, but just in case you don't here is the link to LWMTE's site where all his Flep and other patches are waiting to be downloaded:

http://trep.trlevel.de/en/



Additional info and patches

Delta's patches
http://www.tombraiderforums.com/show...&postcount=247

Smoke-emitter patch stuff:
Quote:

Originally Posted by Lwmte (Post 6827370)
I've released particle testing ground some time ago - it's basically test level with two utilities that can change emitter properties on the fly. You can play with all parameters and find the effect you want; then simply write down parameters into corresponding emitter OCB patch in FLEP, and you should get same result! ;)

Quote:

Originally Posted by Lwmte (Post 6601150)
Classic, unmodified TR4 engine, for both PlayStation and PC, uses 8 rendering subtypes (0 to 7) for transparent faces. Here is the full description of them:

0 - Opaque: Used for bars. I haven't yet encountered another references to it in executable. Note that this subtype IS NOT the same as standard opaque texture type, despite the same index.
1 - Transparent: "Solid" transparency only, specified by magenta colour.
2 - Translucent: Classic translucent face, additive operation.
3 - [broken]: Has to be translucent face with inversion operation (darkness). Was workable on PSX, but on PC it produces the same result as subtype 1. Still, it is used for shadow and fadein/fadeout effect, maybe for something else too.
4 - Font & skybox: Bypasses Z test, so either it will be rendered above or behind anything else.
5 - [unused]: Rendering code for this subtype is missing. I suppose it also was used somewhere in PSX version, but in PC version it simply gets ignored.
6 - Wireframe: Says for itself.
7 - "Forced" alpha: Most complicated one. It's standard opaque face with alpha (translucency) value that is taken from global variable. It works like this: if you send opaque/transparent face to renderer with global alpha variable set to 255 (opaque), it will be treated as subtype 1. But if you will simultaneously set global alpha variable to something else, face type will be converted to 7 and transparency will be calculated with global alpha variable treated as second argument.

So what I did is re-used type 5 for new "inversion aka darkness" blending mode. I had some problems with shadow rendering beforehand, so I set 5 for shadows and 10 for anything else, but this bug is now (at least I hope so) fixed.

Quote:

Originally Posted by Lwmte (Post 6616946)
Yes, you can fully customize a bunch of parameters for each smoke emitter's OCB. I'm doing 10 OCBs for both smoke emitter white and black objects, so effectively you will have 20 different smoke emitter objects to customize.

Here's a list of parameters you can edit for each OCB:

1. Start colour (the one that is used when particle is spawned)
2. End colour (used when particle is fading out)
3. Lifetime (how long particle will stay in gameworld)
3. Fade threshold (when particle begins to fade from start colour to end)
4. Fade-out time (how long it will take the particle to fade-out completely)
5. Blending mode
6. Various flags (damage, setting on fire, react to wind, line or sprite, perspective correction)
7. Size (can only be multiplied by 2, i. e. you basically can have only 4 usable sizes)
8. Vertical speed and acceleration
9. Horizontal speed
10. Dispersion

Also, I'm working on implementing horizontal direction depending on nullmesh orientation - this way, you will be able to create all kinds of super-complicated particle emitters, like fountains, local snow/rainfalls, sparkle streams, gas rings, etc. Only thing I'm afraid is that you all will eventually run out of OCB capacity! :D We are very limited with this. If only we had a flexible script mechanism to load it... Do you remember this miraclous project called T4Mod by Larson? Almost everyone forgot about it, but it was much more advanced patcher than TREP or TRNG. It allowed you to do even more complicated and beautiful particle setups, much more advanced than TREP or TRNG ever provided - because it relied on external Lua scripting engine (good to note that Lua is a REAL script language, not "pseudo-script" that is used in TR4 engine, because it basically contains only bunch of static parameters for engine to feed).




Blending modes:
Quote:

Originally Posted by Lwmte (Post 6591700)
So, here is the test level and engine, with which you can test new blending modes 8-10 (mode 5 is set to the same as 10 and used for shadows only, because I faced serious bugs with rendering extra blending modes with fog bulb nearby). Also mode 8 results in missing faces at certain angles, I think there's another switch case or "if...then" branch somewhere to find. Unfortunately, today my whole .udd database for OllyDbg with partially deciphered graphics calls got corrupted, it's a bit demotivating! :hea:

http://trep.trlevel.de/temp/test.jpg

For those who didn't forgot how to use TREP, there's also test custom patches set.

Quote:

Originally Posted by meta2tr (Post 6592285)
More good news, the blend modes all work on moveables, and the shine effect works on all of them too.

In the image below, the top row is newly added moveable. Without shine, it looks the same as the other two rows. When shine is activated, it is visible over all of the face.

https://sites.google.com/site/meta2t...eableShine.jpg

Sorry if this is taking a while, but I still have a few things to test, such as animated texture ranges and mapmerge.

Quote:

Originally Posted by Lwmte (Post 6600948)
Sorry, I have lot of things to do, can't answer to everyone right now! :o Just another thing I have found out regarding fog bugs with translucent faces.

It seems that TR4 engine can't properly render translucent faces in combination with fog. It affects not only new blending modes, but also classic "add" blending mode. Core programmers did a bypass for translucent faces, so they are not affected by fog, perhaps it was too difficult for them to do it properly. When it's OK for sprites, on room faces it looks very awkward:
I think I will leave this behaviour as it is for a moment. Maybe later I will fix this bug.
Quote:

Originally Posted by Titak (Post 6600197)
When I look at the spidersweb through the window, parts of the spidersweb disappear. :confused:
I checked and this has nothing to do with bent faces because all faces of the spidersweb have been triangulated.

It happens because blending subtype 7 which is used for all "forced transparency" faces in game (like look transparency, vanishing enemies etc., and also TRNG's transparency OCBs) discards rendering of all translucent (alpha-blended) surfaces behind the most closer one. It is needed to prevent bugs like this:
It's a pity that this subtype can't render anything translucent behind itself, I think that it is not applicable for room geometry because of this behaviour, and also it's very complicated and fuzzy in code (seems like Core programmers used global variable for alpha value), so I doubt that it can be changed. In simple words, no subtype 7 for room geometry, sorry! :hea:
Quote:

Originally Posted by meta2tr (Post 6600034)
I think there's a problem with the latest (second) patch. The problem I see is that the frame rate for animated textures, instead of being the usual 10fps, has dropped to 2fps.

Don't worry, I just changed framerate for tests, blending has nothing to do with it! :) It is native TREP setting in GFX Customizer 2 called "frame change interval" that does the trick.
Quote:

Originally Posted by meta2tr (Post 6600289)
In my case it is faces that disappear and reappear depending on the view angle.

I see, it should be fixed in latest version. The reason for these disappearing faces (it happens mostly on the edge of the viewport, am I right?) is Core Design used very complicated rendering procedure which was divided into two parts -first one rendered faces in front of you, and second one rendered faces that are on the edge of viewport. I think they did it to produce proper shading and lighting.

Also, with this version we don't need two seperate subtypes for shadows/black smoke and black room faces, so I only left type 5 for shadows, 8 was replaced with funny "intensity=inversion" blend type, check it out! ;) It may come in handy when creating something like X-Ray vision effects or so.
Moreover, latest version fixes corrupted explosion smoke puffs that Heinz pointed to. It happened because certain particles in TR4 engine still refer to missing blending types (which were available in PSX), and by enabling extra blending modes all this hell broke loose... :hea:

Quote:

Originally Posted by ChocolateFan (Post 8048857)

I added some patches to:
  • Change hardcoded healing values of Small and Large Medipack, as well as hotkeys 0 and 9;
  • Fix a small bug in using hotkeys 0 and 9; and
  • Disable those keys.
The most important patch, however, is to restore compatibility between TRNG 1.3.0.0 and FLEP by resizing the infamous icon. I made this patch a dependency of all patches that have to extend tomb4.exe size.
In other words, there will be no more need to use an old tomb4.exe executable.

A small caveat is that NG Center is very smart (not) and will try to bring back the unpatched version on every startup. To fool it, rename NG Center\TRNG\tomb4.exe to something else. NG Center will display an error on initialisation, but it is not to be cared about. Another option is to copy the patched executable into NG Center\TRNG, but this must be done every time tomb4.exe is patched.

Thanks to A_De and CourierNumber6 for testing!

Quote:

Originally Posted by ChocolateFan (Post 8155907)
Question: What is "red icon" tomb4.exe? And "blue icon" tomb4.exe?
Answer: In short, "red icon" tomb4.exe is the executable that FLEP was designed to patch, while "blue icon" tomb4.exe is a new executable that comes by default with TRNG 1.3.0.0.

Question: What are the differences between them?
Answer: The only difference is the icon itself. While "red icon" tomb4.exe has a 32x32 pixels icon, "blue icon" tomb4.exe has a 64x64 pixels icon.

Question: Is FLEP compatible with "blue icon" tomb4.exe?
Answer: Previously, it was not. But today, since the creation of the "Delete tomb4.exe unused resources" patch, FLEP is compatible with this executable.

Question: Can this patch be applied to "red icon" tomb4.exe too?
Answer: Yes, it can. But the icon will change to the icon of "blue icon" tomb4.exe.

Question: What about custom icons?
Answer: Custom icons must be defined after all patching has been done. Since NG Icon Replacer will refuse to do its work, a third-party program will be needed.

Quote:

Originally Posted by JMN (Post 8155914)
Just use TombIDE and everything will work.



Quote:

Originally Posted by ChocolateFan (Post 8058136)
I think it is fixed now.

There are some parameters this time. The masks red, green and blue control how much of each colour component is passed along. The numbers that should be used are these: 255, 127, 63, 31, 15, 7, 3, 1 and 0. And the modes specify if the channel is to be added or subtracted. The values are as follows:
  • Add: 3;
  • Subtract: 43; and
  • Nice crash: 204.
Any other value is untested!

For example, to make an additive yellow, type:
  • Mask red: 255, mask green: 255 and mask blue: 0; and
  • All modes: 3.
And to make a subtractive yellow, type:
  • Mask red: 0, mask green: 0 and mask blue: 255; and
  • All modes: 43.

Quote:

Originally Posted by ChocolateFan (Post 8120622)
Caustics and reflections
There is only one new patch, the vertex shader patch.

Quote:

Originally Posted by ChocolateFan (Post 8121886)
Patches updated, please refer to the previous post: https://www.tombraiderforums.com/sho...&postcount=678.

Changes:
  • Fixed incompatibility with T4Larson's TREP patches;
  • Fixed bug in reflection rooms.

Quote:

Originally Posted by ChocolateFan (Post 8125504)

Patches added:
  • Remap bubble array
  • Single gun with PULSE (bugfixed)
  • Pigtail: gravity
  • Flat shading mode
  • Disable all dynamic lights
  • Remove hardcoded sound when Lara surfaces
  • Fix hysteresis in one click deep water
All of these patches are more or less self-explanatory, but I want to go into detail about the last one.

If Lara is wading and goes into water that is exactly one click (256 units) deep, she continues to wade, and it is necessary to jump up to make Lara know that now she can run. There was a discussion here: https://www.tombraiderforums.com/sho...15#post7942015 about it. Well, indeed Joey79100 was right about the wrong comparison operator.

Quote:

Originally Posted by ChocolateFan (Post 8127972)
By default, the vertex shader patch removes the hardcoded bluish water effect, and the water becomes totally transparent.

If you want to restore it, the first step is to install (if you have not done it yet) Plugin_AkyVMix02. Download it here: https://www.tombraiderforums.com/sho...90&postcount=2.

You will need three rules:

Code:

patchpreset=Vertex shader rule 1,1,-1|2000|1|-1|-1|1|128,224,255|-1|0,0,0|0
 patchpreset=Vertex shader rule 2,1,-1|2000|3|-1|-1|1|128,224,255|-1|0,0,0|0
 patchpreset=Vertex shader rule 3,1,-1|2000|4|-1|0|1|128,224,255|-1|0,0,0|0

Since these rules can be applied in any level, you will have to type these commands in all of them:

Code:

; Set Trigger Type - CONDITION 112
; Exporting: CONDITION(112:0) for PARAMETER(1) {Plugin_AkyVMix02}
; <#> : Parameters=PARAM_ACTUAL_CAM,    1
; <&> : Camera. The actual camera has <#> parameters
; (E) :
; WARNING:
; If you'll give this trigger to other people or you'll use it with a script.txt different than current
; you should add to the script, first of triggergroup where you'll use this trigger, the following line:
; #define @Plugin_AkyVMix02  1
; Values to add in script command: $018000, 1, $70

#define @Plugin_AkyVMix02 1
TriggerGroup=2000,$018000,1,$70
#define @plugins CLEAR

Parameters=PARAM_ACTUAL_CAM,1,FACTCAM_CAM_ROOM,RTYPE2_WATER,IGNORE,IGNORE

Besides, you can make another set of three rules so that they will create an effect of different colour, and write another condition for them. But keep in mind that the more restrictive rules must be before the less restrictive ones in the list.

And these rules will never change load screens because their condition is not Universe.
Quote:

Originally Posted by TR-Freak (Post 8133132)
@ChocolateFan:
You successfully removed wading when Lara goes from 2 click to 1 click water.
Is there a way to do fix the opposite direction, too?

When Lara goes from 1 click to 2 click water, Lara plays the default "Jump in Water" animation even when walking. it would be better to play the animation when lara goes into 2 click water water on a slope (running -> wading)


Quote:

Originally Posted by ChocolateFan (Post 8135620)
Quote:

Originally Posted by Joey79100 (Post 8133303)
Well, if I believed in Santa I would ask for all constants to be customizable. :p
But the ones I often find myself begging for are these ones:
  • Low water landing animation. By default, landing in low water will play the underwater swim to stand animation, we don't have a proper animation for that. (exactly what I suggested in my previous post, I put it here only for consistency).
    Constant: SWIM2QSTND_A, but there is no separate constant for the landing

  • Standing jump grab animation. We already have a patch that lets us customize the frame at which it should start, but we're bound to using animation 96 (jump forward grab animation), instead of being able to have a proper animation. This is stupid because Core actually made an animation, they just didn't use it (animation 29).
    Constant: STARTHANG_A

  • Ledge release animation. It defaults to the jump up animation, so we can't have a transition either. Same story by the way, there is an animation, it's just unused (animation 37 - this one directly leads to the freefall animation though, so it's not possible to release a ledge to grab the one just below if there is one, and you always get the hard fall animation).
    Constant: STOPHANG_A

  • Push/Pull ready frame number. They hardcoded a delay of 19 frames in the push/pull animation before the player can actually start pushing/pulling a block, instead of a proper solution using State Changes. For and AOD style animation, where she doesn't move until she starts pushing/pulling, it adds an unnecessary delay.
    Constant: PPREADY_F

  • Throw flare frame number. I have a different throw flare animation, and well, the length of the animation is already hardcoded to 32 frames, but the frame at which the flare is thrown is also hardcoded to frame 20.
    Constants: FL_THROWRELEASE_F (frame at which it's thrown) & FL_THROW_FRAMES (animation length)

  • Pickup flare frame numbers for every flare pickup animation (to decide at which frame the flare should appear in Lara's hand).
    Constants: PICKUPF_F & PICKUPF_UW_F

I also thought about the following ones, however I don't think they're as important because they are more or less easily fixable with TRNG scripts, or because I don't think anyone ever asked for them:
  • Pickup item frame numbers for every pickup animation (to decide at which frame the item should disappear).
    Constants: PICKUP_F & PICKUP_UW_F

  • Running jump delay removal/customization. When the run is initiated with the start running animation (not from landing, walking, etc, only from stance), the jump is not possible during the start running animation and is enabled only after frame 4 of the running animation is reached once.
    Variable: jump_ok in the lara_as_run() function

  • Dive delay. When on water surface, if you press Jump to dive into the water, there is a delay of 10 frames before the animation is triggered (if you release the key before it's not triggered at all of course). They probably wanted to make it look like she takes her breath before diving.
    Constant:DIVE_COUNT

I think that's all, I'll come back if I can think of more of them. The constants can be found LARAANIM.H and LARAFLAR.H. :)



So, here it is. Pick a tomb4.exe already patched with Delete tomb4.exe unused resources and Extend Tomb4.exe size patches and test in it, carefully because the animation system is in fact a minefield.

The low water landing animation is harder than the others, I still do not know how I would accomplish its modification.

And I have not found the push/pull ready frame number. Can you explain how this delay happens exactly?

Quote:

Originally Posted by Joey79100 (Post 8135633)
Oooooh you did it! :D

Right now I don't have much time to test things extensively, but here are the results for what I've tested:

Quote:

Standing jump grab animation
Animation & Frame: ok!

Ledge release animation
If the patch is enabled, even with default values, it crashes as soon as you release a ledge.

Throw flare frame number
If the patch is enabled, even with default values, it crashes as soon as one of the throw animations (standing, from LARA, or just the arm, from FLARE_ANIM) start playing.

Pickup flare frame numbers
Underwater: (not tested yet)
Land (crouching): (not tested yet)
Land (standing): ok!

Pickup item frame numbers
Underwater: (not tested yet)
Land (standing): ok!
Land (crouching): ok!
Land (low pedestal): (not tested yet)
Land (high pedestal): ok!
Land (hole-in-wall): (not tested yet)
Land (crowbar): (not tested yet)

Running jump delay removal
(not tested yet)

Running jump delay customization
(not tested yet)

Dive delay
Ok! However it is needed to say that value 0 (or below) will "remove" the dive animation completely (the counter is incremented and it's done before the check), so the minimum value is 1, which actually means no delay at all (so I was wrong when I say it's a 10 frames delay, it's actually 9 frames when you consider that).
I'll update the post later when I can make deeper tests. Thank you very much for doing that! :D




Quote:

Originally Posted by ChocolateFan (Post 8138891)

Added patches:
  • Fast alignment
  • Alignment animations

Quote:

Originally Posted by ChocolateFan (Post 8147416)

New patches:
  • Add [Kills] to statistics
  • Global [Kills] Statistics entry
This update still does not have the animation-related patches because Joey79100 is still testing them.

Quote:

Originally Posted by ChocolateFan (Post 8178253)

Added patches:
  • Fast alignment

Quote:

Originally Posted by ChocolateFan (Post 8180221)

New patches:
  • Violent bats

Quote:

Originally Posted by ChocolateFan (Post 8181619)

Added patches:
  • Ladder to crawlspace
  • Motorbike and Jeep explosion in water
  • Remove hardcoded Jeep audio

Quote:

Originally Posted by ChocolateFan (Post 8199224)

New patches:
  • Shotgun ammo parameters
  • Disable manual aiming

Quote:

Originally Posted by ChocolateFan (Post 8200203)

New patches:
  • Enhance torch flame

Shotgun ammo parameters patch cannot be applied alone. Because the inventory still divides ammo by 6, and new ammo you pick up still is multiplied by 6.

If you are using the Classic Inventory plugin, it is very easy to fix this, just set desired parameters in CUST_CINV_ITEM_QUANTITY. But if for whatever reason you want the flat inventory, you will have to check Inventory Customizer - Shotgun 6x Divider OFF patch, and tweak pickup quantities in CUST_AMMO.

Quote:

Originally Posted by Woops (Post 8237345)
Latest FLEP patches:

New patches:
  • Fix cogwheel animation skip

Fixes the skipping of the cogwheel release animation (Animation 323).

Quote:

Originally Posted by ChocolateFan (Post 8237617)
Latest version:.

New patches:
  • Allow crouching while holding any weapon

Quote:

Originally Posted by ChocolateFan (Post 8239664)
Latest patches:
  • FLEP (patches.flp):
  • TREP (patches.drc and syntax.fln):
Under specific circumstances, it is possible to see sprites flickering all around the screen. For example, in Playable Tutorial Level:

https://i.postimg.cc/KKD95gDd/Tomb.png

The purpose of these new patches is to fix this bug.

Quote:

Originally Posted by ChocolateFan (Post 8243428)
Fixed (hopefully) patches:
  • FLEP (patches.flp):
  • TREP (patches.drc and syntax.fln):

Quote:

Originally Posted by Dermahn (Post 8245022)
I added 3 new patches:

Footstep Sound Customizer:
Allows you to customize all special footstep sounds. When you open the patch, you'll see that all sound effects have very low numbers. That is because they're all relative to the "First Sound ID" (this is 288 by default (FOOTSTEPS_MUD)).
That means, if you want to set "Snow" to Sound ID 290, you would set it to "2", because 288+2=290.

"First Sound ID" can be customized so you can place your footstep sounds wherever you want, but keep in mind that the maximum distance between the first sound ID and a footstep sound is 255.

Enable all footstep sound effects
Enables Stone, Water, and Concrete sounds. These are all set to Sound ID 297 by default, so they should be customized with the above patch.

Prevent TRNG Log Spam
This patches the Tomb_NextGeneration.dll!
It prevents TRNG from generating any log files and helps keep the game folder clean. I included this in a separate patch because FLEP will complain if the dll is missing, regardless of whether the patch is selected or not. To use it, make a backup of your patches.flp file and rename patches_NextGen_dll.flp to patches.flp.

patches.flp

patches_NextGen_dll.flp

Quote:

Originally Posted by ChocolateFan (Post 8245614)

Changes:
  • Fixed ESI corruption in Add [Kills] to statistics patch.

Quote:

Originally Posted by ChocolateFan (Post 8278533)
Added patches:
  • Change shockwave damage

Quote:

Originally Posted by ChocolateFan (Post 8299040)
.

New patches:
  • Free camera: Lock
  • Sample file size
  • Sample rate
  • Sample buffer array
  • Reverb
Unfortunately FLEP cannot fix the Grenade Gun bug since TRNG already patches the code where it happens. But TRNG patch copies the bug instead of solving it.

About the reverb patch:To overcome false positive detection by antiviruses, FLEP patches now are applied to the executable memory, as TRNG does. The new workflow is:
  1. FLEP patcher will patch a binary blob called patches.bin
  2. As soon as tomb4.exe starts, flep.dll will read patches.bin and patch tomb4.exe
This tomb4.exe (Lara blinking) is different than standard tomb4.exe (Lara with headset) because it must talk to flep.dll.

As a consequence, these three files should be distributed if FLEP patches are used: tomb4.exe, flep.dll and patches.bin.TombIDE 1.3.14 includes the same files as above for new projects that use TRNG + FLEP engine.

Quote:

Originally Posted by ChocolateFan (Post 8299722)

New patches:
  • 24 Savegame Slots (bugfixed)

Quote:

Originally Posted by ChocolateFan (Post 8300607)
New version.

Changes:
  • Fixed crash in custom presets.
Refer to this post for updated source code: https://www.tombraiderforums.com/sho...&postcount=848.

Quote:

Originally Posted by Krystian (Post 8307870)

New patches:
  • Title menu adjustment

Changes to existing patches:
  • Fixed panning bug in reverb patch
ChocolateFan has fixed the panning bug in the reverb patch.
The title menu patch has been developed by me, you can see an example of what it can do in the video below.


Quote:

Originally Posted by Krystian (Post 8309322)
Latest version:

https://drive.google.com/file/d/1uvI...ew?usp=sharing

New patches:
  • Remove Ahmet flame death
  • Remove Small Scorpion poison hack
  • Remove poison screen effect
  • Show HP bar in inventory
  • Ammo Counter / Flare Timer
  • Fix sound radius bug

Remove poison screen effect patch was made by Troye and Fix sound radius bug patch was made by ChocolateFan. Show HP bar in inventory and Ammo counter / Flare timer patches were ported from TREP.

Quote:

Originally Posted by ChocolateFan (Post 8314507)
New patches:
  • Upward standing jump ledge grab animation
  • Ledge release animation
  • Pickup flare frames
  • Pickup item frames
  • Jump delay
  • Dive delay
  • Crawlspace pickup
  • Prevent camera position freeze
  • Customize sas gun
  • Fix bottom right corner bug
All patches by me, except Customize sas gun, which was developed by Troye.

DJ Full made a nice research about the bottom right corner bug here: https://www.tombraiderforums.com/sho...d.php?t=204738. But Lara can stand anywhere. Just the camera cannot.

Quote:

Originally Posted by ChocolateFan (Post 8319185)
New patches:
  • TR2Main widescreen
  • Fix jumping through objects
  • Static collision
Fix jumping through objects patch was developed by Troye.

Changed patches:
  • Clear menu backgrounds
Clear menu backgrounds patch now can be used normally, although it does not work correctly when used together with classic inventory plugin.

Quote:

Originally Posted by ChocolateFan (Post 8320154)
New version: https://drive.google.com/file/d/15Ul...ew?usp=sharing.

Added patch:
  • Fix inconsistent camera angle when hanging


Lwmte 28-01-13 22:46

FLEP feature list:
  • Some of the TREP animation patches which work better than the TRNG scripting version + it saves Animation= scripts which amount is limited. Disable ledge-climb delay, disable dive delay, quick crawlspace climb, enable crawlspace jump, enable crawlspace roll, enable crawlspace pickup, monkeyswing 180 degree turn around while hanging still and while moving, roll key setting, wall climbing mid-point adjuster (for faster climbing animations like those by Geckokid in his The Beginning demo), grab frame set for standing jump.
  • Clear menu backgrounds, so no more ugly grey stripes in 32 texture depth mode. Includes some customisation options like transparency blending mode, transparency intensity and pick whatever colour you want.
  • New customisable OCB's for the smoke-emitter-white and smoke-emitter-black: we can now have actual black smoke and countless other colours and effects (different speeds, blending modes, lifetime, extra flags like making it react to wind, Lara's collisionbox (sprites move backwards when Lara walks through the sprites), hurt Lara when she touches the sprites, make her burst into flames, etc) within these two objects as well as the option to pick whichever spriteslot you want to use. No manual has been writtten yet, so experiment with the values to see what the values are all for.
  • New transparency blending modes with which you can create different looking "glass" objects (you also need the latest Meta2TR update and/or TRTexture for this)
  • Stylish static bars: customisation of all bars, including custom bars, TRNG scripting is still needed for the colour of the bar itself, its size and position on screen. Do you want TRC style bars? You got it!
  • Smooth shadows with soft edges: pick whatever sprite slot, adjust elevation and darkness of the shadow.
  • Enable DOT3 bump mapping: this type of bump mapping reacts to dynamic lights like flames and flares/PLS lights.
  • Remove green flare tint: customized flares won't produce hardcoded green flicker on flare ignition and depletion.
  • Fix Lara's visibility in binocular view bug.
  • Change shiny sprite: allows you to pick different slots for the shiny effect, one is for the ingame shine effect, the other one is for the inventory shine effect.

Patches directly imported from TREP:
  • Add "Lara's Home" to the main menu.
  • Old school TR1 style teethspike: no more TRNG workaround needed to make Lara play her "impaled" animation when falling onto spikes.
  • Print "Game Over" text on screen when Lara dies.
  • Disable add-on gun sound: removes hard-coded explosion sound from gunfire.
  • Disable sentry gun flame attack.
  • Add [hits] to statistics.
  • Enable ricochet sound effect.
  • Completely disable load and save items: in case you want to use a checkpoint system and/or savecrystals in your game.
  • Fog colour table editor: allows you to enter different colours into the default fog colour table.

God Horus 28-01-13 22:49

OMFG!! *dies*

raiderromero 28-01-13 22:52

Quote:

Originally Posted by Lwmte (Post 6626251)
So, to warm-up this new thread, here is a fresh patch for you: long-awaited CLEAR MENU BACKGROUNDS. Download latest custom patch set update and test it! :)

OMH LMWTE im loving you so much, when will you try the images as loading screen?

Caesum 28-01-13 22:53

OH MY GOD! :yik: *downloads*
Tested, works perfect! Thank you, thank you, thank you! That's something I've been waiting for so long. ;_; Thank you.

About new features... Well... I have a tiny request that's not really that tiny I suppose. I wonder if it could be possible to restore minecart vehicle using FLEP? I heard minecart wasn't added to TRNG because it'd overlap triggers used by mechanical scarab. Yet FLEP has that advantage that you can check whatever you like and bypass everything you do not. It'd be wonderful to have the minecart. Is FLEP capable of restoring it? :o

Tricell 28-01-13 23:10

Yay! This is going to be so awesome!

-Off Topic-
Right after Titak went to bed :vlol:!

JessyTR 28-01-13 23:54

Lwmte, it's not working for me, everything stills the same, idk if this have something to do with the problem, but when I close FLEP, I get a message saying: "Error saving config/ preset file. Check integrity". :(

raiderromero 29-01-13 01:11

Quote:

Originally Posted by JessyTR (Post 6626350)
Lwmte, it's not working for me, everything stills the same, idk if this have something to do with the problem, but when I close FLEP, I get a message saying: "Error saving config/ preset file. Check integrity". :(

copy tomb4.exe in other folder ( create one in the desktop) and also copy all the flep files in that folder, then apply patches, lastly copy paste over the original tomb4 folder , i have win 7 and i had that problem cause win didnt let apply the patches so i had to copy the program in other place

JessyTR 29-01-13 01:44

Oh, I hate the stupid admin thing on win7 :mad:

Shauni 29-01-13 01:47

Ooh so very cool! @_@ Thank you for making it! <3

Shakira Croft 29-01-13 06:57

Incredible ! Thank you so much =)

Raider99 29-01-13 11:55

*faints*

Thank you so much! :hug:

klona 29-01-13 12:54

Thank you so much! :D
I wonder what does DOT3 bump mapping do?
I've used it but nothing changed. (Maybe I'm expecting the wrong thing)
By the way; can you please please make the underwater waves and camera rotation patch available for TRNG? :D

Lwmte 29-01-13 13:08

DOT3 bump mapping changes the way bumpmaps are applied to textures. By default, TR4 engine simply overlays bumpmaps onto textures, ignoring lighting and surface normals orientation. So, what DOT3 bump mapping patch does, is it changes bumpmap blending operation from simple overlay to dot product function (you can read about it here), which results in bumpmaps reacting to lights, their intensity and orientation. You can easily note a difference at the start-up of Catacombs, Cleopatra's Palaces levels in classic TRLE level set, or, in recent levels, King Arthur's Project (when jeep goes through underground area, you can easily spot how jeep's headlights affect wall textures).

The effect is not so obvious because generally TR has no dynamic lights applied to room textures, only static. It could be really awesome if TR supported bumpmaps on movables.

klona 29-01-13 13:26

Quote:

Originally Posted by Lwmte (Post 6626787)
DOT3 bump mapping changes the way bumpmaps are applied to textures. By default, TR4 engine simply overlays bumpmaps onto textures, ignoring lighting and surface normals orientation. So, what DOT3 bump mapping patch does, is it changes bumpmap blending operation from simple overlay to dot product function (you can read about it here), which results in bumpmaps reacting to lights, their intensity and orientation. You can easily note a difference at the start-up of Catacombs, Cleopatra's Palaces levels in classic TRLE level set, or, in recent levels, King Arthur's Project (when jeep goes through underground area, you can easily spot how jeep's headlights affect wall textures).

The effect is not so obvious because generally TR has no dynamic lights applied to room textures, only static. It could be really awesome if TR supported bumpmaps on movables.

I wonder if it would work on the Flares or LED Light!? :eek:

Suikaze Raider 29-01-13 13:42

Thanks Lwmte :)

I just tested your Clear Menu Backgrounds with default settings and works fine :) I noticed if it's raining, the rain particles don't stop when the game is paused or in inventory :confused: And if it's fogged, it dissapears when you are on inventory or pause, but if you enter to load or save options appear :confused: But I think those things are from engine :)

This patch could be ported to final TR4 & TR5 Games? I tried it, but it doesn't work, the game always crashs :hea: And on TR5 I can't find the long code patch, but maybe the code is diferent :confused:

Another thing... TR4 Engine has a bug with explosive ammo :hea: When you shot a freeze dog (OCB: 1) or a mummy on floor (OCB: 2), the game always crashs. This happens in TR2 with jade freeze warriors too :hea: That bug could be fixed? :)

Cheers :)

Lwmte 29-01-13 13:51

In TREP version, backgrounds patch bypassed rain and snow routines, so they didn't show up under backgrounds, with TRNG version I can't do so (because rain/snow procedure is in dll). As for fog issue, yes, there is a problem indeed; another possible problem is poisoning "trip effect", which also corrupts background. I guess, these are the bugs to be fixed in the future.

As for porting patches to TR4 / TR5 versions, this is something really simple, but you need to know basics of assembly language and OllyDbg usage. Only thing that is needed is to correct addresses of functions and variables.

I never knew about grenade bug though; will check it out! ;)

klona 29-01-13 13:52

Quote:

Originally Posted by Suikaze Raider (Post 6626825)
Thanks Lwmte :)

I just tested your Clear Menu Backgrounds with default settings and works fine :) I noticed if it's raining, the rain particles don't stop when the game is paused or in inventory

I saw that too.
I find it cute, tbh. :vlol:

Lwmte 29-01-13 14:02

Quote:

Originally Posted by klona (Post 6626814)
I wonder if it would work on the Flares or LED Light!? :eek:

Yes, however, effect is not too noticeable, because only bright heightmap zones are affected. I will try to modify rendering pipeline, so effect will be more noticeable (currently TR4 engine does 2-pass rendering, and I will try to add third pass for bumpmap shadows).

teme9 29-01-13 17:00

Wonderful patches!! You truly have a way of getting around problems :D I wouldn't be much suprised if you're going to do something really mindblowing soon :D Thank you!

bekim 29-01-13 17:18

Not sure if you noticed in the other thread..........:o

But seriously I would be awesome , if you could make a patch that disable the CROSSBOW bolt shatter and make it stick in the wall collision Like TR3 Instead.

:tmb: The patches are awesome , I can't stop having fun with them <3

HeinzFritz 29-01-13 17:20

There is an absurd issue with the flyby camera with code bit 5 selected (flyby camera follows Lara when she is moving). The problem is that the camera's focus is on her feet and the canvas has a bad balance and is discomposed, which makes this, otherwise useful setting, possible only from a considerable distance.
I wonder if this default camera setting could be raised so the focus will be Lara's head? All experiments I made in this direction have proven fruitless.

-Roli- 29-01-13 17:31

I'm so glad to the latest patch (too). :D Thank you! :hug:

Quote:

Originally Posted by Lwmte (Post 6626845)
Yes, however, effect is not too noticeable, because only bright heightmap zones are affected. I will try to modify rendering pipeline, so effect will be more noticeable (currently TR4 engine does 2-pass rendering, and I will try to add third pass for bumpmap shadows).

Great, can't wait! :D
Already wanted to use your DOT3 on my Revelations IV project, but the bump looked good in the bright areas only, and the flare doesn't affected well. So this fix will be amazing! :)

teme9 29-01-13 17:32

btw... Any idea if the Opaque bloodsprite effect would be possible to transfer from trep to flep? It is one the patches which I truly love. It makes a huge difference in the blood :D (is it jelly or blood :vlol: )

Caesum 29-01-13 17:33

Minecart is impossible I understand? :o Oh well.

How about making something with objects that flashes(I mean disappear and reappear again) if they are several rooms beyond Lara? It's very irritating, especially when you have big objects!

Tombraider95 29-01-13 18:07

wow thank you very much. This will defo come in handy.

So we can request patches? What can't you do? :p

ggctuk 29-01-13 18:20

Wow, that's sure a lot of patches you've got up and running already!

Is that Teeth Spikes behaviour patch the same as the original Old School Teeth Spikes 1 patch, or does it incorporate anything from the original patch 2 or 3?

GeckoKid 29-01-13 21:46

Quote:

Originally Posted by teme9 (Post 6627082)
btw... Any idea if the Opaque bloodsprite effect would be possible to transfer from trep to flep? It is one the patches which I truly love. It makes a huge difference in the blood :D (is it jelly or blood :vlol: )

Or rather, use the inverse multiply mode :D

Lwmte 29-01-13 21:58

I have updated patch set (green link in the first post of this thread), now clear menu backgrounds should support fog bulbs (before they were invisible in inventory background).

As for distance fog, it seems that TRNG intercepts this value when entering menus and forces it to certain value (I guess that it is done to prevent inventory item pollution with fog on low distance fog values), that's why there is no distance fog in menu backgrounds.

Delta 29-01-13 22:37

Thanks for this patch Lwmte :)
It's not important but the electricity continues to move a bit in the menus with this patch.

Quote:

Originally Posted by teme9 (Post 6627082)
btw... Any idea if the Opaque bloodsprite effect would be possible to transfer from trep to flep? It is one the patches which I truly love. It makes a huge difference in the blood :D (is it jelly or blood :vlol: )

It's included in the "GFX1 Customizer" patch I'm working on, unlike TREP you can also choose the render type :D

Lwmte 29-01-13 23:22

I have updated patch set again, seems I have to freeze both randomizers... That's the reason why electric arc was shaking! :D

Also, I have fixed stylish bars positioning... Not that I'm happy with it, because TR5's position calculation formula was better, but at least now it should be fully compatible with TRNG bar annotations! ;)

raiderromero 29-01-13 23:25

Quote:

Originally Posted by Lwmte (Post 6627658)
I have updated patch set again, seems I have to freeze both randomizers... That's the reason why electric arc was shaking! :D

Also, I have fixed stylish bars positioning... Not that I'm happy with it, because TR5's position calculation formula was better, but at least now it should be fully compatible with TRNG bar annotations! ;)

really? gotta try :jmp:

Delta 29-01-13 23:39

Perfect, also the electricity is frozen now, but I noticed another one :o (not important again): the underwater dust is still enabled but every particle vanishes in very few time.

I cannot test the text for the stylish bars now, but the loading bar is restored :D

Anyway are you planning to build a tool like DRCMerger? I'm adding these patches taken from TREP but you're updating the patches.flp with new patches

raiderromero 29-01-13 23:47

excuse me where do i costumize the bars on flep cause in blending modes there i snothing of that?

there is only :

To understand source / dest blending operations, search for D3DBLEND enumeration page on MSDN.

:confused:
NVM i did it hehe

Lwmte 30-01-13 00:36

@Delta: the reason why we have these problems with underwater dust, lightning, rain and snow particles is that Core programmers didn't separated update routines from drawing routines; so basically they are updating in the same routines they are drawing.

I did a bypass for TRNG rain / snow and underwater dust routines though in latest custom patch set revision. Gosh, it feels like I'm walking on a minefield trying to "wrap" all these scattered TRNG calls! :pi: But so far it works normally.

As for DRCMerger... Yes, I think, eventually I'll port it to support .flp files! :D

THOR2010 30-01-13 02:47

question about the TRC stylish bars, are they transparent nomatter what or can that be changed?

raiderromero 30-01-13 03:20

Quote:

Originally Posted by THOR2010 (Post 6627874)
question about the TRC stylish bars, are they transparent nomatter what or can that be changed?

no in fact you need to play around with the values and parameters so that you can have a desired style:
* border parameters will only change the border (line outisde indeed lol)
* the background parameters will change the appearence of what is inside the bar ( behind the bar full or empty, i said behind but actually if the bar is full this parameters will be over current bar so i can say that this parameters are behind and in fron of current/old bar) be careful cause if you put colors everywhere your original bar will look a mess and will not be so visible because new colors will be covering the old color.
* the active bar render type doesnt do that much (in my experience) if you change this value nothing will happen but ugly black bars,
* background render type maximun value seems to be 30 and gives sort of transparence, but i also noticed different types of bars with values 4 2 -10 8 15
* Border render type will also add transparence to the border (when increasing the number) if you increase it too much it will disappear, a razonable number would be bewteen 0 and 10 (if i remember correctly)

Lwmte 30-01-13 09:51

Well, almost... :)
Background render type can be set up to 14, it corresponds blending modes listed here, plus new blending modes. So, to set up transparent bars, you need to play with combinations of 2, 5, 8, 9 or 10 blending modes for both backgrounds and active bar.

I wish I could write a manual about all this, but I have no time.

Titak 30-01-13 12:05

Quote:

Originally Posted by Tricell (Post 6626292)
-Off Topic-
Right after Titak went to bed :vlol:!

:vlol:

Good thing Wednesday is my day off from work. :D

Although testing this thing will have to wait.
I already lost time today because of getting groceries and a new mouse (the wheel on the old mouse did not scroll properly anymore) and I also, finally, bought a KVM Switch so I can have both my coputers running and easily switch from one to the other. :D

Anyway, the update looks very promissing.
I'm going to test it some time today for sure! :jmp:

raiderromero 30-01-13 16:46

you should also remove :

However, please note that this patch disables loading bar.

cause thats not happening anymore :D


All times are GMT. The time now is 11:27.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, vBulletin Solutions Inc.