I'm a graphics slut.
Also, a lot of characters have their Explod and Helper being misplaced in 1.1 only due to lazy coding from the authors (they could have just set postype = p1 ffs, it wasn't that hard
My loyalty will stay with 1.0.
It's much more stable and to me, allows more freedom than 1.1.
1.1 is still a beta engine compared to 1.0.
Once it's fully released, I'll probably change.
My loyalty will stay with 1.0.
It's much more stable and to me, allows more freedom than 1.1.
1.1 is still a beta engine compared to 1.0.
Once it's fully released, I'll probably change.
Its actually the opposite 1.1 can do more and saves you loads of time if you don't plan to index, also 1.1 has all the features 1.0 has.
My loyalty will stay with 1.0.
It's much more stable and to me, allows more freedom than 1.1.
1.1 is still a beta engine compared to 1.0.
Once it's fully released, I'll probably change.
Its actually the opposite 1.1 can do more and saves you loads of time if you don't plan to index, also 1.1 has all the features 1.0 has.
...and there are no stability issues whatsoever. I guess he hasn't really used the 1.1 engine enough to realize what it has to offer.
Welp, everything I tossed at 1.1 ran with no issues. I even used some really old chars like Sanders Wolverine.
You can turn off zoom too. 1.0 runs like crap for me, and If I use localcoord on some chars it breaks some hypers or moves.
I guess it all boils down to the coder's ability all of the chars in my roster were made for 1.0 and I have no issues with it.
The only real issue 1.1 has is that it does not map pals to the small ports. ( which can be addressed) however most of the people using 1.1 I assume use custom ports.
I get the feeling some people here think 1.1 lacks features and that's not true at all.
1.1 is the more powerful version of the engine and that's a fact.
I still use 1.0. For some reason, stages I use in 1.1 crashes while in 1.0 does not. Most of those stages are taken back when I used Winmugen and the ones that cause 1.1 to crash that come to mind are JAM's Street Fighter IV stages. They cause 1.1 to close completely, so I know it's not stable. Does anyone know that author have anything to do with it crashing?
Another reason is the lifebar portrait thing and the menu sound cut outs. I have a client that heavily relies on small portraits for the lifebar and not seeing them change along the palette bugs me. I even tried using 1.1 for Capcom vs SNK MUGEN and it keeps cutting off.
The JAM stages are due to code that is obsolete I believe. No stage has made my Mugen crash other than JAM's and neither has the menu sound cut off for me ever. I use custom portraits so the palette thing doesn't concern me at least. I for one am very happy with 1.1 but I guess its the users with really old hardware that complain the most.I figured it had something to do with JAM. Those were originally Winmugen stages and did had a lot of color loss, but it should have worked regardless of version. For the menu sound cut off thing, it must be screenpack dependent as I used Akito & OldGamer's Capcom vs SNK MUGEN which was causing problems with sounds. I liked that one because it fits the PotS theme, but this will probably force me to use other screenpacks.
So I guess the verdict is out? 1.1 is the more popular version.Based on what, the forum post and the 60 or so people who voted in the poll?
I'm with SolidZone on this one. Sound cut-off in screenpack and ports not sharing colors are really annoying, but besides this, I like using 1.1 because of the zoom feature. I also avoid OpenGL because my microwave drops FPS. Also since I'm constantly making content for MUGEN, I use 1.0 to test as I see people still uses it, I want to make my creations compatible with both. I'd do the same with WinMUGEN (yes, people also still use it) but there are some codes that are a must and crashes on WinMUGEN.I should also mention that there are certain characters who have lifebars portraits that can glow such as Jmorphman's Chun-Li (Shadow Lady Mode) and Demitri. 1.1 completely breaks that feature and no custom portrait could ever fix that. If Elecbyte would ever come back to make 1.1 out of beta and fix all those issues, I would use it 100%.
Menu sound cut-off only occurs during screen transitions; you may have never noticed this because the fade durations are long enough for the sounds to play out fully in whatever screenpack you're using.I think I remember when OldGamer helped Akito make the Capcom vs SNK Mugen screenpack, Akito wanted it to be for 1.0 as 1.1 doesn't run very well for him on his computer, so it was built for that in mind and was converted to 1.1 later on. That's probably why it had those issues.
So I guess the verdict is out? 1.1 is the more popular version.Based on what, the forum post and the 60 or so people who voted in the poll?
So, I want to use this topic to give me some light. Is it true that 1.0 is better for older computers? I use 1.1 but everything I have here is compatible with 1.0, except for some stages with zoom (which of course I can disable if I switch). Right now I sometimes experience a bit of FPS drop with 1.1, if I switch to 1.0 will the performance be better? Or am I missing something that makes 1.1 not drop frames (in mugen.cfg maybe)? Thanks in advance.
The thing is I use DirectX on 1.1 too, and I still get fps drop sometimes.
I know how to fix it:
use 1.0 instead. :twisted:
People keep saying 1.1 is stable, but when I run 1.1 it just closes out of itself at some point.
No warning, entries in log or anything, it just exits the game.
Anyone else have this issue or know how to fix it?
Mugen 1.1 unstable? Constant crashing? Dafuq are you people talking about?
Stop being poor and get a decent gaming rig.
The only time I've had 1.1 crash on me is when a character or stage was incompatible, and that's an easy fix.
The fact mugen 1.1 won't run on your toaster isn't its fault.
Mugen 1.1 unstable? Constant crashing? Dafuq are you people talking about?
Stop being poor and get a decent gaming rig.
The only time I've had 1.1 crash on me is when a character or stage was incompatible, and that's an easy fix.
The fact mugen 1.1 won't run on your toaster isn't its fault.
Not everyone has the money for that, you know.
Mugen 1.1 unstable? Constant crashing? Dafuq are you people talking about?
Stop being poor and get a decent gaming rig.
The only time I've had 1.1 crash on me is when a character or stage was incompatible, and that's an easy fix.
The fact mugen 1.1 won't run on your toaster isn't its fault.
I don't think your puny gaming pc is quite as expensive or as powerful as my Nvidia Quadro card alone.
yeah, that line out of context comes out arrogant as hell, but in context it is pretty apropiate.
No its not, it has a few bells and whistles over mugenYou undermine whats been accomplished. You can only see things at face value. What you say doesn't really hold any weight, your perception, not facts. If you can't properly contest this, really nothing else needs to be said. "It's not good because I had a bad experience"
I've also seen people pull off some amazing shit in mugen that emulate the official games, screens, moving chars on the select screen etc.
Ikemen is badly optimized and it feels "off" to me when I play it, it runs super fast and some weird shit is happening in it.
99.9% of the chars are made for mugen it makes sense they run better on it.
I have not undermined shit, for a comment that states that mine holds fuck all, I have yet to see "facts" from you as well.
Mine showed 2 examples of people pushing the engine, where's yours ?
Yeah, that was my point.
If people can't afford/don't want to, they don't.
There was no need to tell people to buy stuff because theirs sucks to begin with.
Guess you would've known if you didn't singled out that one line and put it out of context.
I still don't see what some of you are talking about regarding error less crashing. Have you tried the 4Gb patch? When it dies does anything populate in event viewer?
Yes, I have tried the 4GB patch.sigh, looks like the 4GB patch is the same :(
But the problem I have with 1.1 is it "closes" itself at some point, like how a user would manually close it.
It's not the usual crash which tells you something went wrong, it gives me nothing, no error prompt, not even a log.