Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[3D Rad Developer - Fernando]

Proposed new feature

A new 'LOOK-AT' setting for the items listed in the relationship window, on the CamChase object dialog.

If an object is marked as 'LOOK-AT', the camera will look at it, while still following any object marked as 'CHASE', as usual.

If multiple objects are marked as 'LOOK-AT', the camera will look at the closest.

If an object which is marked as 'LOOK-AT', is 'hidden' the camera will ignore it.

Example of usage is a camera following a walking character (CHASE) but looking at a monster (LOOK-AT).

If the 'LOOK-AT' object is a 'dummy' invisible SkinMesh, you can dynamically place the dummy SkinMesh anywhere in the scene to change camera target, while still following the actor.

The new functionality will come with updated documentation and a sample project.

TIMEFRAME: 8 weeks after budget is reached.

[loop]

could this option have a setting to work always or when a button is pressed?

because if not and we want to do something like the car bomb demo we should make two cameras and switch them using a button, with all the inconvienence that it evolves.

I think a setting to choose if the camera gonna look at the extra object OR at the chase object always or only when a button is pressed would complete this feature.

besides I dont really think someone gonna use a camera looking at something else ALL the time. is just something more like the car bomb I think.

[3D Rad Developer - Fernando]

You can achieve run-time target switching by using the 'invisible-skinmesh' method mentioned above.

EDIT: after thinking about it, to make it more flexible, I will make so that, if multiple objects are marked as LOOK-AT, the CamChase will only pick the one set to 'visible-mode' (see SHOW/HIDE function, event objects help files). This way, you can have multiple dummy SkinMeshes, attached to various objects, and select the target based on what dummy skinmesh is set to 'visible-mode'.

Thanx for pointing it out loop 

[loop]

in case there are several set to visible 'LOOK-AT' skinmeshes, which one the cam would look at?
could be the closest?

[3D Rad Developer - Fernando]

Yes, nice idea 

[loop]

the ability to switch between all the set to visible 'LOOK-AT' skinmeshes pressing a button would be too much¿ 

[3D Rad Developer - Fernando]

It wouldn't fit into the budget. I have added a separate entry for it.

Thanx loop!

[loop]

what you propose in that new proposed feature is not what I just said, is the first thing I said but not the last.

what I actually meant is to switch between all the LOOK AT skinmeshes.

EXAMPLE!!:

I have 3 LOOK AT skinmeshes, which happens to be all set to visible.

camera is looking at number 1

I hit the button, camera change to number 2
I hit the button, camera change to number 3
I hit the button, camera change to number 1
I hit the button, camera change to number 2
and so on...

also:

I set to NOT visible skinmesh number 2

camera now look at skinmesh number 3

I hit the button, camera change to number 1
I hit the button, camera change to number 3
I hit the button, camera change to number 1
and so on...

 

[3D Rad Developer - Fernando]

Ah, ok, sorry. Cycling through all LOOK-AT objects would be tricky because this functionality would have to coexist with the system which picks the closest. We would need additional options to let the user choose the picking method and the CamChase dialog would become more complicated to use.

Keep in mind that the same goal can be achieved by moving the invisible dummy skinmesh from one object to another.

What is the community feedback about this?

[loop]

yes, you can do that moving the invisible dummy skinmesh, as well you can do THIS http://www.3drad.com/forum/index.php?topic=2998.0 just setting to invisible the skinmesh, the way you propose earlier,

EDIT: after thinking about it, to make it more flexible, I will make so that, if multiple objects are marked as LOOK-AT, the CamChase will only pick the one set to 'visible-mode' (see SHOW/HIDE function, event objects help files). This way, you can have multiple dummy SkinMeshes, attached to various objects, and select the target based on what dummy skinmesh is set to 'visible-mode'.

scripting.

the difference is the need to script or not, which I think, avoid scripts, is the main goal when someone go for proposed features like this one.

NOW!

Ah, ok, sorry. Cycling through all LOOK-AT objects would be tricky because this functionality would have to coexist with the system which picks the closest.

the system which picks the closest, to know what the closest is, dosnt make a list of all the skinmeshes and order then from closest to farthest??
because, if it does that, then to cycle through all LOOK-AT objects you just need to cycle through that closest to farthest list?

what Im not seeing?

[3D Rad Developer - Fernando]

But we don't know if the game developer will be satisifed with cycling through the object based on distance. They may want to cycle in another order, or randomly...

The problem is how complex this feature would make the interface. The last thing we want is making the help file for the CamChase object like the Space Shuttle User Manual, don't we 

[loop]

But we don't know if the game developer will be satisifed with cycling through the object based on distance.

well, we dont know if the game developer will be satisfied with the cam looking at the closest object either, do we?

that's my start point to propose to cycle objects based on distance.

you could cycle them based on the list of objects in the cam dialog too! would -in my opinion- have less sense, BUT... in the end the same goal is achieved.

is cycle objects not space travel, for god sakes 

[laynedel]

yay my idea was posted as possible!!!

[3D Rad Developer - Fernando]

is cycle objects not space travel, for god sakes 

I don't know loop, I'm not convinced that making the CamChase object more complicated to simply support this is a good idea. After all automatically selecting the closest will cover the majority of cases. And for the rest you can still write a little script.

Furthermore, the algorithm to cycle through objects based on distance is weak, prone to cause problems.

For example, what if you switch to object A, which is the 3rd in the a list sorted by distance. Then A becomes the 4th in the list (it moves!). When the user presses the button again object A is selected again (the target will not change), and the user of your game will complain that your game is buggy 

[archangel]

I think the best way to re-target is what was alluded to earlier: to relocate a dummy, invisible skin mesh.  It would work the same way as say the RTS character we were messing with awhile back...

Then at least the designer could define the sorting parameters.  I.e. distance, bearing etc....