I gotcha 6fix,

On that note. I was a little disappointed with the initial tesselation stuff I've seen so far, namely the heaven benchmark. The framerate drop was more significant than I was hoping for.

Also, as far as this tech goes. Until this came alomg thered be no reason to think polygons would go anywhere. And if it proves itself to be workable, there's an entire industry of tools that would need replacing, so, no, its not going to change overnight, but the idea is intriguing, and it doesn't need to replace polygons for every developer to make it an important part of the near future.

As an aside, it seems to be a growing trend, this it-only-matters-how-many-pixels-on-screen thing. We're entering a new era of efficiency it seems. Aside from the id tech 5, and this, there's also that streaming photo gallery thing microsoft showed off when they were debuting silverlight, where there was hundreds of gigs of image data, smoothly being panned and zoomed with no lag. I predict the next 5 years are going to be sickeningly awesome for the pc end-user

>

> My brother saw this video and he said all graphic cards one day have to end one day to be replaced with this engine and whatever may come in the future, this engine could be the future of next-gen 3D gaming engine

>

If graphics cards have to "end" one day, it won't be this engine replacing it. It will be something else that has yet to be created. Not to mention, by that time we will have enough polygon performance that the difference would be difficult to notice anyways. Also, CPU manufacturers will get better at creating chips that serve as both your main processor and graphics chip.

Polygons are not going anywhere anytime soon.

I understand doubting, but you're stating all this as fact as if you're from the future. Yhou don't know what will come of this, or how how long it will take to come, if at all.

Well, the breakthrough isn't the fact that its points instead of polys, its the fact that there isn't a limit to the detail. That hasn't ever been done with voxels. From what I understand voxels are slower than polys. If it is true, its a breakthrough. By your logic, th id tech 5 is nothing new because we've seen texture maps before

Seems to me that just like I suggested in your thread about find and replace, you could also use Construct to make an app to set up your Java... that works like Construct.

definitely, but looking back at the infinite wake of my unfinished projects, if I've learned anything, it's that unless it's your fulltime job, or you don't have one, working on an editor instead of a game should only be done if absolutely necessary, at least that's the case for me

someone in chat linked this the other day

it's really mindblowing:

http://unlimiteddetailtechnology.com/description.html

the short version is that instead of polygons it uses point clouds and the speed is only affected by the amount of pixels on screen, as no point is read or processed unless it will be shown on screen as a pixel:

[quote:3kz5h6bu]Fig 1.4 shows some strange creatures with very complicated modeling, there are no straight or flat edges to be seen on them. Considering their high level models it is fair to say we could probably display about 4 of them on screen at once if you used today?s polygon system.(See Fig 1.5).....

Here are thousands of them being displayed on an ordinary laptop, using only one core, No special 3D graphics hardware is being used, and it all runs in real-time.

This is similar to id softwares id tech 5 engine, only the id engine is able to display textures of insane sizes with no affect on performance, unless the number of pixels on screen(resolution) changes :

[quote:3kz5h6bu]

using a more advanced MegaTexture approach called Virtual Texturing, which supports textures with resolutions up to 128000x128000 pixels

both are amazing as hell. imagine them combined. nvidia said it's not impressed, which translates to, OH NO!!!

What exactly does the event exporter do?

<img src="http://dl.dropbox.com/u/1013446/simpleevent.PNG">

converts to this:

+ MouseKeyboard: On Left mouse button Clicked
-> Sprite: Set position to mousex, mousey[/code:d4q1ub3z]
which after a few find/replaces (and I confess I forgot I have to manually add { }'s and ;'s until I learn to use the expression based find/replace in notepad++, but my time estimates remain the same) could be converted to this:
if (screentouched())
{
   sprite.setpositionto(touchx,touchy);
}

it'd be useful if you could copy as text, including subevents, or select multiple events (or all), and copy all as text.

yes! please do:

http://www.scirra.com/forum/viewtopic.php?f=3&t=1192

I think what they were trying to say, is that this is more basic than the most basic tutorial, ghost shooter. so maybe wait until you've got something a little more advanced before making it into tutorial form. But, thanks for contributing, and welcome to scirra!

oh here goes soldjah boy, showing up just long enough to say something stupid.

totally kidding sol. yeah, thanks again soljah, for suggesting I try plugin development again, you changed my life. if I become a millionaire developing mobile games, I owe you beer, or a joint, whatever you weirdos do over there.

I've found a way to translate a cap file to Java very, very quickly. it requires some programming know how, and some initial setup time, but once that's over, damn it's fast. and anyone confident in their language of choice can do it. but first a little background info:

So, I was using Construct to prototype my ideas for my Android game, especially because it uses procedural animation exclusively, which requires alot of trial and error. I wanted the process to be as painless as possible, so I created java functions for all the construct functionality I'd need.

I have a 'sprite' class, with a 'move to position' function, a 'set angle towards' function, etc

I've got lerp.. basically every object type I'll be using I made a java equivalent class, and every action/condition/expression also has a java equivalent.

Then I discovered that you can right click on a construct event, and "copy as text".

if you set up your java classes to be as much like construct objects as possible, you can just copy/paste into something like notepad++, and then completely convert it to java using the same set of find/replace commands each time. The whole process of converting from cap file to java takes about 1 minute 30 seconds (because you have to copy/paste, etc). After I setup a macro to automate it, I'd say it'll probably take about 15 to 30 seconds to convert from cap file to java. in short, again, Construct is awesome always, now and forever, and ever has been.

<img src="http://sphotos.ak.fbcdn.net/hphotos-ak-ash1/hs501.ash1/29676_438829659637_759624637_5710054_3141386_n.jpg">