A fast, easy to use, free, and community supported 2D game engine
Agito
Member
hello! I tried installing the 3D template and test the Hello World sample.
works out fine with Debug mode
But kept on receiving "error: no 'EPVRTError CPVRTBackground::Draw(GLuint)' member function declared in class 'CPVRTBackground'" on Release mode
+ 3 other errors
Sorry...nothing like that yet. Batching is different with full 3D models, since each one can be moved separately, they generally require their own transforms, and so multiple nodes can't be drawn in one GL call. We may be able to do something once skinning is introduced, but for now, each node is drawn separately.
Some suggestions to help improve GL performance:
createGLBuffers method to load data into VBO's. Invoke this method on your CC3World instance once all your duplicates are added, or invoke it on each duplicate separately.CC3NodeSequencers to optimize drawing order to suit the models in your application. The goal is to minimize state changes, for example, by sorting by your meshes, or by your textures, etc.Finally, we'll be doing some performance improvements in the next couple of releases. If anyone has any good suggestions for potentially speeding up cocos3d performance, please speak up!
Thanks...
...Bill
Komododave
Member
@Bill
I have discovered a bug - use of antialiasing on the EAGLView seems to break node picking.
I had set isTouchEnabled to YES for some spherical nodes, with interaction code running upon touching these, via [CC3World nodeSelected:byTouchEvent:at:]. I made a few code changes only to discover about a day later the interaction had broken, and the 'node' property of the aforementioned method being nil. I spent a couple of hours trying to figure out which change had caused it.. ultimately identifying it was the anti-aliasing.
The following EAGLView instantiation works fine with picking:
EAGLView *glView = [EAGLView viewWithFrame: [window bounds]
pixelFormat: kEAGLColorFormatRGBA8
depthFormat: GL_DEPTH_COMPONENT16_OES];Whereas this version breaks it:
EAGLView *glView = [EAGLView viewWithFrame: [window bounds]
pixelFormat: kEAGLColorFormatRGBA8
depthFormat: GL_DEPTH_COMPONENT16_OES
preserveBackbuffer:NO sharegroup:nil multiSampling:YES numberOfSamples:4];Presumably this is due to the picking implementation being a colour-based workaround?
I'd be interested to hear if you fix this, as I'd like to use AA in my 3d app.
Many thanks for cocos3d, it's been a huge timesaver!
chakie
Member
Hi,
Cocos3D looks very interesting. Having played with 3D in various frameworks along the years I've been looking for something that would allow me to finally try out some of the ideas I have. Doing raw OpenGL is too low level for an old fart like me. :)
It would seem that getting a basic textured height map up and running would not take too much effort and that is very encouraging. The first thing to do in any new framework is to get some small scale terrain rendered. Fun, fun!
Node selection when using multi-sampling antialiasing of 3D objects is included in cocos3d 0.6.0-sp, which has just been released.
...Bill
Jasperblues
Member
Hi - just started with Cocos3d yesterday. I created a model in Blender, did the Collada2POD dance and got it spinning around on my ipod. Now I want to apply a texture image. Can someone point me in the right direction.
If I add a texture in Blender (2.5 - which I have no idea how to use), will it get included/referenced in the final POD file?
How can I programmatically apply a texture?
n00b.
Ben Roberts
Member
@Jasper - fix for the fps drop on backgrounding issue here : http://www.cocos2d-iphone.org/forum/topic/18436
mkotliarov
Member
Why in CC3MeshNode
-(void) populateAsRectangleWithSize: (CGSize) rectSize
andPivot: (CGPoint) pivot
withTexture: (CC3Texture*) texture
invertTexture: (BOOL) shouldInvert
calls:
[self populateAsRectangleWithSize: rectSize
andPivot: ccp(rectSize.width / 2.0, rectSize.height / 2.0) <----
andTessellation: ccg(1, 1)
withTexture: texture
invertTexture: shouldInvert];
instead of:
[self populateAsRectangleWithSize: rectSize
andPivot: pivot <--------
andTessellation: ccg(1, 1)
withTexture: texture
invertTexture: shouldInvert];
Thanks.
It's a bug.
It's been fixed for the next release...but in the meantime, please make the correction that you indicate.
Thanks...
...Bill
mkotliarov
Member
Thanks Bill for answer my question. Now I have a new problem. I want to record a node selection by swipe gesture like in CC3DemoMashUp, but in my case the first touch not necessarily need to be inside the node. I need to record a kCCTouchMoved and i do the following:
-(void) touchEvent: (uint) touchType at: (CGPoint) touchPoint
{
if (touchType == kCCTouchBegan) {
NSLog(@"Began");
}
if (touchType == kCCTouchMoved) {
NSLog(@"Moved");
[touchedNodePicker pickNodeFromTouchEvent:touchType at:touchPoint];
}
if (touchType == kCCTouchEnded) {
NSLog(@"Ended");
}
}
and
-(void) nodeSelected: (CC3Node*) aNode byTouchEvent: (uint) touchType at: (CGPoint) touchPoint {
NSLog(@"%@", aNode);
}
When i make slow swip gestures the console result is:
2011-09-23 11:56:33.940 [1334:207] Began
2011-09-23 11:56:34.707 [1334:207] Moved
2011-09-23 11:56:34.785 [1334:207] (null)
2011-09-23 11:56:38.613 [1334:207] Moved
2011-09-23 11:56:38.668 [1334:207] CC3PODMeshNode corn_plant_lower07-62
2011-09-23 11:56:39.321 [1334:207] Moved
2011-09-23 11:56:39.418 [1334:207] (null)
2011-09-23 11:56:42.190 [1334:207] Ended
But for fast movement:
2011-09-23 11:59:40.324 [1334:207] Began
2011-09-23 11:59:40.846 [1334:207] Moved
2011-09-23 11:59:40.889 [1334:207] Moved
2011-09-23 11:59:40.902 [1334:207] (null)
2011-09-23 11:59:40.943 [1334:207] Moved
2011-09-23 11:59:40.950 [1334:207] Moved
2011-09-23 11:59:40.955 [1334:207] Moved
2011-09-23 11:59:41.000 [1334:207] Moved
2011-09-23 11:59:41.002 [1334:207] (null)
2011-09-23 11:59:41.047 [1334:207] Moved
2011-09-23 11:59:41.115 [1334:207] Moved
2011-09-23 11:59:41.119 [1334:207] (null)
2011-09-23 11:59:43.456 [1334:207] Ended
like missing picked nodes.
I'm using cocos3d 0.6.1 and read the documentation and tells that -(void) pickTouchedNode picks the node during drawing operations and dispatchPickedNode is invoked during update operations. Also tells that:
"For rapid finger movements, it is quite likely that more than one touch event could arrive before the next rendering pass picks a 3D node. For this reason, no attempt is made to find the node for each and every touch location. In addition, the touch type is only added to the queue if it is different than the previous touch type."
IS there any way to issue my problem. I'm making a mistake? Thanks.
hi i am trying to load some load 3d model which will be a musium i am testing with this object (can be download from "http://e2-productions.com/repository/modules/PDdownloads/singlefile.php?cid=24&lid=389")
but it looks it is having problem with face of the object
akbar
Member
Hi. I`m new in cocos3d. Is exist any way to create solid sphere in cocos3d?
I'm trying to release 3d version of the game lines. (http://www.freegames.ws/games/free_online_games/lines_game/lines_game.htm)
Thanks.
The events are handled asynchronously, because they can arrive at any time. Node picking must happen during the drawing loop, because it uses a color-picking algorithm.
It's best not to use touch-move events for node selection.
You do not need to have a node selected to handle the move events. For example...the following code will handle move events for detecting swipes without ever selecting a node. In this example, the final touch-ended event when the user lifts their finger will select the node for whatever reason you want:
-(void) touchEvent: (uint) touchType at: (CGPoint) touchPoint {
switch (touchType) {
case kCCTouchBegan:
break;
case kCCTouchMoved:
[self handleSwipe: touchPoint];
break;
case kCCTouchEnded:
[touchedNodePicker pickNodeFromTouchEvent: touchType at: touchPoint];
break;
default:
break;
}
// For all event types, remember where the touchpoint was, for subsequent events.
lastTouchEventPoint = touchPoint;
}
If you do want the node selected first, handle node selection in kCCTouchBegan and then track it for swipes using kCCTouchMoved. That's how the die cube is spun under touch control in the CC3DemoMashUp demo.
...Bill
cocos3d does not contain a parametric sphere yet. I'd be happy if someone wants to grind one out and contribute it. :-)
There are some algorithms for creating sphere meshes available in 3D math books, or through a web search.
You can get an understanding about how meshes are programmatically constructed using CC3VertexArrays by looking at the source code for the populateAs... family of methods of CC3MeshNode.
...Bill
Malkavian
Member
Hello everyone o/
I didn't know where to post first, so picked this general sticky thread.
I started programming in Obj-C (had a Java/Scala background mostly) relatively recently, and am already involved in making of a game here at my work. 3D included, ofc.
So, after implementing server-side logic and all sorta things, I had to make a pick and decide on a 3D engine.
My first pick was iSGL3D (since stack overflow provided me with it firsthand). It was kind of an introduction to 3D programming in general for me. Then I began to learn cocos2d (just for myself, really, no work involved) and stumbled upon cocos3d. And, well, here I am =)
I am really excited about using cocos3d - which will begin the day after tomorrow, to be honest.
Thanks the development team for making it.
wildwinter
Member
Can anyone think of a reason why applying a texture to a shape would stop dynamic lighting working? i.e. a plain, simply convex poly which shades correctly as it spins has a textured material applied, and suddenly the lighting is acting as if it's baked on - the model has lighter/darker sides but they're fixed with respect to the model as it spins, looking baked on to the model.
Application of texture:
mesh.material=[CC3Material material];
CC3Texture* tex= [CC3Texture textureFromFile:@"test.png"];
[mesh.material addTexture:tex];
It's not bump-mapped or anything, shouldUseLighting is true, the PNG is a simple 512x512 texture with no alpha. I have had lighting on textures working properly in this project, but after a bit of reorganising it seems to have stopped and I can't figure out why.
The light isn't moving with the model.
Multiple models suffer from the same problem.
I'm vaguely wondering whether I'm missing a retain somewhere, or I'm sharing a material that I shouldn't... not sure.
I've tried this with parametric models, and with models imported via Blender / Collada2POD. I'm obviously hitting some sort of config/boundary condition somewhere, just not sure where to look!
Gray Olson
Member
I don't know what to tell you, but if it's just a test and not too much code, I'd recommend just creating a new project and re-writing the code to see if that fixes it... it's happened to me before when I'm just getting used to new code API's and whatnot and like you said screw up a retain or something like that somewhere.
Gray
wildwinter
Member
Okay... found a workaround for my problem.
I was loading my models from Blender, as a resource file. Then copying the relevant nodes from the resource file, adding them to the world, and the lighting was broken for textured objects.
If, before copying the relevant nodes, you _add_ the resource file contents to the world (but hide them offscreen somewhere) it all works fine.
Weird! My suspicion is that because I wasn't adding the source nodes to the world, a bunch of materials etc. weren't properly available to the world or something, but I don't really know what's going on under Cocos3D's hood in terms of resource handling. Still, that solves my problem, although it doesn't seem ideal in the long run!
Cheers,
Ian
With
-(void) nodeSelected: (CC3Node*) aNode byTouchEvent: (uint) touchType at: (CGPoint) touchPoint {
Sometimes my aNode is coming back as Nil,
I have put into play a fix that was in this post and it seems to fix the issue.
I change
EAGLView *glView = [CC3EAGLView viewWithFrame: [window bounds]
pixelFormat: kEAGLColorFormatRGBA8
depthFormat: GL_DEPTH_COMPONENT16_OES
preserveBackbuffer: NO
sharegroup: nil
multiSampling: NO
numberOfSamples: 4];
To
EAGLView *glView = [CC3EAGLView viewWithFrame: [window bounds]
pixelFormat: kEAGLColorFormatRGBA8
depthFormat: GL_DEPTH_COMPONENT16_OES];
Is this meant to be fixed?
Thanks
Duncan.
Ok, on more investigation, the above didn't fix the issue, it possibly made it happen less.
While going through the stack I noticed that when the node was bill
in the method that was calling it
seemed that
[world nodeSelected: pickedNode.touchableNode byTouchEvent: touchQueue[i] at: touchPoint];
touchableNode would be nil
but pickedNode wouldn't so I have changed it to
[world nodeSelected: pickedNode byTouchEvent: touchQueue[i] at: touchPoint];
as a temporary fix.
I'm sure this will no doubt break something else
You must log in to post.
