Images turning all RED after publishing....what happened?

[travlr588]

Every so often when I publish a course (to both .swf and .pdf) some of the images (both .png and .jpg I think) will change to nothing but a RED fill.  I haven't been able to discern a pattern of when this happens....and it won't always happen even to the same images (first publish I have red, turn around and immediately re-publish and it's fine).

Anyone have any idea about why this is happening and whether or not there's anything I can do about it?

Thanks

Jay

[Captiv8r]

Hi there

I'm not sure if this still holds true or not but years ago there would be Captivate projects that would experience what I called "the red screen of death". Basically what would happen back then is that Captivate would allocate computer memory and not release it when a project completed playing, Eventually the user would begin to see red squares followed shortly thereafter by the whole screen turning red. This happened when all available computer memory had been consumed.

One thought I had was to check your images. Are you inserting them, then having to scale them down substantially to "fit" the project? If so, note that this means substantially large images. For example, you may insert an image that would be perhaps several megs in size. But if you took the same image and scaled it before inserting into Captivate, it might be substantially smaller.

My own recommendation would be to pre-scale the image to the size you need before even inserting. This should cause your project to consume much less space (and need much less working memory when played).

Cheers... Rick

[travlr588]

Thanks for the info.

I've made it a practice to use Photoshop to drop the resolution of my images down to 72dpi and then "publish for web" if I need any transparency.  I replied to another post on here....I'm pushing my PC to it's breaking point, so maybe the memory has something to do with it.  We're supposed to be getting some highspeed replacements soon...I'm counting the days.

Jay

[TinkerTrainer]

We've seen that here, as well, but it seemed to be confined to Captivate versions 5.5 and 6.  Since we moved to v7 that problem has stopped.

We never did figure it out, either.  We both use 16GB machines so it probably wasn't a lack of memory - but who knows?

[travlr588]

TinkerTrainer

Thanks for the reply....I'm having the problem with v7.  That being said, I'm pushing the machine I'm developing on to the limit.  I had a feeling that that might have something to do with it.

TinkerTrainer.....would that refer to the 552d?

//signed//

ex-TRS / ISST

[TinkerTrainer]

Aha!  Close. Not the 552nd - the 38th on the Hill.