Reporting bugs

[StormGnu]

Well I've been using the editor for a few hours now and the editor crash from time to time. In the long run we should definitely have some kind of bug reporting system were we can see if other / jochen can reproduce them and what priority a fix for the bug has, also how serious the bug is.

I'll try to use the form:
Severity - Crash, Graphic glitch etc.
Description - Description of the bug.
Reproduce  - How to reproduce the events that led to the bug, if possible
Comment - Any comment or thoughts on the bug itself.


#1 - Place deletion
Severity
Crash
Description
When deleting a second "Place" objects in the node tree the editor always crashes.
Reproduce

• Load any of the demos or create a new scene.
• Create two or more "Place" objects in the script tab.
• Delete any two "Place" objects.

Comment
This does not happen if you delete the "Place" objects in the script tab, only in the node tree.
Very low priority. Will get fixed sometime

#2 - LOD change
Severity
Crash
Description
When a lot of LOD changes to the terrain is made, the editor and planet viewer crashes.
Reproduce
The editor and planet viewer crashes EVERY TIME after I've looked around a few times or immediately if i try to zoom in.
Comment
It's like i said in the description, it happens when the LOD of the terrain starts to change, i think the crash happends even before it starts to change. I think that it only happens when there is really alot of LOD changes to be made at the same time.
This is clearly a major problem. I am on it.


#3 - Perspective creation
Severity
Crash
Description
When creating a new perspective in a new file.
Reproduce
Create a new file and try to add a Pangea->Perspective object to Interface in the node tree.
Comment
This does not happen when i add it to demo7.3Dm while it happens when i tried a few of the other demo*.3Dm. I guess it has something to do with there already being three Perspective objects added in demo7.
This requires some know-how about the GUI. The perspective will crash if there is either no Inventory, Acton Bar or Power bar.

#4 - Collision sensors
Severity
Don't work
Description
 I can't get OnEnter or OnExit to work.
Reproduce
Try to execute anything OnEnter or OnExit.
Comment
Like i said in the post, demo4 does not work as intended anymore either so something is wrong.
Should be fixed now

[Jochen Stier]

#2 - LOD change

This is a big one. I have never had that on my PC yet. It probably has something to do with the timing. Your PC is either much faster or slower than mine and thus produces a condition that does not happen with me. I have just recently changed the terrain tesselation algorithm, so the problem definately has to do with the changes I made. I will try it on my laptop and see what happens.

Can you clarify though if this happens only when you zoom; i.e. right click on the avatar cam inside the shuttle. I wonder how you even found the zoom function? Or does it happen just when you look around. Can you also try to move the LOD slider in the options window to the left and see if it still happens. ...

thx for the report, I'll get on that ASAP

[Jochen Stier]

Ok, I just tried it on my laptop which is a lot slower than my PC and it works. What kind of processor do you have. Unless it is a lot faster than mine, the problem must have somehting to do with windows 7  and the graphics drivers. I won't be able to fix it until I get my hands on the appropriate hardware/software.

[StormGnu]

About #2:

You're probably right about the drivers and W7. I have a Core 2 Duo @ 2.4 Ghz.

I changed the LOD (i didn't find that option at first) and it did help a lot!! At the lowest level i have yet to experience a crash. At higher levels it takes a little longer but the higher LOD, the faster it crashes =/

[StormGnu]

I'm not sure if it's intentional but why does it matter in what order stuff is placed when placed in a group in the node tree? If for example i place a shader, textures and a geometric figure, say a box, in the same space, then the shader must be first, textures second and box last.

Is this as it should be?

I hope you don't mind me throwing all these bugs at you I've been trying to use and learn a bit more of the editor lately and it crashes about every 10min or so because of different reasons. I usually try to find out why it crashed but I don't always succeed to recreate what i was doing...

[StormGnu]

Collision sensors are not working anymore, at least not the same way as they used to.

Check out demo4, the collision sensors should change camera angles, and did before this version i think, but they don't change.

By the way, I don't think anyone notices when I update the first post so I'll just post here when I find a new bug also.

[TorakunSama]

Talking about collisions, aren't the objects supposed to collide against the trees? Well, they don't!

[StormGnu]

Yes, but I think that this has nothing to do with the collision sensors in the editor, although I really don't know. I think Jochen mentioned something about this in a journal so I'm sure it's pretty close to being implemented.

[Jochen Stier]

The object's don't collide with the trees yet. I haven't actually written the code for that yet. I have just architected the system so that it is possible. I will do that some time in the future.

Yup, I also noticed that the collision sensors do not work anymore. I have a pretty good idea why and I will fix that ASAP.

[Jochen Stier]

I have made this post sticky. Please add additional bugs to the orignal post as stormgnu has outlined. I will keep updating it as fixes are made.

[TorakunSama]

I'm here to report 2 types of bugs in the latest editor, that might go to the next.

After testing a bit I found the following.

1. The editor does not allow adding most of the game objects specially planets. Result : Crash
  . The clouds layer is independent from the planet. Scaling the planet will not scale the clouds.
 
2. From Demo 7, I see visible Nvidia artifacts (flickering black spots/areas in the darker zones of an object (shuttle); Atmospheres and cloud layers are on always on top, objects in front of it don't show (see image).
3. From demo 7, Explosions are messed up, I think the clouds colors are also messed up.

Note that I didn't notice these problems on an ATI system.

[TorakunSama]

And the explosions problem.

Creating a shuttle, shows the bound box, again.
Minimizing the editor and maximize it again, sometimes shows nothing (this my be a problem with my machine, though this problem was not in the previous version).

[Jochen Stier]

Good to see that you are using the editor! I know there are lots of problems in this version. Soon I will be done with the clouds and then I will put my old NVIDA card back into my computer and make sure that everything runs on both platfroms. I still have some blending problems to work out between the cloud billboards, but I am getting there. For the shape of the clouds I tried some kind of growing alogorithm with little success. For now I will probably just stick with Perlin noise. The planet wide cloud cover will disappear and we will place cloud fields by hand. That should remove some of the problems you are seeing right now.

J