Page 1 of 1

SMBX2 is too hard to use

Posted: Tue May 04, 2021 2:36 pm
by Igneouss
Basically the problems and the reason I don't use 2.0 are the overly complex interface and extremely long loading screens. It's not like 1.3 or 1.4 where all section events, tools and options were grouped into buttons and no loading screens for testing levels, while 2.0 has too many buttons for different things and too much loading screens for opening and testing levels. An option to group the buttons of certain actions into one would be good and would help make the creation of levels easier

Re: SMBX2 is too hard to use

Posted: Tue May 04, 2021 5:58 pm
by ben
@ 1gnacio25: Welcome here. :)
1gnacio25 wrote: Basically the problems and the reason I don't use 2.0 are the overly complex interface and extremely long loading screens. It's not like 1.3 or 1.4 where all section events, tools and options were grouped into buttons and no loading screens for testing levels, while 2.0 has too many buttons for different things and too much loading screens for opening and testing levels.

What you are describing, I can not (currently) confirm for myself.

I am currently satisfied with SMBX 2.

Of course, there could are differences of opinion on this too. :)  

Maybe what you described might be due to the fact that SMBX 2 is still in beta?

Re: SMBX2 is too hard to use

Posted: Tue May 04, 2021 6:00 pm
by Kumatora
1gnacio25 wrote:
Tue May 04, 2021 2:36 pm
Basically the problems and the reason I don't use 2.0 are the overly complex interface and extremely long loading screens. It's not like 1.3 or 1.4 where all section events, tools and options were grouped into buttons and no loading screens for testing levels, while 2.0 has too many buttons for different things and too much loading screens for opening and testing levels. An option to group the buttons of certain actions into one would be good and would help make the creation of levels easier
kinda tru not gonna N.G.L.

Re: SMBX2 is too hard to use

Posted: Tue May 04, 2021 6:03 pm
by Luna
ben wrote:
Tue May 04, 2021 5:58 pm
@ 1gnacio25: Welcome here. :)
1gnacio25 wrote: Basically the problems and the reason I don't use 2.0 are the overly complex interface and extremely long loading screens. It's not like 1.3 or 1.4 where all section events, tools and options were grouped into buttons and no loading screens for testing levels, while 2.0 has too many buttons for different things and too much loading screens for opening and testing levels.

What you are describing, I can not (currently) confirm for myself.

I am currently satisfied with SMBX 2.

Of course, there could are differences of opinion on this too. :)  

Maybe what you described might be due to the fact that SMBX 2 is still in beta?
I guess this is more of a preference thing. I personally prefer the 38A overlay (the 1.4.4 one. to be more precise) as well, but I know there are many people who prefer the PGE editor. I guess we're all just used to the engine we've been using for some time by now and would take time to get used to a new editor layout etc.

Re: SMBX2 is too hard to use

Posted: Tue May 04, 2021 6:36 pm
by ben
DerEric wrote:
Tue May 04, 2021 6:03 pm
I guess this is more of a preference thing. I personally prefer the 38A overlay (the 1.4.4 one. to be more precise) as well, but I know there are many people who prefer the PGE editor. I guess we're all just used to the engine we've been using for some time by now and would take time to get used to a new editor layout etc.
I'm not so familiar with the similarities and differences of the individual versions. :)

I use concerning SMBX currently SMBX 2 in the beta phase, because to my knowledge it is the official successor of the official version 1.3.0.1.

And of course I'm looking forward to the full release of SMBX 2. :) (2.0.0)

Re: SMBX2 is too hard to use

Posted: Thu May 06, 2021 4:34 pm
by ben
Off - topic:
ben wrote:
Tue May 04, 2021 6:36 pm
I'm not so familiar with the similarities and differences of the individual versions. :)
Where can I find informations about the different versions? :)