How to reproduce bug:
Next buttonProstateX-0045Series left sidebar, drag the last one KTrans series and drop it into the viewportLooks like this is some issue with the data or with dcm4chee independent of the viewer. There's a 500 error in the dev console that also happens if I try curl directly.
$ curl "https://server.dcmjs.org/dcm4chee-arc/aets/DCM4CHEE/rs/studies/1.3.6.1.4.1.14519.5.2.1.7311.5101.186668715538412577190244617089/series/1.2.276.0.7230010.3.1.3.296485376.7.1528997923.638123/instances/1.2.276.0.7230010.3.1.4.296485376.7.1528997923.638124/frames/1"
<html><head><title>Error</title></head><body>Internal Server Error</body></html>
Looks like this is some issue with the data or with dcm4chee independent of the viewer. There's a 500 error in the dev console that also happens if I try curl directly.
$ curl "https://server.dcmjs.org/dcm4chee-arc/aets/DCM4CHEE/rs/studies/1.3.6.1.4.1.14519.5.2.1.7311.5101.186668715538412577190244617089/series/1.2.276.0.7230010.3.1.3.296485376.7.1528997923.638123/instances/1.2.276.0.7230010.3.1.4.296485376.7.1528997923.638124/frames/1" <html><head><title>Error</title></head><body>Internal Server Error</body></html>
Interesting, it opens successfully on OHIF V1 using an orthanc server.
I'll try using a local orthanc server and see if it opens with OHIF V2.
I downloaded the file by visiting this URL:
Then dropped it in to our new local viewer at:
And saw this error in the console:

Marking as a bug as we're likely the only people that can address the server issue.
Update: I just used a local orthanc server and it still wouldn't display on v2 whereas it displays successfully on v1 using the same server
What's really odd however, is when I drag and drop the actual KTrans.dcm file to the new local viewer, it displays successfully (scrolling doesn't work though)
Not sure what that means
IIRC, that series was created by Alireza using some of of the tools from dcmqi since the originals were in some other format. Maybe you can review how they were created and make new versions. (It would be good to have the process documented somewhere in any case)
I can confirm that the file looks like valid dicom but is missing the required metaheader.
One thing we might want to check is multiframe files with the local viewer. I didn't test it and so it might require some tweaks.
I'm going to close this for now. If more information can be provided so we can create actionable items, I'm more than happy to re-open this or create related new issues w/ scope.
It turns out it was indeed an issue with the DICOM data and not OHIF. No actionable items needed.
I'm going to close this for now. If more information can be provided so we can create actionable items, I'm more than happy to re-open this or create related new issues w/ scope.
@FitterX, please create a new issue instead of commenting on old, unrelated closed issues.