cocos3d 0.7.2 released « cocos2d for iPhone

cocos2d for iPhone » Programming » cocos3d

[sticky]

cocos3d 0.7.2 released

(36 posts) (14 voices)

Started 6 months ago by Bill Hollings
Latest reply from karan

Tags:

cocos3d

12 Next »

Bill Hollings
Moderator
cocos3d 0.7.2 has been released!

This release adds heterogeneous 3D mesh particles, enhanced UIViewController integration, ray-casting enhancements, simplified parametric vertex array allocation and management, performance and memory usage improvements, enhanced logging, and detailed GL error tracing.

Features added in this release include:
- Added mesh particles as a type of particle system.
  
  Particles can now be constructed from any template mesh, (sphere's, boxes, planes, POD models, etc).
  
  A single emitter can support particles constructed from different template meshes.
  
  Mesh particles can individually move, rotate and scale in three dimensions.
  
  Particles can be added manually to an emitter, effectively creating a generic mesh batching system.
  
  All mesh particle vertices are manipulated in main memory and submitted to the GL engine in a single GL call.
- Improved integration with UIView and UIViewController:
  
  New CC3UIViewController class supports auto-rotation of the 3D/2D scene to the device orientation using standard UIKit auto-rotation.
  
  Both iOS6 and pre-iOS6 rotation mechanisms are supported.
  
  The CC3UIViewController loadView method now creates an appropriate CC3EAGLView, removing the need to create the view outside the controller in the AppDelegate.
- Added the ability to determine the individual mesh faces, and the exact mesh location, intersected by a ray (for example from a touch).
- Added the vertexContentTypes property to CC3MeshNode & CC3Mesh to simplify the creation of vertex arrays within a mesh. Parametric meshes (spheres, cones boxes, planes, etc.) can now be created with any type of vertex content.
- Added several new parametric mesh population methods, including parametric cones and invisible touch-boxes.
- Added support for bitmapped text labels as a 3D mesh.
- Added additional camera movement and framing methods.
- Added a build setting to provide the ability to trace GL errors to the exact GL call that triggered the error.
- Automatic handling of textures with pre-multiplied alpha channels.
- Memory and performance improvements including the use of minimal matrices, removal of many redundant GL calls, and the use of bitfields for most BOOLs.
In addition to these main features, this release includes a number of fixes and adjustments based on user feedback. For more complete and detailed information on what's new in this release, we encourage you to read the CHANGELOG document in thecocos3d distribution.

...Bill
Posted 6 months ago #
Aaqib20
Member

Wow, great work Bill.. Thanks alot.
Anyway when is cocos3D going to have support for other 3D formats such as .3ds?

Keep up the great work.
Thanks
Aaqib

Posted 6 months ago #
Eternity
Member

Great, Bill!

Posted 6 months ago #
chakie
Member

Ooh, nice feature list! Does this version work with Cocos2D 2.x or is it still only for 1.x? I have some own 3D stuff that I've so far done in CCNode subclasses, but I would like to migrate it to Cocos3D and be able to use some features that are quite hard to do in plain C2D, such as view frustum culling.

Posted 6 months ago #
riq
Key Master

great!

Posted 6 months ago #
Bill Hollings
Moderator

@chakie

cocos3d is still based on cocos2d 1.x.

Migration to cocos2d 2.x and OpenGL ES 2.0 is planned for the spring.

...Bill

Posted 6 months ago #
Rogs
Member

Nice work Bill! Gonna check this out!

Posted 6 months ago #
pasi
Member

How about MacOS support?

Posted 6 months ago #
cocojoe
Moderator
Sounds good, I have not tried cocos3d however I like the sound that it is implemented as a stand alone viewcontroller 'CC3UIViewController' as I have a UIKit based concept project and would love to be able to drop in a 3D Controller to display an inventory item as a 3D Model.

EDIT:
@bill-hollings your installer did not work for me out of the box, I specified the cocos2d directory relative to the 'cocos3d 0.7.2' folder as shown in the example
```
./install-cocos3d.sh -f -2 "../../cocos2d/cocos2d-iphone-1.1"
```
However the sym links created inside the 'cocos3d 0.7.2/cocos2d' folder are missing an extra '../' (may only effect the demo project?)

When I try and create a 'cocos3d/cocos3d application' project the next step 'choose options' is blank, I am using xcode 4.5.1, the install script didn't report any errors.
Posted 6 months ago #
ayt
Member

Great to see this.
By the way, I'm totally okay with the fact that cocos3d is still using cocos2d 1.x. I'm just using it for the menus, buttons and numbers(e.g. score).

Posted 6 months ago #
Bill Hollings
Moderator

@cocojoe

Strange. Try running the installer with an absolute path to the cocos2d libraries instead. I'll look into whether relative paths are an issue.

I have heard others encounter the template options issue you describe, but I have never seen it myself. I am using Xcode 4.5.2-GM-seed (which is now released as simply 4.5.2).

...Bill

Posted 6 months ago #
Aaqib20
Member

Hi Bill, im getting errors when building/running cocos3d 0.7.2?

error: Apple LLVM Compiler 4.1 Error

Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1

Any idea what is wrong? Im able to run cocos3D 0.7.1 perfectly fine but the latest version 0.7.2 is giving me errors so Im unable to run it?

EDIT: Also, director.runLoopCommon = YES; // gives me an error too. Iv tried to reinstalling it.. but the same problems. When I comment this line, i get the "Apple LLVM... Error".

Thanks
Aaqib

Posted 6 months ago #
joat
Member

Bill, I noticed the new DemoMashup is using a different earth texture map. It is using earthmap1k.jpg rather than Earth_1024.jpg. earthmap1k.jpg size is 1000x500, not a power of two. Was this intentional?

Posted 6 months ago #
Aaqib20
Member

Can anyone else get this build working? Im getting a compiler error? Any ideas?..

Posted 6 months ago #
pasi
Member

Yes, it seems to work ok. Just make sure you've installed the latest Cocos2d 1.x, then Cocos3D. I used absolute path with the latter, if it affects anything.

@Aaqib20, that "Command /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang failed with exit code 1" doesn't really tell us anything. There should be some rows before or after that, that could reveal the cause, like some file is missing or something.

Posted 6 months ago #
Aaqib20
Member

Got it working! :). I had to install the latest Cocos2d 1.1 since I had the beta version of Cocos2D 1.1 installed -> so it gave me the Compiler error.

Thanks for the help anyway @pasi.

Aaqib

Posted 6 months ago #
Zuby
Member

Hi.. I want to thank you for outstanding job you do. Unfortunately new version is full of memory leaks :/ This is simple scene with some POD models, one camera, one light. http://www.q3.cz/images/40Screen_Shot_2012_11_17.png

Btw remove this line [context_ renderbufferStorage:GL_RENDERBUFFER_OES fromDrawable:eaglLayer]; from CC3EAGLView it couses OpenGL error 0x0502 in -[CCConfiguration init]

Posted 6 months ago #
Tenorm
Member

Hi,

thanks for the update. I get the following error in CC3UIViewController.h (maybe it could be solved by adding/removing compiling options?):

Property 'view' type does not match super class 'UIViewController' property type

This sounds logic because UIViewController got a property

UIView* view

and cocos wants to overwrite the view property

EAGLView *view

Anyone know how to solve this?

Posted 6 months ago #
cocojoe
Moderator

@Tenorm CC3UIViewController works for me, what are you actually doing with it?

Posted 6 months ago #
Tenorm
Member

@cocojoe: I did not change code, just pasted the new cocos3d-release.

The error description is that the UIViewController already has a property variable called "view" (type UIView*) and that's right. And cocos tries to change the variable type of "view" from UIView* (declared in UIViewController, super class of CC3UIViewController) to EAGLView* (which is sub class of UIView). And this step, I don't know why, is what my compiler doesn't like.

So I think that this is just an error caused by my compiler setting, not cocos' fault.

Posted 6 months ago #
Tenorm
Member

As I thought, it was really the compiler's failure: Switching from LLVM 4.2 to LLVM 4.1 solved all errors..

Posted 6 months ago #
Bill Hollings
Moderator

@Zuby

When running the hello, world template app, or the CC3DemoMashUp demo app, I am unable to replicate your issues.

I see no leaks when running either the hello, world template app, or the CC3DemoMashUp demo app, even after repeatedly invading and removing the robot invaders, and repeatedly adding and removing shadow volumes.

And I don't see any GL errors logged by CCConfiguration, or by cocos3d.

Can you clarify what versions of everything (CC3, CC2, Xcode) you are using, and perhaps list a bit of your app code, so we can see how you are managing your scene.

...Bill

Posted 6 months ago #
Bill Hollings
Moderator

@Tenorm

Thanks for doing the detective work.

Did you mean GCC 4.2?

Or are you really finding that a newer version of LLVM (I'm on LLVM 4.1 from Xcode 4.5.2-GMSeed) is causing those subclassing errors?

If the former, yes, I'm not really validating against GCC anymore.

If the latter, what version of Xcode are you using to get LLVM 4.2?

...Bill

Posted 6 months ago #
Bill Hollings
Moderator

@joat

Yep. Intentional. It's prettier. :^)

It is an NPOT. They are quite usable in cocos3d.

Are you encountering an NPOT issue?

...Bill

Posted 6 months ago #
Zuby
Member

@Bill Hollings

Thanks for answer :]

All latest version CC3D 0.7.2 CC2D v1.1 RC0 Xcode 4.5.2.

I don't have problem with leaks during scene live either, but try to create one scene and destroy everything by replacing CC2D scene. (Game > Menu.. same code works with 0.7.1 with no leaks at all).

About GL error.. look at the latest ES1Renderer from cocos2d and specially this comment "// Create default framebuffer object. The backing will be allocated for the current layer in -resizeFromLayer". This has been changed couple of cc2d version before, so if you don't get any err, then you probably use older version of cc2d.

Posted 6 months ago #
Bill Hollings
Moderator

@Zuby

Hmm...I'm using the most recent cocos2d 1.1 RC0, and as I say, I don't see any GL errors being logged.

Are you using CC3EAGLView (which uses CC3ES1Renderer)?

Can you package up a simple example of the leaks and GL errors into a project and email it to support@brenwill.com, so I can have a look at it?

...Bill

Posted 6 months ago #
mmarks
Member

@Bill

I believe the problem with the install script is the final '/' character. The README leaves it out, but I believe it's required

./install-cocos3d.sh -f -2 "../../cocos2d/cocos2d-iphone-1.1" <BAD>

./install-cocos3d.sh -f -2 "../../cocos2d/cocos2d-iphone-1.1/" <GOOD>

Posted 5 months ago #
Bill Hollings
Moderator

@mmarks

Thanks for your research and input.

I believe that there actually is also a problem (as highlighted above) in the levels of relative indirection (../..cocos2d...) when using relative directories.

I've fixed it for future releases, but in the meantime, I recommend using an absolute reference for the cocos2d directory when running the cocos3d install script.

...Bill

Posted 5 months ago #
Tenorm
Member

@Bill: I'm using Xcode 4.5 (released, no rc) and switching from "LLVM GCC 4.2" to "Apple LLVM Compiler 4.1" solved the compiler errors for me

Posted 5 months ago #
Tenorm
Member

BTW: Was there a change (or bug) in textureRectangle-property? I get some really strange offset and scaling bugs (according to older cocos3d release) if I set non-quadratic rectangles, e.g. CGRectMake(0, 0, 0.7f, 1.3f). This worked before updating.

Posted 5 months ago #

RSS feed for this topic

12 Next »

Reply »

You must log in to post.