[Set camera to a camera in the scene/level/map]

AZ wrote:

 

 

the situation, and i guess the needs of AZ was to get a camera created in the editor from c++

 

so, i created a camera in the editor, name it EditorCamera and then inside c++ i scan the list of objects and get's the "EditorCamera"entity

 

i create a camera only if i didn't found the one i created on the editor, because, as you said, having no camera is no sense.

 

in App.h, the variable camera is declared as Camera

if we change the declaration from Camera to Entity, then there are no problem and we can get the EditorCamera from the map and assign it to the global variable camera from c++

 

i'm just trying to solve the AZ trouble, and by te way, learning a bit more.

 

We have a winner, who got what I was asking for,

I pasted the code in, but I'm getting a problem on

Map::Load(mapname, StoreWorldObjects);

I'm getting

Error 1 error C3867: 'State::StoreWorldObjects': function call missing argument list; use '&State::StoreWorldObjects' to create a pointer to member

[Set camera to a camera in the scene/level/map]

No, I'm trying to not create a camera in code,

but tell the code use a camera in the level/map/scene.

 

The code is in C++, not lua.

[Set camera to a camera in the scene/level/map]

Hi

I'm trying to set the camera to one I have in the scene

 

Currently I'm using one that is created, but I would like to switch to one that already is in the scene/level/map.

 

I'm curious as to how to do this?

 

Thank you for your time and replies

AZ

[Installing Leadwerks for Linux]

I backed at the Pro Backer level, does it cover a Windows Standard version of Leadwerks?

 

PRO BACKER: Receive Leadwerks for Linux when it's released. This allows you to program games with C++ and Lua. You will also receive Leadwerks for Windows and Mac.

[A Starter Kit or Starter Template]

I just found this post. it is helpful in that it links to samples and tutorials of some of the items in the list. (some in Lua, others in c++)

 

And as one person once said "Patience is a Virtue."

[A Starter Kit or Starter Template]

Since I'm very new to Lua and to programming with an API in C++.

 

I think a starter kit or template kit would be nice for the beginners to this, who could see what does what, why it's needed, and how it works. This would give a base idea of a foundation for experimentation and development of their idea of a game.

 

As some of us may have a very hard time combining the various tutorials (or no tutorial on subject in lua) and getting the engine to run a single player experience like the start of Half-life, Menu screen, start game, no weapons, explore, then **** hits the fan then load new level, test new weapons, going through a breakable wall to the exit.

 

If the starter kit / starter template is a good idea I think it should contain the following example maps;

• an example of creating and using a statemachine for main menu, an options menu that effects the game, and the game itself,
  
• an example of level/map switching,
  
• an example of weapon pickup and weapon switching, and have an example of two weapons, a melee (crowbar, knife etc) and a gun which displays it's ammo count when selected (to help in learning to display ammo count, HP, SP etc.),
  
• An example of a breakable wall, or building collapse from breaking a support.
  
• and a final example where all the examples are tied to gather.
  

All of these should be covered in both C++ and Lua langauges to help those who are new to programming in either of these languages and picked up the engine, since it looks to be better than some of the other engines out there.

 

Now, I will admit I'm aiming to make an RPG, but since the FPS genre is the easiest type of game to start from. It would be the best starting point to learn from.

 

And if people enjoy the starter kit, maybe a more advanced kits could be made to cover more advanced things like; creating or modifing the AI behavior (learn AI logic and processing), Character subtypes (learn inheritance), inventory systems, Advanced map features, ... Etc