jMonkeyEngine.org

Any stack traces?

The first optimization is to remember the old adage about pre-optimizations

This question depends entirely on what your update loop is doing, but I would say that a smart use of the engines features – like […]

Well, I’m still on Java 6 and uses it on daily basis, so I already compile in lower level . The problem is people who tried to run on JRE 7 didn’t succeeded on that, but game runs fine on JRE 6 (my java […]

@pspeed Now my posts seem really goofy, like I did not even read your post.

Thanks again for the help.

@pspeed said:
I actually said exactly what the error was but my post got cut off because our forum is incredibly stupid.

@darklightning7: Yeah quote him for the truth
Edit: Ah, now its visible w/o […]

I actually said exactly what the error was but my post got cut off because our forum is incredibly stupid.

I think I found the problem I am not testing to see if the fixedResults0 so when I test the selectedResult.getDistance() fixedResult.getDistance() it was occasionally coming up with a null distance for […]

I know that is where the compiler says it fails but I have had more than a few times where the line that the compiler tells you is not actually the problem or causing the error or even related to the error. […]

“if( selectionMode == true && selectableResults.size() GREATER_THAN 0 && selectedResult.getDistance() LESS_THAN 25 && selectedResult.getDistance() LESS_THAN fixedResult.getDistance()){”

It is possible to not […]

I did set the limit and the selectableRessults.size() 0 and fixedResults.size() 0 provision in the if statement should take care of the exception when nothing is hit unless there is something I am missing. Also […]

Ummm… the ray has no length unless you set the limit.

But anyway, seems like your NPE comes because you didn’t hit anything. A simple log statement or println before line 161 will tell you.

Another issue related to this I am getting a NullPointerException when I go from a selectable object to a fixed one or to out of range quickly. I am not sure of the exact combination of events that causes this […]

Thanks. That is exactly what I needed.

It depends entirely on how your scene graph is constructed. If certain branches can be ruled out of intersection with a shorter Ray then you will save time.

At any rate, it doesn’t hurt to set the limit of […]

Oh duh, you change the range, right.. Well I guess there isn’t too much to save as afaik there is no real broadphase in the jme picking but empirical data is your best bet.

so there is no performance difference between using a ray or using a vector of a short length to find objects within a certain range? If I am using a ray when finding collision .collideWith() will find all […]

You don’t save anything in the picking there.. selectables.collideWith() and fixed.collideWith() is where the work happens. If you know the player is in one room or something then make a node for that room as a […]

thanks normen it worked.

one more question related to this. Performance wise is it better to create a ray that will interact with all objects within the render distance or is there some way to create a […]

how about picking the nodes in succession?