Thanks for all the feedback. I now know that the FPS is pretty much CPU-independent, so I'll try to find the bottleneck in my coding.
Also, pre_02 is out. There are a few small changes:
- The console window now asks you to input the render distance (in chunks)
- The FPS can be seen at the window title bar.
If you don't have a 1920*1080 screen, it is possible that the application will not display correctly. I'll fix that.
Also, I know I am violating my own rules here by actually releasing the program, mainly because I didn't expect to get so much reactions and support. Thanks everybody, you guys are awesome :biggrin.gif:
Thanks for all the feedback. I now know that the FPS is pretty much CPU-independent, so I'll try to find the bottleneck in my coding.
Also, pre_02 is out. There are a few small changes:
- The console window now asks you to input the render distance (in chunks)
- The FPS can be seen at the window title bar.
If you don't have a 1920*1080 screen, it is possible that the application will not display correctly. I'll fix that.
Also, I know I am violating my own rules here by actually releasing the program, mainly because I didn't expect to get so much reactions and support. Thanks everybody, you guys are awesome :biggrin.gif:
What made you decide to get a 6970 with an athlon?
Because I love making people ask questions.
Well part of it was my own stupidity.
Prior to this I had a Single core celeron and a 8600gt as you know my 8600gt died.
Well I had another lowend graphics card sitting around I used it for a while.
Well the rumors at the time is we were to see bulldozer release in 3 months.
I saw my current GPU at a really good price so I pushed it then figured in 2 months ill buy a bulldozer cpu and have a nice highend gaming rig.
Then I figured well crap my 6970 is going to be brutally bottlenecked by a singlecore. Bulldozer was set to release on the AM3 socket at the time so I figured I will get an AM3 motherboard and just wait 2 months and get a Bulldozer and be able to drop it in.
Well bulldozer ended up taking another year and a half to release. Then I spent some money on a droidx instead of a new cpu then I spent my money on a Gnex instead of a new cpu. Now I am waiting for IvyBridge or preferably PileDriver.
Well part of it was my own stupidity.
Prior to this I had a Single core celeron and a 8600gt as you know my 8600gt died.
Well I had another lowend graphics card sitting around I used it for a while.
Well the rumors at the time is we were to see bulldozer release in 3 months.
I saw my current GPU at a really good price so I pushed it then figured in 2 months ill buy a bulldozer cpu and have a nice highend gaming rig.
Then I figured well crap my 6970 is going to be brutally bottlenecked by a singlecore. Bulldozer was set to release on the AM3 socket at the time so I figured I will get an AM3 motherboard and just wait 2 months and get a Bulldozer and be able to drop it in.
Well bulldozer ended up taking another year and a half to release. Then I spent some money on a droidx instead of a new cpu then I spent my money on a Gnex instead of a new cpu. Now I am waiting for IvyBridge or preferably PileDriver.
Oh ok. You guessed what would happen with technology 1.5 years later? That's bold. But I too am hoping for piledriver to be on am3+ and be not a failure, otherwise I will be stuck way out of date.
Oh ok. You guessed what would happen with technology 1.5 years later? That's bold. But I too am hoping for piledriver to be on am3+ and be not a failure, otherwise I will be stuck way out of date.
Well at the time Bulldozer was expected to be a few months away not years.
1-dimensional linearly-interpolated perlin noise is a success. I'll see if I can make it 2-dimensional with bicubic interpolation. But that's a thing for tomorrow, I'm tired right now.
This perlin noise engine took me three whole days of non-stop coding + removing my code again before I actually got it to work. And it feels awesome.
The grass & dirt overlay algorithm had to be temporarily disabled for compatibility issues. I will re-enable it later. So now, here's a screenshot of randomly generated terrain:
Oh, and for the record, it took me three days to come up with this piece of code:
for (int i = 0; i < 16; i++) {
for (int j = 0; j < hMax; j++) {
for (int k = 0; k < 16; k++) {
double var = cosineInterpolate(
cosineInterpolate(aData[0][0], aData[0][15], (double) i / 16),
cosineInterpolate(aData[15][0], aData[15][15], (double) i / 16),
(double) k / 16);
if (j < var) {
blockData[k][j][i] = 1;
}
if(j == 0){
blockData[k][j][i] = 1;
}
}
}
}
Phenom II x4 955 BE 3.2 Ghz
4Gb RAM
MSI GeForce gt520
Also, pre_02 is out. There are a few small changes:
- The console window now asks you to input the render distance (in chunks)
- The FPS can be seen at the window title bar.
If you don't have a 1920*1080 screen, it is possible that the application will not display correctly. I'll fix that.
Also, I know I am violating my own rules here by actually releasing the program, mainly because I didn't expect to get so much reactions and support. Thanks everybody, you guys are awesome :biggrin.gif:
Pre_02 download
With render distance set to 1 it runs perfectly. 60 FPS.
With it set to 5 however, it's really laggy, 7 FPS
AMD athlon x4 3.0 Ghz
AMD radeon HD 6770.
4GB ram.
Can run minecraft on max no problem.
With the render distance added by 1, i noticed a 10-20 FPS decrease. It's definitely a CPU user when i checked task manager, 100% CPU. 1440x900.
Okay, thanks for the feedback. Did you experience any problems with the window size?
It went off the screen, but not by too far, both ways.
Nothing that makes it unbearable.
Here's a pic of what it looks like if you care:
In the pic you can see that the sides are hardly off the borders of the screen while the bottom border is off the screen.
Ah yes, I see. The window is probably resized automatically to the max width & height if it's bigger than the sceen size.
What made you decide to get a 6970 with an athlon?
i5 6600k 4.6ghz / MSI 280X / 8Gb 2666 DDR4 / Gigabyte Z170X-UD5 / TX550M / 500Gb 850 EVO / NZXT S340 / Corsair K65 / Corsair M60
Because I love making people ask questions.
Well part of it was my own stupidity.
Prior to this I had a Single core celeron and a 8600gt as you know my 8600gt died.
Well I had another lowend graphics card sitting around I used it for a while.
Well the rumors at the time is we were to see bulldozer release in 3 months.
I saw my current GPU at a really good price so I pushed it then figured in 2 months ill buy a bulldozer cpu and have a nice highend gaming rig.
Then I figured well crap my 6970 is going to be brutally bottlenecked by a singlecore. Bulldozer was set to release on the AM3 socket at the time so I figured I will get an AM3 motherboard and just wait 2 months and get a Bulldozer and be able to drop it in.
Well bulldozer ended up taking another year and a half to release. Then I spent some money on a droidx instead of a new cpu then I spent my money on a Gnex instead of a new cpu. Now I am waiting for IvyBridge or preferably PileDriver.
Oh ok. You guessed what would happen with technology 1.5 years later? That's bold. But I too am hoping for piledriver to be on am3+ and be not a failure, otherwise I will be stuck way out of date.
i5 6600k 4.6ghz / MSI 280X / 8Gb 2666 DDR4 / Gigabyte Z170X-UD5 / TX550M / 500Gb 850 EVO / NZXT S340 / Corsair K65 / Corsair M60
Well at the time Bulldozer was expected to be a few months away not years.
Oh ok.
i5 6600k 4.6ghz / MSI 280X / 8Gb 2666 DDR4 / Gigabyte Z170X-UD5 / TX550M / 500Gb 850 EVO / NZXT S340 / Corsair K65 / Corsair M60
i7-2600k
MSI GTX 580 Lightning Xtreme Edition 3GB - Factory and self overclocked
8GB RAM 1600mhz
When I benchmark with FRAPS I get around 15 fps.
If you open the Terminal, and navigate to the directory of swiss_cheese.jar, you should be able to run it as
Or you could create a shell script for it. Something like this should work.
This script doesn't have to be placed in the same folder as the application.
Also visit my youtube please! Youtube.com/legitzdestroy
The FPS is working fine for me. It probably has something to do with Linux registering the system time differently.
The grass & dirt overlay algorithm had to be temporarily disabled for compatibility issues. I will re-enable it later. So now, here's a screenshot of randomly generated terrain:
Oh, and for the record, it took me three days to come up with this piece of code:
I'll upload a new prerelease in a minute.