flc problem
- Thread starter register
- Start date
ShiroKobbure
Still modding Civ3
It's hard to say, you could upload all directions and maybe someone can find the problem.
Otherwise, just manually paste the SW directions into the storyboard with Photoshop.
Otherwise, just manually paste the SW directions into the storyboard with Photoshop.
I will do that, I will paste each SW frame to storyboard in Photoshop but I don't believe it will fix the problem. In attachment you can find default storyboard and all frame directions. Is nothing wrong with them. I noticed that no matter what unit I will render I always can see this bug in SW direction in all six animations always after export to flc 
Balam-Agab
God King
It's definitely not a problem with the image files. I took what you posted an I made a flc without any problems. There could be a palette issue (post it and i'll take a look for you). The other issue could be with some program that you're using. What are you using to make the flc?
Oh great! I use Flicster 1.8
http://forums.civfanatics.com/showthread.php?t=10208.
Palette in attachement
http://forums.civfanatics.com/showthread.php?t=10208.
Palette in attachement
Balam-Agab
God King
Unfortunately, it's now doing the same thing for me, but i have found the problem. It has something to do with the dimensions of the flc. If you use a different sized bmps (I know that 150, 198 and 236 work as those are the sizes I use and i tried your unit with the second 2) it should work fine. You will either need to rerender the units or to batch process them with photoshop (or similar).
Finally I did it, I changed frame size to 236 and it's working. I would never find it myself 
All range of sizes 220, 222, 226, etc, 230, 233, etc, just don't work. The funny is that I used 220 before for other units and I had no problems what so ever. Ok, so I can continue Many thanks.
All range of sizes 220, 222, 226, etc, 230, 233, etc, just don't work. The funny is that I used 220 before for other units and I had no problems what so ever. Ok, so I can continue Many thanks.
register... I suspected the problem was the frame size coupled with particular aspects of the Unit such as the thin Spears jutting out.
Flicster has a problem with any part of a unit animation being closer than 3 pixels from the Right Frame. Tearing of the animation happens like your Spears throughout the frames.
The solution is to keep the animation at least 3 pixels away from the Right Frame. Animations can touch any other Frames with no problems.
I have not seen the problem as you experienced with larger Frames but then I have not used 220 x 220 frame size. It isn't just the Frame Sizes that cause the Tearing... it is also due to other details in the animation that for some reason are not addressed correctly within the spaces of the Frames.
240 x 240 works as well as many other sizes.
Civ3FlicEdit has the problem of removing the original 1st frame by duplicating the 2nd Frame and placing it on the 1st Frame. This causes animations to stammer and hesitate because they are missing the original 1st Frame as well as having the 1st and 2nd Frames the same. This is especially evident with Run animations where one can see the "Hiccup" and Hesitation in the Loop.
Civ3FlicEdit does this Only with New Units when Directly making a New Storyboard and FXM file with Civ3FlicEdit... It does not happen with existing Units where you open a Finished Flc then generate a Storyboard and FXM file from the Finished Flc. Civ3FlicEdit will keep the existing factors in the FXM file the same as the Finished Flc with no problems.
The Work Around for Civ3FlicEdit is to Open an existing Finished Flc that has the same Frame Size and Number of Frames as your New Unit and generate a New Storyboard and FXM file. Replace the Storyboard with your New Unit Storyboard... then generate the New Flc.
A Work Around for Flicster is to first make the New Flc even if it has Tears, then Open the Flc with Civ3FlicEdit and generate a new Storyboard and FXM file. Replace the Storyboard with your Original Storyboard, then generate the New Flc with Civ3FlicEdit.
This should work for the different sized Frames as well.
Another manual way to correct Tears in animations from Flicster is to place 2 or 3 Pixels wide of the lightest Shadow or Smoke shades in front of the areas where the tears occur.
These light shades are not evident and generally will not detract from the animation.
So if you want to use a 220 x 220 Frame size or other sizes, you could do so with the above technique using both Flicster and Civ3FlicEdit. The Two programs have their glitches, probably due to unforeseen programing errors, but if you know what they are, you can work around the problems as they occur.
Hope I have explained this where it is understandable
Flicster has a problem with any part of a unit animation being closer than 3 pixels from the Right Frame. Tearing of the animation happens like your Spears throughout the frames.
The solution is to keep the animation at least 3 pixels away from the Right Frame. Animations can touch any other Frames with no problems.
I have not seen the problem as you experienced with larger Frames but then I have not used 220 x 220 frame size. It isn't just the Frame Sizes that cause the Tearing... it is also due to other details in the animation that for some reason are not addressed correctly within the spaces of the Frames.
240 x 240 works as well as many other sizes.
Civ3FlicEdit has the problem of removing the original 1st frame by duplicating the 2nd Frame and placing it on the 1st Frame. This causes animations to stammer and hesitate because they are missing the original 1st Frame as well as having the 1st and 2nd Frames the same. This is especially evident with Run animations where one can see the "Hiccup" and Hesitation in the Loop.
Civ3FlicEdit does this Only with New Units when Directly making a New Storyboard and FXM file with Civ3FlicEdit... It does not happen with existing Units where you open a Finished Flc then generate a Storyboard and FXM file from the Finished Flc. Civ3FlicEdit will keep the existing factors in the FXM file the same as the Finished Flc with no problems.
The Work Around for Civ3FlicEdit is to Open an existing Finished Flc that has the same Frame Size and Number of Frames as your New Unit and generate a New Storyboard and FXM file. Replace the Storyboard with your New Unit Storyboard... then generate the New Flc.
A Work Around for Flicster is to first make the New Flc even if it has Tears, then Open the Flc with Civ3FlicEdit and generate a new Storyboard and FXM file. Replace the Storyboard with your Original Storyboard, then generate the New Flc with Civ3FlicEdit.
This should work for the different sized Frames as well.
Another manual way to correct Tears in animations from Flicster is to place 2 or 3 Pixels wide of the lightest Shadow or Smoke shades in front of the areas where the tears occur.
These light shades are not evident and generally will not detract from the animation.
So if you want to use a 220 x 220 Frame size or other sizes, you could do so with the above technique using both Flicster and Civ3FlicEdit. The Two programs have their glitches, probably due to unforeseen programing errors, but if you know what they are, you can work around the problems as they occur.
Hope I have explained this where it is understandable
