Token Death Indicator 2.0 - BLOOD SPLATS!

[Gwydion]

And what did those errors say?

Just finished a session and one of the players sent me an email with the error. He sent in email, but here is a recreation:

Runtime Error: D3DXCreateTexture failed - [4294967276] - D3DUSAGE_RENDERTARGET - D3DPOOL_DEFAULT - D3DERR_OUTOFVID

It didn't happen every time. It seemed like with new encounters it would work for a couple of deaths and then throw errors again.

[LordEntrails]

Used it today with no errors. Players loved it and quickly noticed the 'fallen as if dead' label. Would love it if there was an option to leave the blood splat behind when the NPC is removed from the CT though. Would map the map nice and bloody!

[Trenloe]

Just finished a session and one of the players sent me an email with the error. He sent in email, but here is a recreation:

Runtime Error: D3DXCreateTexture failed - [4294967276] - D3DUSAGE_RENDERTARGET - D3DPOOL_DEFAULT - D3DERR_OUTOFVID

It didn't happen every time. It seemed like with new encounters it would work for a couple of deaths and then throw errors again.

These are Direct3D video errors. Is that last D3DERR_OUTOFVID truncated? I'm guessing it is actually D3DERR_OUTOFVIDEOMEMORY.

Info on these errors here: https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

It's more than likely that the video card on the computer doesn't have much memory available - either the player is running a very large screen/app resolution or their graphics card just doesn't have much memory available to start with.

[Gwydion]

[U]
These are Direct3D video errors. Is that last D3DERR_OUTOFVID truncated? I'm guessing it is actually D3DERR_OUTOFVIDEOMEMORY.

Info on these errors here: https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx

It's more than likely that the video card on the computer doesn't have much memory available - either the player is running a very large screen/app resolution or their graphics card just doesn't have much memory available to start with.

Ok. Cool. I'll have to see if the error is truncated. So, not necessarily on my end as the DM, but rather theirs, right?

[Trenloe]

So, not necessarily on my end as the DM, but rather theirs, right?

Absolutely.

[Vishera]

Glad it worked out. I've been playing with it and haven't experienced any errors. As far as leaving them behind, I'm not sure how that would work. I know there is an extension for SW that does it, but this script isn't equipped with that. If someone figures that out, I'd love them forever

[Full Bleed]

It's more than likely that the video card on the computer doesn't have much memory available - either the player is running a very large screen/app resolution or their graphics card just doesn't have much memory available to start with.

I'd be more inclined to be looking at:

1) How this particular asset is being rendered in FG (in particular, how it's being buffered differently that other assets) or
2) Driver update.

The memory usage of this tiny overlay is not likely to be the straw that breaks this particular camel's back. If it was just your run-of-the-mill "out of memory" error, it would be far more likely to happen with a larger asset and more likely to happen more often in other situations (because this would be indicative of the user skating on a pretty thin line). And, remember, were talking about *multiple* users from this group.

[Moon Wizard]

I don't think this is specifically an out of memory condition caused by the desired logic of the extension. My guess is either that the system having the problems is on the edge anyway due to token/map/module sharing, or that the extension has an endless loop condition creating death indicators until it errors out. I haven't looked at the extension specifically, so just brainstorming as places to check.

Regards,
JPG

[LordEntrails]

... that the extension has an endless loop condition creating death indicators until it errors out....

Those dang kobolds just won't stop bleeding! You can't imagine how many quarts of blood one of those little things has in it!!

[Gwydion]

I don't think this is specifically an out of memory condition caused by the desired logic of the extension. My guess is either that the system having the problems is on the edge anyway due to token/map/module sharing, or that the extension has an endless loop condition creating death indicators until it errors out. I haven't looked at the extension specifically, so just brainstorming as places to check.

Regards,
JPG

I'm wondering if it is the endless loop condition. I say that for a few reasons. My Saturday night game was a one-shot. Brand new campaign and although I shared a few maps with the players, none of them were crazy large. I also didn't share much of any tokens with them, I normally don't. The blood spatter worked fine early in the session. It wasn't until later until some (I don't think all) began having issues. On my Sunday game, everyone did have issues and, although they all have high-powered machines with strong graphics card, it COULD be related to the fact that we are getting farther into POTA and I have a lot of maps shared. I might unshare some of the earlier maps in the campaign to see if that has an impact. We will see! Oh, and interestingly, in the POTA game it felt like for each new encounter there would be no errors to start and then mid-way through the encounter the errors would start. Someone in my stream speculated that it happened when the "dying" npc had an effect on them (ie. hunters mark applied to them), but I can't confirm that is the case...