Thank you for the wonderful mod, I've followed the install guide to best of my ability on mod manager page. The physx particles all stay for the alloted time which is way longer only thing is the more blood section particles and blood on the ground don't stay no matter which setting I apply there is extra blood but it disappears after a few seconds. I hope you can help me, please say if theres any information you need I'm just using the community patch and your mod.
"Remember, this mod mostly run on the CPU, not GPU. I run a intel i7-4790 3.60GHz and have good performance."
The only way one can play with this much of the unoptimized Physx in BL2 and still get good frame-rate is if you have an nVIDIA GPU, preferably paired with another GPU.
Nothing you or anyone else can do with a mod can make this game run CPU Physx well, because the engine is single-threaded.
I'm guessing your mod is just some changed values in willowengine and willowgame? I know the exact lines and values for particle count and corpse time.
"Blood pools, limbs and alien blood splatter stay for 1 hour"
I have the i7 CPU and run a 1080Ti card from Nvidia. Safe to say that the CUDA engine in nvidia cards are helping, but not by a lot. Remember CUDA engines where meant to support the OLD EVGA Physics engine used way way back when physics became a thing in games. After EVGA physics failed and shut down they use CUDA ONLY for their new Flex and hair rendering. Mean while they have found other way (hence, HAVOK) to render basic physics on video and cpu memory. I don't get why you are so hostile against all this.
Either way, what you're saying is wrong, few years after the release of Borderlands 2, Nvidia has also been removing the CUDA lock on their cards, so AMD users can experience physX features on AMD CPU's, but only running strictly on the CPU. (this would ofc impact performance tho)
Then agian the engine is so old, that the only way physX was playable back them was if you had TOP tier hardware. Now this is not a problem anymore. CPU's these days are powerful enough to handle the extra PhysX strain that this mod provides. Even if the game engine it's single-threaded.
You dont need a "nasa" meme pc to run it.
Also No, you guessed wrong. it's not just a simple edit of the Willowengine ini files. Any edits made on the Willowengines will reset when you launch the game, since the main preset which the game is programmed to follow are in the archives.
And i don't know about you, but i can guarantee that other people, inc me finds it annoying that the static blood stain disappears after 10 seconds is annoying. There is no reason why it shouldn't be longer, as it takes NO performance from the main experience as much it takes away immersion.
"Either way, what you're saying is wrong, few years after the release of Borderlands 2, Nvidia has also been removing the CUDA lock on their cards, so AMD users can experience physX features on AMD CPU's, but only running strictly on the CPU."
I'm sitting here with a RX 580 8 gig GPU, and an overclocked i7 CPU. I'm playing BL2. I'm telling you BL2 today, with the latest version on Steam, still runs like garbage on CPU handled PhysX Medium, and that's without your mod upping the ante. Nothing has changed. In fact, it got permanently worse after the pirate booty DLC made the particle system even more unoptimized and Gearbox has never bothered to fix it.
BL2 is 32-bit, and single-threaded, taking no advantage of multi-cores or even hyper-threading. The PhysX in this game has to be at least partly offloaded to a GPU, or else it cripples the CPU, period
Modern CPUs are powerful because they have multiple physical cores. BL2 simply isn't coded to use them, and clock speed only takes you so far.
"annoying that the static blood stain disappears after 10 seconds is annoying. There is no reason why it shouldn't be longer, as it takes NO performance from the main experience as much it takes away immersion"
I fully agree. As you know, there's another mod for this, which I gather you've assimilated into yours.
"Also No, you guessed wrong. it's not just a simple edit of the Willowengine ini files. Any edits made on the Willowengines will reset when you launch the game, since the main preset which the game is programmed to follow are in the archives."
Getting the changes to stick is as simple as setting willowengine and willowgame to read-only, or editing the baseengine and basegame configs. I've done it myself.
Overriding the willow/base configs with custom configs is probably what the mods you've amalgamated are doing.
Horrible place to have an discussion, but here goes:
"I'm sitting here with a RX 580 8 gig GPU, and an overclocked i7 CPU. I'm playing BL2. I'm telling you BL2 today, with the latest version on Steam, still runs like garbage on CPU handled PhysX Medium, and that's without your mod upping the ante. Nothing has changed. In fact, it got permanently worse after the pirate booty DLC made the particle system even more unoptimized and Gearbox has never bothered to fix it."
Just out of curiosity, what frames do you consider unplayable? 30-40-50? Like i stated before i run this game flawlessly, only boss fights and heavy battles dips me down to the 40s, and when free roaming and just shooting a few raiders im rocking 90fps mostly. unless the environment is taxing.
"BL2 is 32-bit, and single-threaded, taking no advantage of multi-cores or even hyper-threading. The PhysX in this game has to be at least partly offloaded to a GPU, or else it cripples the CPU, period"
32-bit and single-threaded is correct. PhysX is helped by the GPU on the Nvidia side, but only by a small amount. I looked this up, and amd users runs PhysX on the CPU only, at least that what i could find out, maybe that's why you have s*** frames.
"I fully agree. As you know, there's another mod for this, which I gather you've assimilated into yours."
Yeah but i tweaked it, so realism and limbs stay for longer and don't look "over the top"
First of all, it's a nice mod. But I have an issue. A weird message after executing the patch. So, it says: "Unrecognized class or object EngineResources.DefaultPhysXParSys". Any suggestions?
This is a weird bug that happens since there are a few lines of codes that does not want to be set as command. this is not an issue tho so don't worry about it. it wont break anything. mod still works regardless.
14 comments
Thank you for the wonderful mod, I've followed the install guide to best of my ability on mod manager page. The physx particles all stay for the alloted time which is way longer only thing is the more blood section particles and blood on the ground don't stay no matter which setting I apply there is extra blood but it disappears after a few seconds. I hope you can help me, please say if theres any information you need I'm just using the community patch and your mod.
The only way one can play with this much of the unoptimized Physx in BL2 and still get good frame-rate is if you have an nVIDIA GPU, preferably paired with another GPU.
Nothing you or anyone else can do with a mod can make this game run CPU Physx well, because the engine is single-threaded.
I'm guessing your mod is just some changed values in willowengine and willowgame? I know the exact lines and values for particle count and corpse time.
"Blood pools, limbs and alien blood splatter stay for 1 hour"
Dunno how you did this, though.
Safe to say that the CUDA engine in nvidia cards are helping, but not by a lot. Remember CUDA engines where meant to support the OLD EVGA Physics engine used way way back when physics became a thing in games. After EVGA physics failed and shut down they use CUDA ONLY for their new Flex and hair rendering. Mean while they have found other way (hence, HAVOK) to render basic physics on video and cpu memory. I don't get why you are so hostile against all this.
Either way, what you're saying is wrong, few years after the release of Borderlands 2, Nvidia has also been removing the CUDA lock on their cards, so AMD users can experience physX features on AMD CPU's, but only running strictly on the CPU. (this would ofc impact performance tho)
Then agian the engine is so old, that the only way physX was playable back them was if you had TOP tier hardware.
Now this is not a problem anymore. CPU's these days are powerful enough to handle the extra PhysX strain that this mod provides. Even if the game engine it's single-threaded.
You dont need a "nasa" meme pc to run it.
Also No, you guessed wrong. it's not just a simple edit of the Willowengine ini files.
Any edits made on the Willowengines will reset when you launch the game, since the main preset which the game is programmed to follow are in the archives.
And i don't know about you, but i can guarantee that other people, inc me finds it annoying that the static blood stain disappears after 10 seconds is annoying. There is no reason why it shouldn't be longer, as it takes NO performance from the main experience as much it takes away immersion.
"Either way, what you're saying is wrong, few years after the release of Borderlands 2, Nvidia has also been removing the CUDA lock on their cards, so AMD users can experience physX features on AMD CPU's, but only running strictly on the CPU."
I'm sitting here with a RX 580 8 gig GPU, and an overclocked i7 CPU. I'm playing BL2. I'm telling you BL2 today, with the latest version on Steam, still runs like garbage on CPU handled PhysX Medium, and that's without your mod upping the ante. Nothing has changed. In fact, it got permanently worse after the pirate booty DLC made the particle system even more unoptimized and Gearbox has never bothered to fix it.
BL2 is 32-bit, and single-threaded, taking no advantage of multi-cores or even hyper-threading. The PhysX in this game has to be at least partly offloaded to a GPU, or else it cripples the CPU, period
Modern CPUs are powerful because they have multiple physical cores. BL2 simply isn't coded to use them, and clock speed only takes you so far.
"annoying that the static blood stain disappears after 10 seconds is annoying. There is no reason why it shouldn't be longer, as it takes NO performance from the main experience as much it takes away immersion"
I fully agree. As you know, there's another mod for this, which I gather you've assimilated into yours.
"Also No, you guessed wrong. it's not just a simple edit of the Willowengine ini files.
Any edits made on the Willowengines will reset when you launch the game, since the main preset which the game is programmed to follow are in the archives."
Getting the changes to stick is as simple as setting willowengine and willowgame to read-only, or editing the baseengine and basegame configs. I've done it myself.
Overriding the willow/base configs with custom configs is probably what the mods you've amalgamated are doing.
"I'm sitting here with a RX 580 8 gig GPU, and an overclocked i7 CPU. I'm playing BL2. I'm telling you BL2 today, with the latest version on Steam, still runs like garbage on CPU handled PhysX Medium, and that's without your mod upping the ante. Nothing has changed. In fact, it got permanently worse after the pirate booty DLC made the particle system even more unoptimized and Gearbox has never bothered to fix it."
Just out of curiosity, what frames do you consider unplayable? 30-40-50?
Like i stated before i run this game flawlessly, only boss fights and heavy battles dips me down to the 40s, and when free roaming and just shooting a few raiders im rocking 90fps mostly. unless the environment is taxing.
"BL2 is 32-bit, and single-threaded, taking no advantage of multi-cores or even hyper-threading. The PhysX in this game has to be at least partly offloaded to a GPU, or else it cripples the CPU, period"
32-bit and single-threaded is correct. PhysX is helped by the GPU on the Nvidia side, but only by a small amount.
I looked this up, and amd users runs PhysX on the CPU only, at least that what i could find out, maybe that's why you have s*** frames.
"I fully agree. As you know, there's another mod for this, which I gather you've assimilated into yours."
Yeah but i tweaked it, so realism and limbs stay for longer and don't look "over the top"
So, it says: "Unrecognized class or object EngineResources.DefaultPhysXParSys".
Any suggestions?
This is a weird bug that happens since there are a few lines of codes that does not want to be set as command. this is not an issue tho so don't worry about it. it wont break anything. mod still works regardless.
But i have not experienced any bugs or crashes while using this mod.
I've tested this mod for around 11 hours worth of gameplay time.