So, I've decided to upgrade my iOS engine from OpenGL ES 1.1 to 2.0. What does this mean? No more fixed function pipeline! I have to write shaders for everything!
So I did.
First cube is Position-Color vertex.Second cube is Position-Color-TextureThose two are sort of boring. You've seen them before. Third cube is better. Its a Position-Color-Texture-TextureID cube - along with the x/y texture coordinates, I also send in the texture ID. For the cube in question, halfway through the cube it switches textures, so you have some faces with one texture, some with another, and some faces that start as one texture and suddenly change to the other.Finally, the utterly epic green-bullseye glow in the dark blended-texture cube. Rather than render one cube, and then another on top of it with the glowy texture, I just do it in one pass.Woo!Next up I'm going to do lighting, then per-pixel lighting, and then bumpmapping!
All I can think of is "How did you take screenshots of your phone?"
Or that… and how I love the third cube <3Photoshop/Gimp, FTW.
That's what the iPhone emulator in XCode looks like, actually.
that's awesome.
How does the emulator handle the hardware-emulation? I mean, the computer is obviously much more capable than an iPhone. Does it try to emulate the CPU/GPU of the iPhone?
Mordi, unfortunately, it doesn' - the emulator runs things in almost exactly the same manner as a device, but the GPU/CPU are on steroids. It is very good emulation, aside from that. On the other hand, it's better than the Android emulator which in my experience ran slower than on device.
Aside from that, I do know the performance specifications of the iOS hardware, and it has more than enough oomph for what I plan.I wonder what Minecraft would look like if all of the blocks had the Position-Color vertex shader cube as their texture.