News:

MFG's Character of the Month: October 2026 Voting

Main Menu

Fighter Factory Development Thread

Started by VirtuallTek, September 04, 2010, 04:06:44 AM

Previous topic - Next topic

_Josue_

Quote from: VirtuallTek on March 31, 2011, 03:06:44 PM
Hello!

Some information
I'm not died  ;D, I'm currently finishing the Beta 4. Probably, the Beta 5 will be the last private release.  :twisted:

[]s
Wow, this is great!
Now I guess I have a little something to share about the old Fighter Factory Classic (the 5 years commemorative version)
Even though many bugs were fixed, I think there's still a little issue I noticed when I opened the same SFF file with both FFClassic commemorative and MCM (Mugen Char Maker) MUGEN char maker was correctly NOT displaying) transparency for sprites that didn't have shared palette, while those same sprites were erroneously showing transparency in FF Classic commemorative. Now, this happened to sprites that had the same BG color as the ones with shared palette, as if just having that color as BG color were enough. However both MUGEN and MCM showed those sprites with no transparency at all as the color was actually not set as color 0
The inverse effect is also present, sprites that have a BG color set as color 0 correctly display transparency in both MCM, however, as such sprites don't have shared palette, the BG color is shown.
I... I guess a screenshot would better show this:



I don't know whether this is fixed for FF 3.0 but I'm reporting just in case.

rednavi -RETIRED

FFClassic takes the color from slot 0 from the very first image on the sff as the transparent color, even in later images that dont share the same transparent color.

that's fixed in FFU.

_Josue_

#202
Quote from: Rednavi on April 01, 2011, 12:20:25 AM
FFClassic takes the color from slot 0 from the very first image on the sff as the transparent color, even in later images that dont share the same transparent color.

that's fixed in FFU.
Thank you. Man, I hope it's fixed for FF 3.0 too... wait, if Virtualtek has fixed it for FF ultimate why didn't he fix it for FF classic  commemorative since it was being released again with bugfixes?
Anyways, still waiting eagerly for FF 3.0

VirtuallTek

Quote from: Rajaa on March 31, 2011, 04:17:58 PM
You must have some really good beta testers! :ninja:
:suttrox:

Quote from: _Josue_ on April 01, 2011, 03:24:17 AM
Thank you. Man, I hope it's fixed for FF 3.0 too... wait, if Virtualtek has fixed it for FF ultimate why didn't he fix it for FF classic  commemorative since it was being released again with bugfixes?
Anyways, still waiting eagerly for FF 3.0
FF 3 doesn't have this problem.
About FFC, as I said on the FFC topic, the only bug fix I made was the accuracy of clsns. The development of the FFC isn't planned as FFU or FF3. Bug fixes in this version requires many changes in the code, which requires time. Currently, I occupy all my free time on FF3.

[]s

_Josue_

Quote from: VirtuallTek on April 01, 2011, 04:01:38 AM
Quote from: Rajaa on March 31, 2011, 04:17:58 PM
You must have some really good beta testers! :ninja:
:suttrox:

Quote from: _Josue_ on April 01, 2011, 03:24:17 AM
Thank you. Man, I hope it's fixed for FF 3.0 too... wait, if Virtualtek has fixed it for FF ultimate why didn't he fix it for FF classic  commemorative since it was being released again with bugfixes?
Anyways, still waiting eagerly for FF 3.0
FF 3 doesn't have this problem.
About FFC, as I said on the FFC topic, the only bug fix I made was the accuracy of clsns. The development of the FFC isn't planned as FFU or FF3. Bug fixes in this version requires many changes in the code, which requires time. Currently, I occupy all my free time on FF3.

[]s
Glad to know it,
So... FF3.0 correctly detects each sprite's color 0 as transparent...
any news from Elecbyte? They have left some bugs and I'm still waiting for those to be fixed...
I really want to use FF3.0... and MUGEN 1.1
Personally I haven't messed up with SFFv2 yet, so I wonder how easy  the transition will be...
Anyways, thank you VirtuallTek for all you have been doing... see ya and God bless you.

VirtuallTek

Quoteany news from Elecbyte?
No, I'm faster than Elecbyte  ;D FF3 will be released prior to Mugen 1.1, unfortunately.

The Beta 4 is out, with a lot of updates.

[]s

rednavi -RETIRED

Thank God, I cant wait to use SFFv2 for real.

O Ilusionista

Holy shit!

VT, I've received the beta 4, its simply amazing!
Loved the new features :)

Quote from: Rednavi on April 02, 2011, 10:57:01 PM
Thank God, I cant wait to use SFFv2 for real.

I use it to make SFFv2 files and its works perfectly. I can even add palettes to the sff (sffv2 format).
And VT added the suport to not only .act and .apl, but many other formats...even Mugen 1.1 palettes

_Josue_

Quote from: VirtuallTek on April 02, 2011, 10:19:40 PM
Quoteany news from Elecbyte?
No, I'm faster than Elecbyte  ;D FF3 will be released prior to Mugen 1.1, unfortunately.

The Beta 4 is out, with a lot of updates.

[]s
Good to hear it... lol  ;D
however....
*sigh* why is Elecbyte so delayed ?  --;
I mean... they could have began to release at least MUGEN 1.0.1 with some bugfixes... you know it's been almost three months with no words from them, nothing at their blog, as if they had... no, better not even think about it.  :-X
anyways, we hope for the best.

Cyanide

Confused about sffv2 through this, i can't find any info on how it's working here.

The palettes stuff on the side, kinda helps, but as it enforces the use of the currently displayed palette on whatever sprite you have displayed rather than using the native palette i'm back to confused.

I figure i'll make sffv2 manually and import it in to see how it works out.

Your export function is pretty unreadable due to lack of carriage returns in the text. Which doesn't help me make sense of it.

Would you mind a short explanation of the current remappal tool here? I would like to know how it works, and how it ties all the palettes together. Cos currently my unshared display as shared within sff manager but are of course normal in game.



In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.

VirtuallTek

#210
Quote from: Cyanide on April 03, 2011, 02:06:55 AM
Confused about sffv2 through this, i can't find any info on how it's working here.

The palettes stuff on the side, kinda helps, but as it enforces the use of the currently displayed palette on whatever sprite you have displayed rather than using the native palette i'm back to confused.

I figure i'll make sffv2 manually and import it in to see how it works out.

Your export function is pretty unreadable due to lack of carriage returns in the text. Which doesn't help me make sense of it.

Would you mind a short explanation of the current remappal tool here? I would like to know how it works, and how it ties all the palettes together. Cos currently my unshared display as shared within sff manager but are of course normal in game.

OK, for those who are familiar with sff v1, the operation is quite different.

About SFF v2:
- The images don't have your own palette like SFF v1, all palettes are shared.
- The images are stored in a certain encoding, not as PCX, like SFF v1.
- The palettes are separated from the images (you can see and edit all palettes of the SFF in the right panel).
- The sprite palette is defined by the palette index, not propagated by the "shared palette" option.
- When you open a SFF v1, FF3 convert it to SFF v2 (palettes separated from the sprites and shared (you lost the "native" palette forever).
- When you save a SFF in FF3, the format will be the same as the source.
- You can save a SFF v2 from a v1 using the Save as function.
- If you save a SFF v1, FF3 generate the "shared palette" option automatically based on the current editor state, and adjust the sprite order if needed (SFF v1 palette propagation is strict related to the sprite order).

About the remap function:
- with this function, you can redirect a certain palette group/indx to another (for view purposes)
- you can use it to simulate the Mugen 1.0 RemapPal state controller and see the changes in design-time.

I think this clarifies the matter.
About feedback, use PM.  ;)

EDIT: About the export, FF3 save it in Unix UTF-8. Notepad not recognize the Unix-style line break, but Wordpad, Notepad++, ... yes

[]s

O Ilusionista

Quote- If you save a SFF v1, FF3 generate the "shared palette" option automatically based on the current editor state, and adjust the sprite order if needed (SFF v1 palette propagation is strict related to the sprite order).

yeah, and that is great.

QuoteEDIT: About the export, FF3 save it in Unix UTF-8. Notepad not recognize the Unix-style line break, but Wordpad, Notepad++, ... yes

Yes, its a Notepad bug. If I use TextEditor on my Mac and save a txt file, Notepad can't read the carriage return.

_Josue_

#212
I have seen this in at Elecbyte's,
http://elecbyte.com/forum/index.php?topic=2975.0
and I thought it would be a nice idea. You know, if the "save all as PCX" button saved each image with a name that made it easier to know which sprite no it was and which group no it was. When I do it manually names are like this:
30000,3,18,16.pcx
group,Imageno,posX,posY.pcx
I think this would be particularly helpful when batch saving all sprites as images.
Anyways, Now that I remember this, FF3.0 will be able to transfer sprites from a SFF file to another isn't it?

VirtuallTek

Quote from: _Josue_ on April 17, 2011, 03:44:19 AM
I have seen this in at Elecbyte's,
http://elecbyte.com/forum/index.php?topic=2975.0
and I thought it would be a nice idea. You know, if the "save all as PCX" button saved each image with a name that made it easier to know which sprite no it was and which group no it was. When I do it manually names are like this:
30000,3,18,16.pcx
group,Imageno,posX,posY.pcx
I think this would be particularly helpful when batch saving all sprites as images.
FF3 currently uses: user specified name - group - index . extension (pcx, bmp, png)

QuoteAnyways, Now that I remember this, FF3.0 will be able to transfer sprites from a SFF file to another isn't it?
Yes, you can transfer sprites, sounds or animations. Already implemented.

In the next week, i will post the first screenshots.

[]s

MadkaT

Where can i pick the GNU/Linux version?
<- Foros Mugen en español. And also English forums.

VirtuallTek

#215
Quote from: MadkaT on April 17, 2011, 09:52:16 PM
Where can i pick the GNU/Linux version?
Will be released at the same time as the Windows version.

EDIT: FF3 on Linux is 3-10 times faster than in Windows.

[]s

sal-azul

Quote from: VirtuallTek on April 18, 2011, 12:39:33 AM

EDIT: FF3 on Linux is 3-10 times faster than in Windows.

[]s
:ninja: :ninja: :ninja: :ninja:
Now THAT gives me an excuse to use linux on my laptop. :D
*now I have to wait for mugen 1.2 linux version* --;




Quote from: TempesT
I just got back from having really hot and raw sex with sal and seph, oh my gosh they violated my body many times, IT WAS GREAT!!!!! They have many big dick and used to have sex with my sex holes! Also my armpits are strictly OFF LIMITS especially to foreign weiners.
>:)

Henry Hero

Quote from: VirtuallTek on April 18, 2011, 12:39:33 AM
EDIT: FF3 on Linux is 3-10 times faster than in Windows.

Is this true to FFU?

Could you explain that to us?

Recently I got a MUCH BETTER pc than I had, and it uses windows 7 while my old one used XP, and now FFU is much slower than before, it's kinda frustrating really, I can't see the animations properly, they're 10 times slower than normal mugen, so I end up making them way too fast when testing them on the air editor.

Lasombra Demon

Quote from: sal-azul on April 18, 2011, 06:47:47 AM
*now I have to wait for mugen 1.2 linux version* --;
WINE runs every MUGEN ver perfectly. :)
For downloads and questions, go to IKEMEÑ:  https://discord.gg/rweS5ZUek3

For donations go to https://ko-fi.com/lasombrademon

_Josue_

Quote from: VirtuallTek on April 17, 2011, 09:06:29 PM
FF3 currently uses: user specified name - group - index . extension (pcx, bmp, png)
Yes, you can transfer sprites, sounds or animations. Already implemented.
In the next week, i will post the first screenshots.
[]s
Thank you! I'm so impatient to use MUGEN 1.1 and FF3.0  ;D
Oh, by the way, I also noticed this: It is possible to use the same .def file for your character and for your introduction or ending cutscene, MUGEN allows it with no complaint nor warning. However FF Classic just can't open a def file that is used for both introduction and char or ending and char definitions.
(you know, some chars like N-Mario's have dual sized scales, which means they can be used at both their original small chibi size and a normal 2x scaled size, which gives 2 def files one for small size and one for 2x scaled normal size.)
Now I have added introduction and ending cutscenes so for example the normal sized def contains the intro and the small sized one contains the ending, both linking each other. MUGEN 1.0 and WinMUGEN supported this trick, however FF classic just can't open the chars, it says:
cannot find the file, "whatever.SFF"
I must comment out this lines to open it:
;[SceneDef]
;[Info]
If you want a sample char, you can download my modded version of N-Mario's Omega Zero at my website (the link is at my signature)
Now I don't know if I would prefer to keep it like that (so only people with sufficient knowledge can open the char with FF)
However I wanted VirtuallTek to know it.