What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Trinity 1.7.1.12

Status
Not open for further replies.
deleted
"solved" below :) until further notice
 
Last edited:
heads up,
[15:48:02.156 N] [226E0130] GizmoType: Barricade Name: Barricade_Doube_Breakable_Snow_A-90721 ActorSNO: 195108 Distance: 13.31783 Position: <3265.059, 2759.047, 0> Barracade: True Radius: 16.05383
[15:48:02.156 N] [226D1790] Type: ClientEffect Name: Barricade_Doube_Breakable_Snow_A_B-90722 ActorSNO: 205748, Distance: 13.31783

can't destroy even when 195108 is in dictionary

Maybe your trinity destructable range is set at 12 or so, mind the log the range of the baricade is 13, so range must be more than that in order to destroy it.
 
yup my bad, thought it was just destructables range issue, that is until i encountered the same barricades.
 
Trinity 1.7.1.11 Posted

IF you have performance problems and are still using 1.6.3.4 because of performance problems, I invite you to use this version. If you still have performance problems, please do the following:


  • Set your DB log level to Normal or higher so debug logging doesn't slow down the DB log window
  • With "Use NavMesh to prevent stucks" ENABLED:
  • Go to Trinity config > Advanced > Enable Debug Performance, Debug Cache
  • Reproduce the performance problem and attach your log as a zip to this thread.
  • Next, try the same thing with "Use NavMesh to prevent stucks" option DISABLED.

Improving performance and reliability in Trinity is my top priority.

Changelog 1.7.1.11:

  • New GUI option: "Use NavMesh to prevent stucks" on the Combat>Misc tab. Default and recommendation is to enable this option. Disabling this may lead to stucks for bot attempting to target monsters/shines through walls and floor gaps. If you experience severe performance problems, try disabling this option.
  • Barbarian Weapon Throw can now be used as "primary" if no other primary ability is present.
  • Reduced barbarian bash destructable attack range.
  • Changed Targetable/Invulnerable/Burrowed/NPC checks (should be faster now)
  • Profile toggle targetting / toggle loot tags now work as expected
  • TrinityLogs moved to Demonbuddy directory.
  • Added more performance logging.
 
Im using 1.6.3.4 (with darkfiend loot added myself). I will check your version (1.7.1.11) and will report about performance comparision.
 
Bug with trinity .11;

Barb is still swinging at destructible objects from too far away. This occurs with any primary skill (Bash/Cleave/Frenzy). I set the destructible object range to the minimum, but this also does not help fix the problem.
 
trinity does not check Z coordinate?
same things happen at skycrown and stonefort, since .10
 

Attachments

  • Screenshot008.webp
    Screenshot008.webp
    283.2 KB · Views: 299
Bug with trinity .11;

Barb is still swinging at destructible objects from too far away. This occurs with any primary skill (Bash/Cleave/Frenzy). I set the destructible object range to the minimum, but this also does not help fix the problem.

same here,and the unstucker looks like not working properly
 
great job , but most important thing is "Performance problems still being investigated." still i got lags and frezzes because of trinity :<
 
this had become a slight problem in the last few updates but it seems to be getting worse. my wizard ignores a lot of mobs and will just keep running. She will almost run right through packs of mobs and not attack them until a few feet past them. any way to fix this?
 
this had become a slight problem in the last few updates but it seems to be getting worse. my wizard ignores a lot of mobs and will just keep running. She will almost run right through packs of mobs and not attack them until a few feet past them. any way to fix this?

I noticed this as well, also it seems the unstucker has stopped working.
 
I noticed this as well, also it seems the unstucker has stopped working.

unstucker, allowing game restart for long stucks and gold inactivity too. Got stuck in a3 for few hours when i was sleeping;/ with every option ON ;/
 
Did you guys use YAR with Trinity? Recent replies shows that the ver 0.1.9.2 of YAR is causing memory leaks and high CPU usage.
 
Bug with trinity .11;

Barb is still swinging at destructible objects from too far away. This occurs with any primary skill (Bash/Cleave/Frenzy). I set the destructible object range to the minimum, but this also does not help fix the problem.

Can you take a screenshot and get me the ActorSNO of these destructable objects? At least a screenshot.
 
great job , but most important thing is "Performance problems still being investigated." still i got lags and frezzes because of trinity :<

If you still have performance problems, please do the following:


  • Set your DB log level to Normal or higher so debug logging doesn't slow down the DB log window
  • With "Use NavMesh to prevent stucks" ENABLED:
  • Go to Trinity config > Advanced > Enable Debug Performance, Debug Cache
  • Reproduce the performance problem and attach your log as a zip to this thread.
  • Next, try the same thing with "Use NavMesh to prevent stucks" option DISABLED.
 
Status
Not open for further replies.
Back
Top