Well since the Alpha 4 build is readily available now to everyone, I guess it is ok now to use this thread to discuss any questions, bugs, tutorial links etc relating to Mugen 1.1 Alpha4.

Let me start by asking: Are all 1.0/Winmugen stages compatible?
And if not, is there an update tutorial anyone can direct us to? (I'm not talking about stage zoom tutorial)

I recieved this stage error bug already with a randomly selected EXshadow stage and several others:

Code:

BG error reading stages/EXSHADOW/XX'TRON'XX.def
Clipboard tail:
Selected char 45 on teamslot 0.0
Char Marrow.def (45) request pal 5 FFF (FFF) -> reserved 5 (FDF)
Selected char 77 on teamslot 1.0
Char cvsFevrier.def (77) request pal 5 FFF (FFF) -> reserved 5 (FDF)
End of charsel loop
Game loop deinit
Gameflow 8
Gameflow 9
Gameflow 10
Entering versus screen.
Unloading match assets
Freeing players
Game loop init
Versus screen init
End of versus screen loop
Game loop deinit
Gameflow 11
Loading match assets...
Loading stage...
Info: stage Ex Shadow - Tron loading in pre-1.0 compatible mode
  Loading BG...

All stages with zoffsetink has issues with deltas.

Not my interest in keeping 1.1 since it's still unstable.

Actually I just fixed my problem there too. Mugen 1.1 had directory issues too.
If you keep stages their own folders say like: stages/guiltygearstages/verdant.def, it will show the error mssg above but when it is in the main folder stages/verdant.def it works fine....weird. Yeah I dunno if I luv or hate this, but atleast 32bit colour lol

I'm not going to go to 1.1 either. I'm going to experiment with it, but i'm sticking to 1.0.

Yo, FF3 works fine with 1.1 right?

Watta wrote:I'm not going to go to 1.1 either. I'm going to experiment with it, but i'm sticking to 1.0.

Yo, FF3 works fine with 1.1 right?

yep ff3 works fine. I added some unindexed 32bit png portraits with transparency and glowing edges as a test:



No more indexing and 8bit makes me so happy wanna cry....

having to remake my whole goddamn SP in 1080p with 32bit PNG makes me wanna die...........

DOUBLEPOST

I just found a very big bug worth mentioning.
The bug is called "Where the F&*# is my projectile" when using zoom stages:


This is what is happening - If you stand at the max stage bound away from opponent on any zoom enabled stage, it wont draw your projectile attacks at all.

If you slightly go closer to the char, they will draw but stop near the character, and if you run after your projectile, it will hit the character normally....WTF???

Thats one of the resoons i don´t use the zoom.
It just screw up some characters moves.

I just use it cuz the 32 bits images and how well it works at HD.

have another doozie regarding 1280x720 resolution....

Am I correct in saying that to prevent incorrect scaling of all winmugen/1.0 characters that have a default localcoord of 320x240 (eg pretty much everything except blazblue, persona, and a few other HD characters) correctly in Mugen 1.1 when using 1280x720 resolution,
a character localcoord of 480,360 needs to be set?

I just tested this and it seems so...let me know all your thoughts

I normaly see that a Localcoord of around 426, 320 to 400, 300 are the most used i think.
But imo depends more on the needed for your lifebars & screenpack.
For me the screenpack & lifebars need a localcoord of 436, 320 so thats the one i use.

LOL
I noticed that the zoffset of that stage is wrong.

So many issues....

I,d rather stick to WinMPlus and 1.0 for now. Don't see the point in creating something for a buggier engine.

Cruz Excahm wrote:I normaly see that a Localcoord of around 426, 320 to 400, 300 are the most used i think.
But imo depends more on the needed for your lifebars & screenpack.
For me the screenpack & lifebars need a localcoord of 436, 320 so thats the one i use.

LOL
I noticed that the zoffset of that stage is wrong.

Very helpful - thanks cruz. 426,320 seems to be what i am looking for - that seems to work for what Iam going to use. Actually interestingly enought I did some research and discovered that the whole scaling thing gets quite intricate because capcom CPS2 character sprite aspect Ratios and SNK KOF /neogeo character sprites work on different ratios:

CPS2 uses Raster, 384 × 224 pixels (horizontal), 4096 colors as per Wiki, while KOF is again different. 426,320 seems to be a universal fix for ALL lores characters in a 1280x720 or 1920x1080 mugen 1.1 res tho.

No offense from everyone, but I'm still sticking to WinMugen.

mAdLaX wrote:No offense from everyone, but I'm still sticking to WinMugen.

I respect that brother. TBH the only attraction to 1.1 for me is the png support and full HD capabilities, plus the fact that we can finally utilize GPU Vram. damn 1920x1080 uses 99% of my Vram on GTX480 SLI - its using 3072MB total LOL! Ima get me 2 x GTX Titan SLI soon for a total 12GB Vram and see wat POWAH this baby can really unleash. i need to upgrade my power supply for that to 1500W too. But seriously, mugen 1.1 requires alot of work - more time modding and creating than actually playing

Phant0mD wrote:I respect that brother. TBH the only attraction to 1.1 for me is the png support and full HD capabilities, plus the fact that we can finally utilize GPU Vram. damn 1920x1080 uses 99% of my Vram on GTX480 SLI - its using 3072MB total LOL! Ima get me 2 x GTX Titan SLI soon for a total 12GB Vram and see wat POWAH this baby can really unleash. i need to upgrade my power supply for that to 1500W too. But seriously, mugen 1.1 requires alot of work - more time modding and creating than actually playing

This is just an Alpha Version, who knows when the full version is released. It might have more features than what just being stated.

ooh 1.1 at long last...
but might as well wait a yr or so...till it gets tightened up...

If it even does.


Then again..

Currently having issues with the forum. We're investigating it and hopefully it'll be back up soon.

Thanks.

Update: It might be a couple days before the forum comes back up. I don't want to open the forum back up until I can confirm what happened with our server admin. As far as I can tell, all the posts, etc are still there.

- dfw

Quoted from Elecbyte forum today.

At least they're still AROUND. That's what a majority of the people encouraging the leak wanted. Confirmation that they're even working at all. Obviously they're doing SOMETHING to fix their forum, who's to say they aren't doing engine work?


Just because you're a beta tester, doesn't mean you get ALL stabilized versions immediately. They try to develop the engine with the mistakes they notice THEMSELVES and send it to them for testing. So you could've had, what to them is an 'outdated' version.


At the same time I can see the user frustration because they did this last time. If they're busy in life and do not have time to do engine work then wouldn't it suffice to just post something like "We're still working, we just need more time, life's busy right now." Instead of ignoring it? Regardless, if they can post forum updates, they can post engine updates.


Either way, I'm willing to wait for a more completed version before I download it whether that'll happen or not.

Another 7 years for 1.1 to become stabilized guys. Let's keep on waiting. :mcmahon: