[SOLVED] Double Mode Editor Error

[modori]

hi.

 

 

Engines were compiled into a double mode.

Nothing that other issues

Joint property settings in the Editor at the coordinates will modify parts of an error.

 

10:29:40 load samples/joints/hinge_02.cpp:

10:29:40 Loading "samples/joints/hinge_02.cpp" 28ms

10:29:40 Loading "samples/joints/common/joints.mat" 7 materials 3ms

10:29:40 Loading "samples/joints/hinge_02.world" 3ms

10:30:12 Variable::getDVec3Safe(): can't convert vec3 to dvec3

10:30:13 Variable::getDVec3Safe(): can't convert vec3 to dvec3

10:30:18 Variable::getDVec3Safe(): can't convert vec3 to dvec3

10:30:20 Variable::getDVec3Safe(): can't convert vec3 to dvec3

10:30:23 [uGD]: video_grab

 

 

Is there any further modify parts?

[steve3d]

double precision require more work, some demos don't work, so if you really need that, you should modify these by you own.

 

Most problem is:

use Mat4 instead of mat4,

also Vec3 instead of vec3.

 

others like this.

[modori]

OK!

 

thank you.

[dave.lannan]

Hi again,

We are seeing this error which repeats while trying to modify a node position of a world object in the tracker editor. It didnt seem to matter what object we chose in our world, the results are pretty much always the same. And the objects being selected are loaded in from a normal world.cpp file (although large in dimensions - some 30 km in length).

 

these two lines below.. repeat continually

 

14:00:29 Variable::getDVec3Safe(): can't convert vec3 to dvec3

14:00:29 Editor::update(): editor update function return 0

.....

 

When this happens it can occur in a number of places with the Tracker Editor open.

- When setting new time size for the tracker

- When trying to play the new tracker keys

- When adding new keys into the tracker.

 

I suspect there is some conversion missing somewhere? Shouldnt all node positioning be using Vec3 and not vec3?

Cheers,

Dave Lannan

[frustum]

Fixed. Try the updated version of tracker.

tracker.zip

[dave.lannan]

Thanks very much frustum. This patch worked very well!

I assume this will be in the coming SDK's?

Thanks again for the prompt response too. Has helped us move through a feature addition very quickly.

Cheers,

Dave Lannan

[manguste]

Yep, sure, it will be in the next SDK as well.