vbraun
Raytracing
Was I suppose to run the InstallFlcEdit.exe first? Eggh looks like it. Do you know where I can download the MFC42.DLL? I seem to be missing it.
Yes, you should - under Win OS the InstallFlcEdit.exe file runs automatically by installation.vbraun said:Was I suppose to run the InstallFlcEdit.exe first? Eggh looks like it. Do you know where I can download the MFC42.DLL? I seem to be missing it.
Bjornlo, I have got from you an e-mail with attached files. When I have opened Me262Attack.flc I can see wrong pixels. But also I have found a Me262Attack.c3f storyboard and when I have opened it all working fine. After I have export C3F to FLC - new FLC has not contains wrong pixels. Then I have made one more test - new FLC convert to C3F and then again to FLC. All working fine, so I don't know where are the wrong pixels from...Bjornlo said:This bug sure does seem to be in Civ3FlcEdit. Since to create the PCX, I took a FLC I made with flicster and exported the storyboard/pcx.
The bug did not exist before in the FLC. For fun, I also pulled the PCX out with flicster and replaced the pcx Civ3FlcEdit generated. The display bug was still there in Civ3FlcEdit but not in flicster. I examined the PCX file quite closely with photoshop to see if all the pixels had the exact same value and they did.
The bug in the picture was more visible then most of the other occurances, where it was around 1/4 as many pixels. The flc in question is Me262Attack.flc from the me262 in my signature.
So, I can duplicate the bug with Civ3FlcEdit using either the PCX file it or flicster generates. I can not duplicate this bug with flicster, nor can I find any annomoly in the image files. It is fairly easy to check. Select the magic wand, set the tolerance to zero, and check if any stray pixels show up when you click on the background color.
Since this issue does not seem to show up in the final FLC, it is not a HUGE bug, as far as I am concerned. But it would be nice to see what is in the pcx without wondering if it is a render bug.
This problem can be easyly solved. Point is that different FLC files have different structure. So not all export settings are acceptable for all FLC files.Another more interesting bug is that the resize option sometimes works perfectly (80%) and sometimes destroys the image (20%). I was playing around with a couple of planes that were the wrong scale. 4 resized correctly, one went invisible and the shadow went red. Curious I tried 5 more (some of which were the correct size, some not, since that part did not matter to my experiment). Again 4 went perfectly, the 5th lost 20-50% of the pixels which became invisible.
Puzzling.
Sorry, but attached ZIP file is not contain any storyboard - just a palette file and empty PCX file (zero length)...vbraun said:Here you go:
I'm pretty sure nothings wrong with the storyboard.
I may be that its a pcx and I'm trying to add a pallete. If that is the case just change the pcx to a bmp and try it.
I'm glad that it's work for you now.vbraun said:Thats weird. Anyway I got it to work. But I'll get you the .c3f file that had the problem.
It's a good idea. Maybe I'll make it (unfortunately, I have not free time now).One thing I would like to see added is the ability to change the amount of frames of a exsisting .c3f file.