Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Plugin fail to open Hdr Cubemaps #14

Open
JSeb-92 opened this issue Jul 15, 2016 · 1 comment
Open

Plugin fail to open Hdr Cubemaps #14

JSeb-92 opened this issue Jul 15, 2016 · 1 comment

Comments

@JSeb-92
Copy link

JSeb-92 commented Jul 15, 2016

Hello,

I've started looking into your dds photoshop plugin, and it looks to be great: open source, handling recent compression formats (things that some other dds photoshop plugin doesn't have).

The only drawback IMHO is the limitation to Intel CPU platform, but I'm not sure if it can't run on non-Intel CPUs, maybe it can ?

I post an issue here for a DDS file open bug:

I get "Could not place the document 'filename.dds' because of a program error" from photoshop when I try to open DDS uncompressed Hdr cubemaps (both R16G16B16A16F and R11G11B10F formats fail).
DDS file open works for 2D Hdr (at least R16G16B16A16F).
DDS file open works for Cube SDR (at least BC3_UNORM).

I'll try to debug your lastest plugin code (I was hitting other issues to retrieve last ISPC with sourceforge being down)

Thanks

@JSeb-92
Copy link
Author

JSeb-92 commented Jul 15, 2016

I debug the issue but it's not trivial as I thought first: dds loading looks to work until the end (IntelPlugin::DoReadFinish()).
But there are memory access violations just after in photoshop callstack:
First-chance exception at 0x00007FF805311F28 in Photoshop.exe: Microsoft C++ exception: photoshop_error at memory location 0x000000000014F5E8.
First-chance exception at 0x00007FF805311F28 in Photoshop.exe: Microsoft C++ exception: photoshop_error at memory location 0x000000000014F5E8.
First-chance exception at 0x00007FF805311F28 in Photoshop.exe: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
First-chance exception at 0x00007FF805311F28 in Photoshop.exe: Microsoft C++ exception: [rethrow] at memory location 0x0000000000000000.
It looks like some of datas given to photoshop by the plugin are wrong, but I don't know what.

Then I don't know how to solve this issue, could you plan to do so ?

Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant