This topic contains 12 replies, has 8 voices, and was last updated by 
impixi
1 year, 2 months ago.
-
Posts
-
Just a thread to find out what others are coding away at, so, watcha coding?
My current dabblings with mojo3d physics are here.
Recently finished “Get to Da Choppa!”:
https://therevillsgames.itch.io/get-to-da-choppa
Now I need to go and do some boring stuff!
I’m working on collision code and physics, and found they are the same thing!
Also reverse cpu 2d shadow additions.
Just uploaded this demo!
Alien Phoenix 2D / 3D example (WASM).Hi, I have posted a web assembly demo compiled with Emscipten. Featuring Mark’s simple light demo (with canvas scale, rotation) and a 3D demo all running real-time in my window based GUI. If you have ever wondered what Alien Phoenix can do this demo will give you a good look.
You may have to wait for all data to be downloaded before it will run. The download data counter will hit it’s max before everything is downloaded, especially on slower connections. If you have any issues try reloading. Left-click and hold in a window to move it. Windows resize.
Rock on.
Attachments:
It looks good, runs smoothly too.
^Awesome. Glad it runs good. What video card do you have?
The Alien Phoenix framework will be available to all under the same license as Monkey. I am getting ready to release a game demo very soon and this little test helps to make sure that will go smoothly.
Video for those curious.
That was cool. Runs as smooth as silk. I do have an EVGA GTX 1080 8gb though with 32GB system ram.
^Thanks. I have a GTX 950 and it runs great here at 60 FPS. So far I have had no reports of any issues (currently on IndieDB) which is a ‘ding’ to Monkey and Emscripten as well as my framework. I’ve designed the framework from the ground up to be as efficient as possible which translates into excellent performance.
I hope that when Monkey coders see that you can write one app and have it use the same interface on a PC, tablet or browser they will embrace the framework. In addition to a window based GUI (the heart of the framework) coders will have access to layered mapping resources that allow for vast player maps as well as other resources. In fact integrating a coders own or third party code is fairly easy as evidenced by the demo. You can get a look at the code for the demo here.
At first I’ll be releasing the code (GitHub) for the GUI part of the framework as that will be the most useful and is close to being ready for alpha release. It’s been years of work to get this far but the results are worth it.
@richard-betson Nice demo! I don’t necessarily have a slow computer, a lot of things work rather smoothly on it actually. I have unfortunate news though, on my computer the demo stutters heavily and the frames have more than a second of latency when watching the virtual mouse follow my own.
I don’t think the problem is your framework, I actually have seen this particular slow-down in my own monkey2 rendering tests. The frame-rate for any particular monkey2 project I’ve used exponentially drops with increasing canvas sizes. . . And I think since you have multiple virtual windows being rendered it might be hitting your demo hard on my computer.
I did notice that once I shrunk your windows all the way down, as to my hypothesis, the frame rate went to 56+.
My computer has
gpu: GTX960m,
mem: 8GB RAM,
cpu: i7-6700HQ 2.60HZAbe_King, Which web browser did you use? I have a GTX 950 2GB, AMD Phenom II X4 with 8GB ram. Well below your specs, so on the face of it I would think a v-card driver or other system issue exist . I would recommend Chrome to run this. I have tried it on FireFox Quantum and it runs slower but still usable.
And I think since you have multiple virtual windows being rendered it might be hitting your demo hard on my computer.
I use one single canvas at 1920 x 1080 (although windows can have independent canvas) and there is no mojox involved. I use the one canvas to draw windows as well as any 2D or 3D. This is a more efficient method and saves on v-card and CPU resources. So… the framework is ‘not’ doing anything like multiple canvases, mojox integration or using special third party code or modules. It instead uses all native Monkey code and resources.
The only thing that comes to mind is the memory size of your GTX 960m. I would recommend at least 2GB. Other then that the GTX 960 should handle this kind of demo easily, One other remote issue could be Emscripten related as it relies in part on resources available from your web browser as well as installed resources on your OS.
Edit: I may post a non web assembly version if you are up for testing.
Lately I’ve been contemplating coding a personal share management/trading system… But I have actually retired from coding (and all other keyboard-intensive activities) for medical reasons (cubital tunnel syndrome), and have been much better for it, physically. Mentally though, I do miss my daily monkey2 coding sessions…
But it’s good to see other people progressing well in their projects. Keep it up everyone!
You must be logged in to reply to this topic.