I had a similar problem and I am certain it is not my loot profile causing this. I am fairly certain it is not actually a bug in vtank, but rather in decal itself (probably similar to the bug I had to work around for StuffExchanger, where Decal is not able to "keep up" with updating objects when GUIDs are reused by the server at a quick rate).

Thanks again lino!

Is it something that might be fixed with the rewrite of Decal?

I keep getting the red error "our pack is completely full" also, even with six or seven empty packs as well as the main being empty also.

Do you have the colo packs with the extra slots?


Also, VI, I have started getting an error in-game recently. When I log in and click start, I get red text that says vtank couldn't start because of a memory error or something similar. I'll copy/paste it next time I get it so you can see what's going on.


Edit - Forgot about the error log:


============================================================================

2/6/2011 10:36:39 AM

Error: Error HRESULT E_FAIL has been returned from a call to a COM component.

Source: Decal.Interop.Filters

Stack: at Decal.Interop.Filters.CharacterStatsClass.get_TotalXP_64()

at Decal.Adapter.Wrappers.CharacterFilter.get_TotalXP()

at VirindiReporter.PluginCore.statustimer_Tick(Object sender, EventArgs e)

at MyClasses.MyTimer.tim_Tick(Object sender, EventArgs e)

============================================================================


This always happens at log in. Never once the macro is up and running.

 

-----signature-----

Nope, just regular packs. It happened from time to time in the past, but recently it started happening much more often.

This is probably because your char has a Jester deck. Decal has an issue when you login with a cooldown timer still ticking down. When you use portal or ToD gems, wait for the cooldown to run out before you logout. If you use the Jester deck, you will have to wait quite a bit.

 

-----signature-----

Any ETA to a fix? All my chars use surge of destruction aetheria so this bug bites me quite a bit.

Hmm. I'll have to take a look in my packs. Only things I use with timers are portal gems and the health/armor aug gems. And the health/armor gems aren't in my list of usable items, so they never get clicked by vtank.


I'll keep a better look at what's going on and report back on this.

 

-----signature-----

Hi Virindi,

Thanks for the awesome plugin(s). I really appreciate the functionality that it adds to the game!

I have two requests:

1)
Shield mode

I'm using target by range, because I was having the same issue as joeblow8579, where I would target something slightly too far away to hit in a crowd. This issue is specifically regarding olthoi, and unarmed weapons, so it may not apply to all monsters or weapons, but I suspect it applies to many.

Olthoi being olthoi, they hop around alot. I'm finding myself dragged out of my corner and into the middle of a horde, and then finding that I'll heal with my back turned to 6 or so, resulting in me getting totally owned.

Since you're able to discern object boundaries and monster locations, would it be possible to keep the shield mode character prioritizing shield-towards-most-melee-attackers and back-against-the-wall over attacking, and perhaps cycle a target re-selection if the character attempts to move too far out of the corner/wall?

Scenario
Tunnel full of olthoi:
Character faces side with most oncoming olthoi (probably tunnel). If surrounded, tries to back against wall, if boundary_distance < wall_approach_range. Targets nearest target, while attempting to maintain maximum amount of monsters in the shield-protection-zone.

2)
Also, is it possible to set a mob priority, as in kill lowest HP mobs first?

Virindi, I turned on the mouse-turning setting and since have not been able to run a route. I attempted to set keys to default, but that did not solve the issue. It seems as though once my character hits a nav point, he stops moving. If you press forward or back, he'll restart until next nav. Any idea what may be causing this?

NVM, fix was turning off "Turn your character with camera turning" in Config>Input Options