Crash when taking screenshots since the last patch

[Coolit]

I just wondered if anyone else was having issues when taking a screenshot since the last patch?

I have SM3.0 with MSAA enabled and an ati card running the latest drivers. When I hit the print screen key I get a crash then the following error:-

 

Pretty sure its a bug as it was working fine pre-patch so reported it ingame also. 

[TSR-JoshuaM]

I've tested and confirmed that this is indeed the case.  I will report it immediately.  This is not an issue on your system.  I will update you when I have more information regarding a fix for this.  To help us, and yourself, with issue tracking, I highly recommend opening a support ticket and referencing this issue and even this entire thread.  PM me the incident number when you have done so.

[Coolit]

I've opened a ticket and sent you the reference number 

[Rothgar]

We have this problem fixed.  It'll go out with the next hotfix.

[Coolit]

Great thanks

[TSR-JoshuaM]

Great news, thanks Rothgar!!

[Lasai]

oh, thanks.. I reported this in the other performance forum.  Ill edit with a link in case other people go there

However.. I had no problems taking screenshots on 6/25.  Today, after the 6/29 patch I do.. same message as the OP.

[Voel]

Having this same exact issue as of today.  Methinks the hotfix didn't exactly fix it?

[TSR-JoshuaM]

I'll double check and verify.  

[serenader]

I can confirm this as well, at first it was just when msaa was enabled with 3.0 I had thought, so I turned it off, now it does on or off

[TSR-JoshuaM]

I've reproduced it and reporting it.  The fix for it may not have been included but I don't have that information in front of me.

[Lasai]

Thank you.  And thank you all for plugging away for so many years on little snarly issues like this.

Seems like you guys have been at this forever, responsive and willing to look at issues and try to get them fixed.

Also.. always communicating.

Huge Props.

[TSR-JoshuaM]

For me personally, I play the game probably just as much as anyone here (when not working!) and always want to give the same level of support I would expect as a customer when I ran in to issues before I started here.

[Oink]

I'm now getting crashes taking screenshots as well

SOEBuild 7798L

DirectX9RenderDevice.cpp (17746)

D3DERR_INVALIDCALL 00c7bade

No shader 3, no anti-aliasing enabled, nvidia drivers 270.61.

[LokaJim]

I have the same issue using Windows 7 computers. All machines are using different kinds of ATI/AMD graphic cards. Seems on Vista this does not apply, as we are able to take screenshots there. Also there is a Geforce card doing the service. I remember having installed the latest Service Pack for Win 7 recently, but I am not sure, if it is related to this. Hope this info can be helfpul. Cheers, Jim

[serenader]

Using win xp pro 64 so it cant be a win 7 issue, but using an 4870 ati card

[Troubor]

serenader wrote:

Using win xp pro 64 so it cant be a win 7 issue, but using an 4870 ati card

I don't know if ATI is the issue.  I have Win 7, but I'm using 2xNvidia cards in SLI (yes, I know SLI doesn't do much for this game, but I do play other things too.    ).

[Voel]

Running WinXP and Nvidia GeForce 9800GTX+ ...not that I blame either of these things because I never had this issue before.

[TSR-JoshuaM]

Just got back from Fan Faire, I will double check on where this issue is.  It was reported prior to 6/30 and we did have a developer, Rothgar, acknowledge the issue on this thread.

[Oink]

Still crashing for me after 7/12 update.

[Louis_M]

Everquest II has detected an unrecoverable error and mustshutdown    e:liveeq2frameworkcoredevicesdirectx9renderdevice. cpp(17746):    Directx error (d3derr_invalidcall)00c7c00e

been getting that error when trying to take a screenshot today mostly of my realy disfigured dark elf character so i could add it into a petetion to see why she looks wrong ie hair is misplaced when i wear i certin robe you can see things you shouldn't be able to see if you get my drift

[Chalmo]

As a tip to fellow denizens out there, this error only ever happens to me when playing in windowed mode.

If I jump into full screen, I can capture screen shots normally. Going back into windowed mode I will not crash when trying to subsequently take a screenshot, but will crash when zoning for the next time.

Windows screenshot will work regularly in windowed mode if you disable the key from EQ2. So if you're really desperate, as a temporary work-around you can take a screenie, alt-tab to another window and paste the picture there. I actually did this during raid yesterday for some detrimentals but obviously it was not pleasant nor efficient.

Disabling Windows screenshot capability with an external program (http://www.itknowledge24.com/PrtScrn.zip) will not prevent it from crashing. It occurs with Shaders 3.0 on and off.

[Troubor]

Posting to add that as of 8AM Pacific time, July 13th I still have this issue.  For me this happened in full screen or windowed mode.  I'm using Shader 1.0, I haven't even tried 3.0.

I am using the streaming client.  If there is a way to go to the "standard" launcher/client without a full reinstall I'd not mind doing that, both in general and to see if this issue exists using the standard client.

[Thor]

Rothgar wrote:

We have this problem fixed.  It'll go out with the next hotfix.

A hotfix was in last Tuesday and Wednesday and this problem still persist.

[Voel]

Troubor wrote:

Posting to add that as of 8AM Pacific time, July 13th I still have this issue.  For me this happened in full screen or windowed mode.  I'm using Shader 1.0, I haven't even tried 3.0.

I am using the streaming client.  If there is a way to go to the "standard" launcher/client without a full reinstall I'd not mind doing that, both in general and to see if this issue exists using the standard client.

I use the "standard" EQ2 launcher and still had the problem.  But I guess the patch today finally addressed it because I just took some captures in windowed and fullscreen mode and no problems.  O/

[Troubor]

Voel@Unrest wrote:

Troubor wrote:

Posting to add that as of 8AM Pacific time, July 13th I still have this issue.  For me this happened in full screen or windowed mode.  I'm using Shader 1.0, I haven't even tried 3.0.

I am using the streaming client.  If there is a way to go to the "standard" launcher/client without a full reinstall I'd not mind doing that, both in general and to see if this issue exists using the standard client.

I use the "standard" EQ2 launcher and still had the problem.  But I guess the patch today finally addressed it because I just took some captures in windowed and fullscreen mode and no problems.  O/

I'm going ahead and doing a full reinstall so I can swap to the standard launcher.  I decided that even if there is a way to swap the launcher without reinstalling everything else, maybe a fresh one will somehow help.

Anyway, when it's finally done and I have my characters set back up, I'll try a screenshot.  I'll do a second post with the results either way based on that.

[Troubor]

Rewording this so it (hopefully) reads a bit better and hopefully is a bit more clear.

I went ahead and did a reinstall, this time using the "standard" client, not the streaming one, since I've been wanting to switch to that anyway.

After fiddling with settings and so forth, I tried a screenshot.

The screenshot worked, but when I went to an alt I crashed the very second the alt came up.  The error is identical to the one the OP has, which is what I was getting when I do a screenshot.

After that crash, any time I went to a character, I'd have him barely come on, then crash.  Again I'd get the Op's error.

Otherwise, it wasn't even letting me play, my character would be up for less then a second then I'd crash.

I rebooted, still the same thing.

I finally started removing random files from the Everquest 2 folder, letting the launcher repatch itself.  After doing this a bit, everything went back to normal and I can play again.

Screenshots went back to being "bugged".  If I try to do one, I crash as described by the OP.  The game isn't otherwise corrupted though, I can log back on and play.

Anyway, it appears that as of very early morning July 14th this is still bugged.  Either I corrupt my files to where I have to delete things and make the game reinstall/repatch, or I get the "normal" screenshot bug as described by the OP of this thread.

[TSR-JoshuaM]

It's still crashing for me too and I have not abandoned this.  I'll post more info if and when it comes my way but I know a fix is already out for it, it's just a matter of getting in it to the patch.  That's an entire process I have nothing to do with unfortunately.

[Oink]

Still crashing after Jul 19th update.

[TSR-JoshuaM]

I'll reproduce and re-report.  THanks for the update.