Is Anyone who use NxOgre1.021 without any problem? Come in

I cannot even create a actor with my mesh,and a lot of other problems which really confused me so much

I cannot even create a actor with my mesh,and a lot of other problems which really confused me so much
mBall = mScene->createBody("Balletje; nx.sphere.50cm.mesh", new NxOgre::Sphere(0.5f), Ogre::Vector3(0, 20, 0), "Mass: 10");
mBallSceneNode = ((NxOgre::OgreNodeRenderable*)(mBall->getRenderable()))->getNode();
That code works fine here.

If you want a more stable and more documented version I suggest you try NxOgre 0.9, unless you really need the new features in 1.0 or if you just want to help out by testing 1.0

As much as I like free-speech and all. I hate polls, and I hate polls like this. Not only it's rude, it's also demeaning.

If you can't use 1.0 fine, but there are plenty of others who can, and do.

I am very happy with NxOgre 1.0. Of course it's not stable yet, but I like the new graphics independant concept, PhysX 2.8 is supported and I'm hoping for a new Character System (in 0.9, my Character got stuck sometimes).

As much as I like free-speech and all. I hate polls, and I hate polls like this. Not only it's rude, it's also demeaning.

If you can't use 1.0 fine, but there are plenty of others who can, and do.

I think you as the author of the SDK,has reponsibility to serve users and to hear public's voice,so I launched this poll,I am sorry if you think it's rude to u. yes,there are plenty of others who can,and do it much better than me. But maybe there are much more people from all over the world who are using Ogre feel confused by NxOgre1.0, my suggestion is: A mature SDK should contain detailed documents and serevel examples to describe your SDK features,at least,has api manual. if the SDK can not reach this rule,it had better stay until it can do. "Customer is God." you cost over 2years to create this masterpiece for what? I consider the answer is for people not only for u. I just wanna help NxOgre to become more popular and more people will like it,including many rookies such as me.

It has been said again and again about the documentation, and I've always replied. I am working on it. I work almost 10 hours a day on NxOgre, almost 15 in some cases. Would you rather me create beautiful, featured filled, fast code, or spend all of my time knee deep in documentation?

It isn't hard to run Doyxygen through the source code. Nearly every major function and class is commented using the "JavaDoc" method? Is it not reasonable to use the search, or look it up at NxOgre.org? Or even look at the Cake source code? I've designed every class and method to be self-initiative, if it's not - there is something there to tell the user what to do, when they use it.

I must remind you, that I don't get paid to write NxOgre. I'm currently not using it in any games project I'm working on. Infact I'm not working on any games projects anymore because all of my attention is focused on NxOgre, for other people I may add.

That being said, I feel you don't have any rights to complain about the quality or quantity of work, but only to give out constructive criticism.

actually ,complaining about something is my rights, that you don't like these complaining is your business, each coin has two sides,right?
If my words make u unhappy,I apologize to u. But I keep my opinion, I don't think a clear detailed document for a SDK is unneccesary. It does not mean I am forcing you to cost more time to write doc and creating codes without any pay. Certainly, you did a good job in 2 years. but suppose you find some helpers,or volunteers, to build NxOgre together,like a studio,that must be more efficient. It's just a simple idea.

I have seen the comment in each head files, but users prefer ro read CHM mostly, can u publish such API document? I think it is easy to u.

After galancing at Ogre or Physx SDK, we will find the difference.
As I have great expectation in NxOgre and it's author, I put forward my "unconstructive" criticism, if you are bothered,execuse me again please.

I have seen the comment in each head files, but users prefer ro read CHM mostly, can u publish such API document? I think it is easy to u.

http://www.stack.nl/~dimitri/doxygen/


And actually. I don't think you should complain about something that is given to you for free.

I will try to keep my comment as constructive as possible...

NxOgre is not a "mature" library. You are expecting a lot from it at this point in time. I see that there is the one person working on it so I think you might have come of a bit harsh here with your "Customer is God" style talking.

It is still changing a lot I think.

I have post-poned my work concerning physics programming because of this. I want to wait now regarding physics and work on other areas of my application in the mean time.

I recognized that NxOgre is not matured enough yet, and it is better for me as a hobbyist, relatively inexperienced programmer, to wait if it stabilizes and gets more documentation so that it is easier to understand how NxOgre should be used.

Because I am not in a hurry and can wait patiently that betajaen gets a chance to improve NxOgre and its documentation. I would help if I could, but I think my experience in this field isn't enough to help with actually improving the NxOgre library or its documentation.

There is good documentation from AGEIA. I've gone through it and it basically gives much of the information needed when working with NxOgre.

I have seen the comment in each head files, but users prefer ro read CHM mostly, can u publish such API document? I think it is easy to u.

http://www.stack.nl/~dimitri/doxygen/


And actually. I don't think you should complain about something that is given to you for free.
sincerely say sorry to u, I become impatient these days for troubles I met in NxOgre1.0 , but it's not your fault. Any way,I will support u and NxOgre forever and learn to ask for contructive help not complaining.

byw, hope to see your stable NxOgre1.0 before long

The thing is; NxOgre 1.0, is based upon 0.9, which is based upon 0.6. Which has been used by many people for the last two years. How many people would you say, has had the core (World, Actor, Shapes) of NxOgre crash, due to general usage?

I run NxOgre applications 30-40 times a day at least. I've run tests creating 30 scenes at a time and creating many different types of Actor combinations to stress out the PhysX solver and find bugs in NxOgre. It's been fine. NxOgre is stable, but it's not mature yet.

Any crashes are due to human input error and not following the rules properly.

I'm late in the discussion but i want to point just one thing that none here said.

There is no NxOgre documentation (and i dont like current demo code, although i liked the very first demos in nxogre 0.4/0.6) that's right, also in many NxOgre releases there is an interface change, it has some bugs, etc etc.

BUT when you have a problem, the mantainer itself is giving support in the forums, sometimes just one minute before the user posts Betajaen is replying. He provides a 5 stars quality support.
Usually you wont get that kind of support even paying for it.

A more usefuls poll would be:
What features you think NxOgre must have?
What things you do/dont like about NxOgre?
What should be the next feature/task to be done in current version?

A more usefuls poll would be:
What features you think NxOgre must have?
What things you do/dont like about NxOgre?
What should be the next feature/task to be done in current version?

Yes! I prefer polls and posts like this.

kidcdf, not to be mean or anything, but reading your posts really put me into strangling mode.

Problems or not, you can't really talk like that for something that you are provided for free, and on top of that, has great quality. Can't imagine how it feels when you are doing something for other people, spend more time than you probably "should", and you get pure whine posts with no content.

I just had a bad temper these days, and I have apologize to him, is that not enough? can you stop blaming please? - -

I partly agree with both sides in this discussion, I love the ease of use of the NxOgre's up until 0.9, I guess because of Bleeding moving away from Ogre slightly it seems to me to have made things alot more complicated to use, my project is using 0.9 and I'm very reluctant to move to bleeding as it would mean alot of changes plus the fact that there is very little information on doing things in Bleeding at the moment. If me or someone else adds interpolation to 0.9 I'll probably stick to using that.

Having said all of that, I am very, very greatful to betajaen for all of his hard work, as he says, which would we prefer him to spend his valuable time working on, new NxOgre code or documentation?
As has been stated, you shouldn't really complain about something that is free.

Thank you very much for bringing us NxOgre betajaen

I find it insane, ogre has documentation, physX has documentation. betajaen even provided you with a nice looking "book" to get you started. If you cant take the trouble to read through the documentation then I dont what to say...