Forum Replies Created
-
Posts
-
For those who want a white themed docs:
http://turdus.be/monkey2docs/whitedocs/The official docs are now white themed.
I just read your other answers. So, in theory, Ignition-X should work in Cerberus? or are they also modernizing the language? Do they still use Mojo1? If not developed by Blitz, who’s behind it?
Yes ignition should work with cereberus-x as mojo1 is included. I think Ignition-x turned open source too. Some directories have their name changed and some features have been added (at least enums I think). Building monkey-x/cereberus-x from source is a lot more difficult.
The guys behind cereberus (I don’t really like the name change!) are former monkey-x users who had published some games. They have their own idea of how things should go. They visibly hoped Blitz-Research would continue to work on blitzmax and monkey-x (like adding 3D and other stuffs) and now take profit of the great move Blitz made by open-sourcing these two products.
After around 100 plug-unplug of two different gamepads I had no crash… Nothing except some few times the pad was not detected but I think it’s a normal usb thing when you change plugs too fast.
Yes! Technology demonstration!
there’s a git guide (dunno if it’s up to date):
—–
There’s just one thing missing, after uncompressing the mingw version provided into the ‘devtools’ folder,
I had it in my PATH but tried without it in my PATH and it worked too. MMMmm!? But Yes building monkey2 is a piece of cake.
It’s even easier on Mac!final questions:
-Is Playniax’s Ignition-X compatible with MOnkey 2?
-Is Cerberus-X the continuation of Monkey-X?
-For a Linux version, would it be possible to link all the libraries locally instead of dynamically? That way a build would be possible as a single download.-Nope ignition-x is not compatible (it’s based on mx1’s mojo1 which is not even opengl ES based so should be hard to port..)
-Yes Cereberus-X is a fork of Monkey-x that had had some commits to get it working with latest environments. But I must say apart from the HTML5 very fast thing, I’m more into mx2 now. MX2 is a much more modern language although looking more or less the same, and the garbage collector of MX2 has a better design in order to avoid hiccups. Cereberus-X is the only monkey-x fork actively updated. Blitz-research is not working on Monkey-x anymore.
-I know there are some license problems about static linking but don’t know exactly what/how.This link might help you building mx2 on linux. It’s a bit old. But worked fine for me at that time. Now I’m on w10..
Don’t download the master branch but the dev one!
For your w10 install problem its 95 % probability you AV has quarantined something on the fly.EDIT: tried to build latest dev on an old mint 17 (office) machine and worked fine with the following:
extract monkey2-develop from github on your desktop
open terminal and type:123456789101112sudo apt-get update && sudo apt-get upgradesudo apt-get install g++-multilib libglu1-mesa-dev libopenal-dev libxi-dev libxrandr-dev libxinerama-dev libxcursor-dev libxxf86vm-dev libx11-dev libgl1-mesa-dev libpulse-devcd Desktopsudo chmod +x -R ./monkey2-developcd monkey2-develop/scripts./rebuildall2go.shthen wait
had bananas musictest and monkeyroids working fine.
(The Key.Key1 was not working in audiotest though? Maybe because I have an AZERTY keyboard and the Raw mask was not used?)Just step several times before rendering.
For example set steptime to 1/240.0 then step chipmunk 4 times before rendering. Then when you want to slow it down or accelerate it just change the number of step calcalations before render.
This way it will always act the same way. You’re just modifying the play speed.Hi
just had a rebuild of the latest dev branch (rebuild mx2cc + rebuildall) because I saw the commit about the atlas thing but no luck I get the same results as etheraut’s version (with drawPrimitive).
too bad. Maybe there’s still something to add to the repo before I can test the code below?Will look into adding some white theme ASAP but it’s not soon.. sorry bout that.
Yes, extension should behave just the same as classes/struct and a framework end-user shouldn’t need to pay attention to that kind of things IMHO.
I have now:
35.5k on a 3630QM laptop with GT635M ON, on W10 (had to force GPU manually (optimus thing))
13.4k on a 3630QM laptop with the i7(HD4000) integrated graphics, on W10. One strange thing is that when I reach the limit it switches to 30FPS directly and stays there! and if I want to go back to 60fps I first have to go back to 8k…?
14.3k on a 3630QM laptop with the i7(HD4000) integrated graphics, on MacOs ElCapitan. no strange FPS switching to 30FPS on this one! Mac performs better that W10 on the exact same hardware! Who would have guessed it?)
I’m getting 3k on a 3630QM laptop with GT635M.
Strange thing is desktop or release only slightly affects speed!Do you know there’s a FPS count for you? No need to use millisecs and all the stuffs (and your avg was sticked at 62 because you where using only integers in your division so it was not able to show the real 60) You should always put a float in a division if you want accurate results.
Local avg := 1000/( ( elapsed /frames*1.0) )
canvas.DrawText(” FPS: ” + App.FPS, 300, 0 )
Looks cool! Hope you’ll share.
For my own use a go back to Monkey-x wouldn’t be possible because I like the way monkey2 is a stricter language (impotrant for bigger projects).Also monkey2 can create console apps easily and can integrate external C/C++ code that can be used for all the platforms so you do the job only once.
HTML5
However if you want to go the easy way regarding html5 deployment, monkey-x is far faster for compilation and easier to install as it has its own html5 transpiler. It doesn’t use third party emsrciptem that is a bit complex to install as I can see on this forum (I’m not deploying to html5 anymore since i’m on mx2).
Android
On android, monkey-x can also inject your app directly in you device but it’s not a real advantage for larger projects as you’ll probably want to get full control over your app via android studio anyway.
Monkey2 uses native C++ code so if you want to add android system stuffs not available out of the box in mx2 you’ll have to master JNI. So for that point monkey-x can be a bit easier as you can import java code lines directly in you monkey-x code if needed. But it’s a bit specific.
Ios
I don’t have an IOS device so I don’t really know but it looks like it’s more or less the same than with monkey-x
Desktop
Mx2 desktop is clearly superior to mx1. It uses sdl2 instead of glfw and runs really smooth. you can create console apps easily. Mx2 is more versatile on desktop.The big advantages of mx2 over mx1 for me:
-The design of the Garbage collector is way better and you don’t have those annoying ‘hiccups’ you sometimes have with mx-1. Witch is very important for ‘pro’ action games and other realtime apps.–>more professional result
-The OOP features of mx2 are very advanced (inspired by D as I undestand). It makes the language super productive once you get them.
-In mx2 you have pointers and first class function (more or less function pointers). witch is not mandatory but can be important for some optimization parts of the code, and to import C/C++ libs easily. –> once again more professional feeling.
-The language is stricter so you have a better protection against you own stupidity. Very important for larger projects. –> more professional once again.So to me both are great but blitz product has often had the image of “good for prototyping but not for final development” witch is not the case for mx2 to me. With mx2 you can prototype *and* finalize large projects. That makes mx2 a more “serious” candidate.
Mx2 is still a bit young, though functional, you won’t find much examples/showcases. especially for mobile platforms and 3D projects.But hey!, the community forum rarely leaves you with an unanswered question *and* Mark Sibly (the creator) is active on this forum so you’ll often get very accurate answers!If you use mx1 in strict mode it shouldn’t be too hard to switch to mx2 later (porting code can be a bit long). You’ll just have a bit more possibilities with the mx2 language but you’re not obliged to use them!
In summary
You want quickly compiled HTML5 target for fast prototyping/playing-around -> go mx1
You want serious stuff with fast running code without hiccups and think about a larger project -> go mx2 (or any other serious dev environment). This hiccup thing was a real problem for me when I was on mx1.I’d personally suggest you concentrate on mx2 so you learn stuff only once and you’ll get more fluid executables.
Using latest dev branch, I could comment all “private” tokens in canvas.monkey2. Then rebuild mojo. Then access the private canvas fields with no compilation crash.. You could set the members you want to acces to “protected” so you can extend.. or just play with your own modified Canvas class. If I where you I would build mx2 from latest dev brach as it is version 1.08 wich is a bit more stable than the latest ich release.
