Open GoogleCodeExporter opened 8 years ago
Hi,
JMugen is in alpha Phase so, There a many many bug.
You can post issue, when the beta will out.
And at this time i will correct them.
I will change the name of the demo to alpha, i am sorry i put beta.
Original comment by lknhi...@gmail.com
on 18 Mar 2009 at 11:21
Well, it's not really a complain, just a reminder.
I know that you are actually developing jmugen alone, not an easy task.
Is it running too fast on your system as well?
BTW to me the definition of alpha/beta etc. doesn't fit very well opensource
projects.
Just my opinion.
Original comment by silicon...@gmail.com
on 19 Mar 2009 at 10:36
ha, Sorry :p i don't know very well opensource license, i just put this project
in
opensource so if some new developer do no want to re invent the wheel, they can
take
some ideas, and choose GNU license by default. :P
I know only that alpha, is for internal
and beta is near RC
and RC is near Final lol
Sorry about that
Anyway It is weird, because in my system it run a 60 fps.
Thanks
Original comment by lknhi...@gmail.com
on 19 Mar 2009 at 5:33
Ho have you look in LMugenTimer ? it is the implementation of the timer
Original comment by lknhi...@gmail.com
on 19 Mar 2009 at 5:34
Hi,
I'll try to do a clean checkout and rebuild, and I will let you know as soon as
I can
if the issue persits.
Maybe you have some sort of "monitor refresh synch" enabled in your graphics
card
control panel? My ati card has it but I disabled it.
What I meant is that alpha/beta/rc/ect. is more suited to commercial projects
than
free ones, you don't have a big company's CEO breathing on your neck to get a
"final
release"...
Instead you work on it as you please and whenever you find the time.
You don't need to have a release, it just needs to work and be reasonably bug
free.
Happy about your choise, GPL is always good :D
later
Original comment by silicon...@gmail.com
on 20 Mar 2009 at 12:34
I also get the same problem with FPS running too fast, trying to checkout the
code
for LMugenTimer but getting 400 Bad Request error. Raised a separate issue on
this...
cheers.
Original comment by yun.zhi....@gmail.com
on 23 Apr 2009 at 12:19
Original issue reported on code.google.com by
silicon...@gmail.com
on 18 Mar 2009 at 2:26