Re: Unleashed progress thread. (Previously Line Rider C progress thread.)

[darklight]

any way you can make it work w/ macs with less than 10.7? I nearly jizzed my pants when I saw this, only to be crushed by an error message. I'm way too cheap to upgrade yet. maybe christmas.

[mhenr18]

Yeah I've still got the Snow Leopard SDK and Xcode 3. I'll do a build later.
Any less and you're SOL.

[mhenr18]

My god......

I just spent the past day implementing a [censored] of texture caching in Unleashed.
It paid off.

I'm panning around a track with 2 million lines in it.
6.1% CPU
734MB RAM
60fps

There's literally no difference between any line count any more. This is surreal, once I fix the bugs LR's gonna be a totally different game. The only limit is now the amount of RAM in your system. 1 million lines = 365MB.


EDIT: oh good god I just disabled vsync and let it render frames as fast as the system can handle. I'm getting over 1800fps with 2 million lines

[[senpai] kevans]

My god......

I just spent the past day implementing a [censored] of texture caching in Unleashed.
It paid off.

I'm panning around a track with 2 million lines in it.
6.1% CPU
734MB RAM
60fps

There's literally no difference between any line count any more. This is surreal, once I fix the bugs LR's gonna be a totally different game. The only limit is now the amount of RAM in your system. 1 million lines = 365MB.


EDIT: oh good god I just disabled vsync and let it render frames as fast as the system can handle. I'm getting over 1800fps with 2 million lines

OMFG!

[mhenr18]

i dont think you'll be able to get as good as that in your flash builds hehe

[Derpinator]

i can have 11.000.000 lines then... wierd

[[senpai] kevans]

Hang on.... I think Ive spotted a bit of an error.

During the time when I tried to make LR HD/Engine 2, I noticed some stuff.

[this being said in a nut shell] In order to make it run the same speed at 60 FPS, I had to change a few numbers. This meant different physics. So basically there was two trade offs...
1) Same physics, slightly faster speed
2) Normal speed, new physics.

Mhenr, you saying that this runs at 60 fps, does this mean one of the previous said situations, or is this only for testing?

[TheRevTastic]

Hang on.... I think Ive spotted a bit of an error.

During the time when I tried to make LR HD/Engine 2, I noticed some stuff.

[this being said in a nut shell] In order to make it run the same speed at 60 FPS, I had to change a few numbers. This meant different physics. So basically there was two trade offs...
1) Same physics, slightly faster speed
2) Normal speed, new physics.

Mhenr, you saying that this runs at 60 fps, does this mean one of the previous said situations, or is this only for testing?

This is a different programming language so some errors from another probably don't appear in other languages.

[mhenr18]

it's multithreaded so the game logic isn't tied to the rendering speed

[14mRh4X0r]

I think I want to give the C version a title. Line Rider: Unleashed. Why? Because I've finally unleashed your machine and let it ride the lines like never before. Also it sounds cool

Thoughts?

Line Rider++

Up for a linux port? :|

I think that isn't necessary because Linux is designed to run win32 programs.

No.

it's multithreaded so the game logic isn't tied to the rendering speed

[[senpai] kevans]

I think I want to give the C version a title. Line Rider: Unleashed. Why? Because I've finally unleashed your machine and let it ride the lines like never before. Also it sounds cool

Thoughts?

Line Rider++

Up for a linux port? :|

I think that isn't necessary because Linux is designed to run win32 programs.

No.

it's multithreaded so the game logic isn't tied to the rendering speed

lolwut?

[14mRh4X0r]

Linux is definately not designed to run win32 programs. It's even more likely that a mac program runs on linux than that a win32 program runs on it (without compatibility layer)

Also, @mhenr: I'm for GTK myself, but you could consider using OpenGL.

[mhenr18]

Linux is definately not designed to run win32 programs. It's even more likely that a mac program runs on linux than that a win32 program runs on it (without compatibility layer)

Also, @mhenr: I'm for GTK myself, but you could consider using OpenGL.

The whole engine uses OpenGL, but I need a GUI framework to get the OpenGL context to render into, get mouse/keyboard events from the OS, show OS dialogs, that sort of thing. I'll probably go with GTK.

[14mRh4X0r]

Heh, already thought so, just had to mention it.

[mhenr18]

Right, I've done as much render optimizing as I can be bothered to do for now. I still need to implement a dirty rect system so that when you add new lines it doesn't need to recache everything and just recaches modified render tiles. Anyway, it's still lightning fast, although you might get a jitter or two when panning around if you're working with massive line counts. I'll explain the whole system later once I finalise it. Also, lines that get drawn anywhere outside the bottom left quadrant (anywhere left or above where the lines get added by the add 10k button) aren't rendered right now because although the grid is working fine, I haven't bothered to rewrite the grid access functions to support all four quadrants.

Mac: http://dl.dropbox.com/u/49905412/Line%20Rider%20Unleashed_Mac_0.05.zip

Windows: http://dl.dropbox.com/u/49905412/Line%20Rider%20Unleashed_win32_0.05.zip

edit: oh yeah, there's two bugs I already know about. One is a random crash bug, it's due to a memory error that I'm still trying to debug, the other is that sometimes the color of the line isn't rendered. I'll fix 'em soon

[Helios Pavonine]

I click the New track button, nothing's happening =/

[14mRh4X0r]

Same for me, but I'm running under wine, so that could be my issue

[[senpai] kevans]

Works for me...

Okay... so you get line tool to work, but not pencil? And it seems that lines are drawn upside down, as in when drawn left to right, it shows up as left to right.

And could you worry about making the mouse change to said tool before making it work. it's a little bothersome that I can't tell if it switched tools or not.

also, you need to make the black side further from the blue side.

[Conundrumer]

Hang on.... I think Ive spotted a bit of an error.

During the time when I tried to make LR HD/Engine 2, I noticed some stuff.

[this being said in a nut shell] In order to make it run the same speed at 60 FPS, I had to change a few numbers. This meant different physics. So basically there was two trade offs...
1) Same physics, slightly faster speed
2) Normal speed, new physics.

Mhenr, you saying that this runs at 60 fps, does this mean one of the previous said situations, or is this only for testing?

The physics don't exist yet. When they do, it's gonna be different because it's unlikely he'll be using the same exact code as fsk's and floating point errors may be different.

Also, he's worrying about performance and rendering, not the gui. It's kinda irrelevant to bring up issues with the gui.

[mhenr18]

Works for me...

Okay... so you get line tool to work, but not pencil? And it seems that lines are drawn upside down, as in when drawn left to right, it shows up as left to right.

And could you worry about making the mouse change to said tool before making it work. it's a little bothersome that I can't tell if it switched tools or not.

also, you need to make the black side further from the blue side.

It's early stages dude, right now I'm not caring about the interface or making the compositing as accurate as possible. I'm just caring about speed.

[mhenr18]

Thought I'd post something of an update, because I'm going on a road trip tomorrow morning and might not be quite as active for the next few days.

Simulation's working reasonably well - I've yet to fully implement line snapping. It's pretty nice to have simulation running with a few million lines. And yes, it's the normal 40 ticks/second for the physics engine, there's no change in speed or anything - it feels identical to beta 2. Yay for multithreading.
I've made considerable progress on render performance and resource use - I've now got it to behave a whole lot smarter in terms of choosing where to render new tiles. My next step is having the renderer use the textures for bosh and the sled so you see more than just some dots.
Lines render perfectly in the editor now - I totally rewrote fsk's original code for that so now it's bulletproof - the small bugs you used to see in the rendering in 6.2 are gone.
I've made quite a bit of UI progress too, menus and checkboxes now work.
I need to fix up a bug in my grid insertion code, which should then fix up a few other things that are broken.
Once I make all the fixes that I need to and get simulation going flawlessly, my next goal will be saving/loading and then the eraser.

[Blesshiscottonsocks]

Hell yeah!

Say, now we have a somewhat laggles system, would you be able to implement music importing for track syncing :3

[[senpai] kevans]

Hell yeah!

Say, now we have a somewhat laggles system, would you be able to implement music importing for track syncing :3

That sounds easy. Maybe it can run like unbound did? Simple drag and drop music into folder, on/off setting for play music.

[rabid squirrel]

that's ridiculous. This computer is 16 months old.

[TheRevTastic]

that's ridiculous. This computer is 16 months old.

He probably hasn't added backwards capability for Mac OSX yet, or since you're a mac user, upgrade to Lion .

[Sponsored content]