Odb718 said, April 15, 2018, 11:32:22 pm

But I will say, the auto-hitboxes would be a blessing if you could control How Many hitboxes are used.
If you could define it as 2, 3, 4, or 5, It'd make editing those boxes soooo much faster. You'd only have to pull one or two corners a frame.

Absolutely agreed. I hope they include this option.

Odb718 said, April 15, 2018, 11:32:22 pm

But I will say, the auto-hitboxes would be a blessing if you could control How Many hitboxes are used.
If you could define it as 2, 3, 4, or 5, It'd make editing those boxes soooo much faster. You'd only have to pull one or two corners a frame.

Absolutely agreed. I hope they include this option.

Now back to the subject.

There are some syntax problems with the new ff version. The same happened with the 3rd FF version.
XAngle, YAngle, etc.. are not recognized as explod arguments, even tho they were implemented in mugen 1.1

FF3 with fixed syntax:


FF Studio:


Its not a priority, but that just makes my OCD kick in.

Using nulls as a mean to set Vars now looks 10x uglier hence the fact that they have a different kind of color with non bold fonts:

It kind of makes sense and it kind of doesn't. People that arent familiar with Null will just assume that the code won't work, since it looks like it's disabled or something.

Interpolated animations do not animate. FF3 did it in it's quircky way but at least it was something. But FF Studio just don't animate the interpolation between frames. (I've just tested with 8bit Png images).

The rest was already mentioned in this thread. There's a really RARE bug that I found with the interface that I wasn't able to replicate, but the menus on the top of the program ("Project, Edit, View, Definitions...") stoped working for some stupid reason. it happened right after I had tested a char and closed down mugen.

That's about it. Great job so far I really like some aspects of FF Studio, it's a step forward for sure.

VirtuallTek said, April 16, 2018, 07:16:29 pm

EDIT: I'll' add an option in the error window to let FF fix them by sorting sprites and converting 24/32bit images to 8bits

I swear FF3 did this already...? Seems odd that Studio doesn't.

I downloaded FF with Chrome. Anyway I disabled SmartScreen, but am now getting this error instead:

And it still crashes when trying to load the Open window.

Can confirm the sound player is better at least on Linux! There's still the odd DPI issue, though. Syntax highlighter no longer picks up "Heavy" as an issue for AnimType, however it still shows in the error list.

BindToTarget says it expects 3 parameters, but got 2; however it does have a default for the 3rd parameter which is Foot IIRC.

For SuperPause, it says it expects 2 parameters for sound, however this is completely valid:

Code:

sound = -1

For a StateDef, it says this is invalid:

Code:

;----------------------------------------------------------------------------------
; DEAD SAND
[Statedef 1106]
type = ScreenBound
movetype = AssertSpecial
physics = Null
ctrl = 0
anim = 1

[State 1106, DestroySelf]
type = DestroySelf
trigger1 = !Time

Yet once again, thanks to MUGEN's busted parser, it is valid (I do this just to mess with people lol).

It also says "Unknown parameter potarget" when I do this:

Code:

[State 147, BindToTarget]
type = BindToTarget
triggerall = NumTarget
triggerall = Time <= 1
trigger1 = Target, StateNo = 148
pos = 0,(target, Const(Size.head.pos.y)-7)

I might know what that is, and it's not a pretty solution for VirtuallTek: you need to sign your code.

I say it's not pretty because the only way to do that is to buy what's called a code-signing certificate. The cheapest I know of is from DigiCert. The reason I know this is because we had to get around that Smartscreen crap for Windows 8 at work and that was how we managed to solve that for our customer, because Smartscreen and Norton go apeshit if your code isn't signed.

If you want, I can donate the cost to you because it's important to have as a Windows dev these days. Yes, it's total bullshit, I agree, but... we have to do it.

EDIT: Could try this, too https://www.globalsign.com/en/code-signing-certificate/code-signing-tool/

Yes, I restarted after each time I changed the DPI scale.

also the program keep crashing when you try to mess with the menus and also this happen when you close the program. its keep crashing...

DPI scaling on Linux seems to have no effect. I tried 0.5 all the way up to 10 and I saw no differences.

Sound preview cuts off for some sounds in Linux (sound 2,1 in cvsfelicia I sent you is a good example) and it's slower than last time. If you need me to record a video, let me know.

Just tested the new fixes. I think the crashing is delayed, but I still occasionally get them from time to time. Now it crashes when closing 4 character tabs while in sprites, states, command, or sound and then trying to view the animations of the 5th character. If it doesn't that time, then onwards. I should also mention if you are already on animations instead when closing character tabs and then switch to states, the program will crash that way too. I have so many crash logs on my computer and I don't understand why the program keeps doing this. Right now in my opinion, the program is great for testing finished characters but not so much for making/editing them in it.

thanks for the new release!!

i've a question. if i add/modify a sprite and then save SFF, it says it find 50 errors and i've to fix them before save.

in the old FF3 this message's never appeared (in fact i'm still using ff3 right now).

since i have more than 2700 sprites to check, is there a way to know at least which sprites has "errors", so i can try to fix them?

thanks in advance.

Sound navigation seems even slower, as you have to wait for the waveform to load before the correct sound plays, which can take a second or two. Playing a sound before the waveform has loaded plays the previously loaded sound before getting cut off by the currently loaded sound.

Wow, the new tools and improvements look really awesome.

But I got a serious problem while testing a project of mine: sometimes when opening a stage, I eventually closed FFS and opened it up again, and then noticed my original stage files were deleted. For sure this happened a couple of times, as I had been recovering the stage using a backup folder. Not sure if the crashes regarding the sprite editor are also related to that;
Edit: maybe it's related to a engine directory bug? I just noticed there are new copies of the stage .sff file in the folders listed for the "Run the project in engine..." function. Still, the original files were completely gone;

Nonetheless, thank you guys for the updates. This looks promising!

- cannot save an edit project

- if adding a rgb image without transparency, it cuts to half the image and put a black block instead.

- it crash after trying to "save as" the sff file

- in the palette edit screen, if open a rgb image without transparency doesn't generate that image palette anymore

- don't have the palette organizer

Another problem I saw here was with adding sprites automatically (through the file name itself)
The option works normally when only 1 sprite is added. So if you load a file with the name "5.1" it will put the sprite in group 5 and in index 1 (as it should be)
But when you add more than one sprite at a time the program simply put all the sprites in the same group. I believe the correct would be to detect file by file. If you add the following files "1.0", "20.1", "50.2" at one time, it would add all I their respective groups and index or I'am wrong?

I can't export/save images from the thumbnails tab on the Animations Screen, independent of extension.
It works fine when i export from the Sprites Screen.

Thanks for the fix regarding the "Run the current project in engine...". Now I can test characters before putting them in my roster. However, I've been encountering a crashing issue with the program. If you have 3 characters open, try to close 2 character tabs while in sprites, states, command, or sound and then view the animation of the 3rd character, the program will stop working and crash. Losing any work or edits if you haven't saved. I did this by accident the first time and I intentionally replicated it using the same method 10 times. I hope version 3.5.1 will fix this bug.

The new fix seems to be working great! ^^
From the problems I related here, I think the only one left is the resolution problem.
I'll keep testing it when I get back home (so I can use my 1080p monitor xD)
Great work so far, VirtuallTek o/

Quote

Do you want to import with same group/index number?

Yes I do. Thank you!

Also, did I miss the button that toggles the right side window options? The one that changes things so we can sort and scroll through sff, air, and snd files? I couldn't find the button on the Neo default template. I had to go to Classic. But Classic hides a ton of other features.

Also I noticed it highlights errors when I write “Heavy” as the HitDef type; most flags for hitdefs, it not all, only check for the first letter, so “Hamburger” is also, oddly enough, valid to MUGEN.

When I open my character in FF3, it shows the green checkmark for No Errors Found

When I open my character in FFX, it shows a red X and 13 errors.

2 things:
1. Double clicking an error to jump to it only works if the relevant .CNS tab is currently active. IF possible, it would be great if FFX could also jump to the correct .CNS tab   I do see that it shows the tab # next to the error, which does help though.

2. Reviewing the reported errors against the MUGEN documentation, some of the errors are valid, and some are not.

Spoiler: Not Actually Errors (click to see content)

Unknown constant 'info.name'

Code:

trigger1 = StageVar(info.name) = "Superjail! Prison Riot"

link to StageVar in MUGEN docs

Unknown keyword 'Heavy'
(This was reported by someone else)

Spoiler: Actual Errors, which were overlooked in FF3 (click to see content)

Unknown parameter 'y' for 'PosFreeze' block

Code:

[State 1851, Cork stop]
type = posFreeze
...
y = 0

I see the only correct parameter is "value = "

Unknown parameter 'sprpriority' for 'Helper' block

Code:

[State 193, Jacknife run]
type = Helper
...
sprpriority = 3

I see sprpriority is not a valid parameter

Expected 2 arguments, got 1

Code:

[State 3300, 9]
type = HitDef
....
hitsound = -1

(Well, using -1 does prevent a sound from playing, and MUGEN does not report an error in debug *shrugs*)

Oddly, when I fixed the error pertaining to PosFreeze (changing 'y = 0' to 'value = 0'), a number of other errors suddenly appeared which seemed bugged.  When I saved and re-opened my project, they disappeared.


I am also experiencing the same error reported by SolidZone

SolidZone 26 said, April 04, 2018, 08:36:09 pm

I found a bug with Fighter Factory Studio. The "Run the current project in engine..." function isn't working as it's keeps not detecting the cns file of any character I load up. Example:

Error message: Can't read file: Constants.cns
Error loading chars/ffs_0/ffs_0.def
Error loading p1

Fighter Factory 3 doesn't have this issue and runs it fine. The cns file is spelled correctly and it's in the character's files. This makes it difficult for me to play test a character without having to run the engine itself. Do you know what's causing this?

Minor question, do you guys still have an option to change the colors of CLSN1/2Default ?

I can not do it

Another thing I noticed that is inconvenient. For importing from another project you get 2 options. Replace sprites and skip sprites. There is no add as duplicate numbers option. So when I went to import some fx from another WIP and they shared some group numbers I had no way to import without changing them in the source sff

Another thing, and it's something that I had an issue with in FF3 and (I think) forgot to mention in the project thread is that there are three buttons in the sound editor that have no icons associated with them (or at least, they don't when using the Ultimate skin), so I imagine quite a few people don't realise they're there.

• Split on modules with support for multiple engines.
• Project file explorer (will be essential for full game development).
• OpenGL is mandatory, but a software rasterizer alternative is available too.
• Updated to latest version of Qt framework.
• Hybrid parser/syntax highlighter (smarter, faster and more reliable).
• Multi-threaded (long tasks are split across all available CPU cores).
• Import from another project can import from any supported engine too, and has collision resolution.
• Backup function restore files by replacing them and reloading, instead of just loading the backup on memory without changes in the original files.
• 'Project -> Save' improved. Saves all modified files and call save as for those who lives on memory only as expected, on all projects of the same 'group'.
• 'Project -> Save as' improved. Saves all files of the current 'project group' to a new folder (copy them in its current state to a new folder). Eg.: open a character, make a copy of it on another folder to create a new one based on the first.
• We can even make a full copy of a default engine installation to make a full game.
• 'Project -> Run in engine' improved. All bugs solved, faster than before, and on a full game 'project group' runs on the game itself.
• Undo, redo, cut, copy, paste, find and replace available in all editors. You can even undo complex things like changes on sprites.
• Zoom available on code editor too.
• Built-in image editor inside sprites editor.
• Import replace sprites with same group/number.
• Ability to resize one or more sprites outside image editor (you can scale all sprites with hit box adjustment/scaling in one batch).
• Default background is set based on localcoord.
• Contact Box drawing always use the same type as current ones (default or not), or non-default if there's none.
• Better support for frame interpolation, including timeline controls.
• Onion Skin on animations changed from sprite to animation/frame.
• Complete support for high DPI displays.
• Palette generation and 'Adapt image to palette' with better support for alpha channel (can produce anti-aliased 8bit sprites).
• Animated GIF generation works even with non-8bit sprites (adapts to 8bit).
• Better interface preset system (adjusts to available space and scales nicely).
• Drag and drop support on the Organizer.
• Sound file viewer on sounds editor (basic editing functionality will be added over time).
• Added fold all/unfold all for code editors.
• Improved 'Export to HTML function' (tries to detect AI commands to uncheck them).

• Parser groups allowed code by file type.
• Added A1 transparency shortcut in Animations editor.
• Added full support for frame interpolation.
• Improved offset viewer and throw creator.
• Fixed PCX decoding (solves some issues on portraits in SFF v1).