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

Cybaster

Fighter Factory is NOT compatible with 1.0 as of now. Any 1.0 trigger or controller will not be read by FF, that's the purpose of this update : to make it 1.0 compatible with all features.

ExShadow

Sorry for the necrobump.

I don't know if anythings been mentioned about this already, but I would like to suggest batch 256 color conversion to be implemented in the new version of Fighter Factory.

Jesuszilla

Quote from: ξ Bastard on October 31, 2010, 11:12:43 AM
Fighter Factory is NOT compatible with 1.0 as of now. Any 1.0 trigger or controller will not be read by FF, that's the purpose of this update : to make it 1.0 compatible with all features.
Hopefully 1.1... But I dunno if VirtuallTek knows that 1.1 SFFs can do things 1.0 SFFs can't, such as 24 and 32-bit PNGs. Something I'm working on happens to use this.

Cyanide

Brought that up on the beta forum some time back. The use of 32bit and 8bit should be provided within the sffv2 standard so it shouldn't be too much of an issue having them both displayed.


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

Quote from: ♥Shizuku♥ on November 16, 2010, 07:45:49 PM
Sorry for the necrobump.

I don't know if anythings been mentioned about this already, but I would like to suggest batch 256 color conversion to be implemented in the new version of Fighter Factory.
If I understood correctly, FFU has this. Use the "Insert Palette in images" function. It only works perfectly on FFU 2.6.

Quote from: Jesuszilla on November 17, 2010, 03:42:02 AM
Quote from: ξ Bastard on October 31, 2010, 11:12:43 AM
Fighter Factory is NOT compatible with 1.0 as of now. Any 1.0 trigger or controller will not be read by FF, that's the purpose of this update : to make it 1.0 compatible with all features.
Hopefully 1.1... But I dunno if VirtuallTek knows that 1.1 SFFs can do things 1.0 SFFs can't, such as 24 and 32-bit PNGs. Something I'm working on happens to use this.
Yes, I know. FF3 supports 5, 8, 24 and 32 bits. But I don't have any specific information about 1.1 format (eg. internal loader version counter).

Quote from: Cyanide on November 17, 2010, 03:45:30 AM
Brought that up on the beta forum some time back. The use of 32bit and 8bit should be provided within the sffv2 standard so it shouldn't be too much of an issue having them both displayed.
:sugoi:

[]s

Darkest Shade of Light

Hopefully I won't get in trouble for a late BUMP. As this is, like, a month and a half empty, but did I miss a release date here? Or is this just a teaser type of thing right now, 'cause I seriously wanna use this!
MUGEN creation at Darkest Productions.
Lead by: Darkest Shade of Light
           /^\ (That be a secret smiley)
Co-Lead by: Nobody atm... :(
Productions: Being loaded onto a website I'm TRYING to figure out how to make....

Cyanide

It's still in wips and he's stated pretty clearly it'll be released in 2011. As we've only had 2 DAYS of 2011 and it's not in the first page of releases you can be pretty sure it's not out yet can't you.

I'm still hoping for a few screenshots of it. Palettes, sffv2 and the .def screen mainly (i would like to see if i have to rant for a bit if the .def is still that checkbox rubbish)


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.

tunglashor

Quote from: VirtuallTek on November 25, 2010, 03:49:06 PM
Yes, I know. FF3 supports 5, 8, 24 and 32 bits. But I don't have any specific information about 1.1 format (eg. internal loader version counter).
I've added support for the new 1.1 formats to one of my tools, so can provide details if you still need them :tipshat:

Jesuszilla

#148
If ya need an SFF that makes use of that for testing purposes, I'll send that over as well. Because ZCharCad 9 could NOT open up the SFF file in question.

montyoum

I would only ask that the keyboard shortcuts get somewhat simpler. I.E. most of the shortcuts that are ctrl+shift+... could just be ctrl+...

And that there be more of them.

Or (this may be asking too much) that ability to make your own shortcuts.

Speed is everything :)

O Ilusionista

Quote from: tunglashor on January 03, 2011, 04:37:11 AM
Quote from: VirtuallTek on November 25, 2010, 03:49:06 PM
Yes, I know. FF3 supports 5, 8, 24 and 32 bits. But I don't have any specific information about 1.1 format (eg. internal loader version counter).
I've added support for the new 1.1 formats to one of my tools, so can provide details if you still need them :tipshat:

Good, send this info to VT, because he doesn't have access to Mugen 1.1 yet.

VirtuallTek

#151
QuoteI'm still hoping for a few screenshots of it. Palettes, sffv2 and the .def screen mainly (i would like to see if i have to rant for a bit if the .def is still that checkbox rubbish)
I will provide some screenshots when I finish the work in interface.
About .def editor, as I said before, will be in text mode.

Quote from: mrs. nesbit on January 03, 2011, 08:40:36 AM
If ya need an SFF that makes use of that for testing purposes, I'll send that over as well. Because ZCharCad 9 could NOT open up the SFF file in question.
OK, send me the SFF.

Quote from: I.L.U. on January 03, 2011, 10:14:49 PM
Quote from: tunglashor on January 03, 2011, 04:37:11 AM
Quote from: VirtuallTek on November 25, 2010, 03:49:06 PM
Yes, I know. FF3 supports 5, 8, 24 and 32 bits. But I don't have any specific information about 1.1 format (eg. internal loader version counter).
I've added support for the new 1.1 formats to one of my tools, so can provide details if you still need them :tipshat:

Good, send this info to VT, because he doesn't have access to Mugen 1.1 yet.
:sugoi: But, now I have access to Mugen 1.1, thanks to K'Style. And, SFF v2.01 is already implemented.

Quote from: montyoum on January 03, 2011, 03:28:19 PM
I would only ask that the keyboard shortcuts get somewhat simpler. I.E. most of the shortcuts that are ctrl+shift+... could just be ctrl+...

And that there be more of them.

Or (this may be asking too much) that ability to make your own shortcuts.

Speed is everything :)
:sugoi:

[]s

Jesuszilla

Also will you have it so it remembers the window size and minimize/maximize? Currently, it always starts maximized in Windows 7 64-bit (not sure about other OSes) and when I minimize, it's always the set size.

VirtuallTek

Quote from: Jesuszilla on January 14, 2011, 04:16:37 AM
Also will you have it so it remembers the window size and minimize/maximize? Currently, it always starts maximized in Windows 7 64-bit (not sure about other OSes) and when I minimize, it's always the set size.
Yes, it is easy.

Interesting information:

Compression ratio in SFF with WinMugen as base:
WinMugen (SFF 1.01)  - 100%
Mugen 1.0 (SFF 2.00) - 90,6%
Mugen 1.1 (SFF 2.01) - 65,4%

Obviously, it is approximate and depends on the content.

Based on file size, lower is better.

[]s

O Ilusionista

VT, I've found a bug on FF

when you impoty some sprites from another SFF, it doesn't takes the right numbers of the group,image

for example, if you have:

900,0 - 900,1 - 900,2

It will import as:

900,1 - 900,2 - 900,3


Jesuszilla

#155
Quote from: VirtuallTek on January 17, 2011, 02:23:42 AM
Interesting information:

Compression ratio in SFF with WinMugen as base:
WinMugen (SFF 1.01)  - 100%
Mugen 1.0 (SFF 2.00) - 90,6%
Mugen 1.1 (SFF 2.01) - 65,4%

Obviously, it is approximate and depends on the content.

Based on file size, lower is better.

[]s
Yeah I actually noticed that when I sent you the SFF. When I zipped it up, the file size was about the same because it was already compressed. Pretty awesome.


Also, I forgot, have you fixed the problem of CLSN2Default stacking up in the CLSNviewer and making it hard to tell which CLSN is the current? It also slowed down animations.

VirtuallTek

Quote from: I.L.U. on January 17, 2011, 02:34:42 AM
VT, I've found a bug on FF

when you impoty some sprites from another SFF, it doesn't takes the right numbers of the group,image

for example, if you have:

900,0 - 900,1 - 900,2

It will import as:

900,1 - 900,2 - 900,3

OK, i will check it.

Quote from: Jesuszilla on January 17, 2011, 02:57:59 AM
Quote from: VirtuallTek on January 17, 2011, 02:23:42 AM
Interesting information:

Compression ratio in SFF with WinMugen as base:
WinMugen (SFF 1.01)  - 100%
Mugen 1.0 (SFF 2.00) - 90,6%
Mugen 1.1 (SFF 2.01) - 65,4%

Obviously, it is approximate and depends on the content.

Based on file size, lower is better.

[]s
Yeah I actually noticed that when I sent you the SFF. When I zipped it up, the file size was about the same because it was already compressed. Pretty awesome.

Also, I forgot, have you fixed the problem of CLSN2Default stacking up in the CLSNviewer and making it hard to tell which CLSN is the current? It also slowed down animations.
You can explain more about this?

[]s

Jesuszilla

When you add new CLSNdefault to an anim, they keep stacking up in the viewer. This slows down the animation preview and makes it impossible to tell which CLSN was the last unless I run in MUGEN. It's REALLY annoying.

VirtuallTek

Quote from: Jesuszilla on January 17, 2011, 05:39:01 PM
When you add new CLSNdefault to an anim, they keep stacking up in the viewer. This slows down the animation preview and makes it impossible to tell which CLSN was the last unless I run in MUGEN. It's REALLY annoying.

Oh, yes.
This problem isn't present in FF3. FF3 have a new sprite/clsn renderer writen from scratch (see ZCC9, but is more complex than it). You add CLSNs with drag and drop, drawing the box on the screen.
You must click in the first point and drag to the last point. After it, FF3 keeps the last box selected.
And, another new feature is when you click in a clsn that is already selected, FF3 selects the clsn bellow it (when available).

[]s

Jesuszilla

Yeah I tried looking in ZCC9, but it doesn't display it correctly, either. It only shows the first CLSNdefault.