General Question Generic base objects

[fort]

Yes,

and i think, with a meshe makes as a vessel, it must be enough simple to have that sort of auto switch with some, or at least, one C++ function. I've collected some topics about that.

 

[orb]

Yes,

and i think, with a meshe makes as a vessel, it must be enough simple to have that sort of auto switch with some, or at least, one C++ function. I've collected some topics about that.

Yes, they can use for example this function to switch between their day/night textures.

 

[fort]

And/or ( like i see it in one topic ):

SetMeshVisibilityMode() ?

But, what is that ?

void oapi::GraphicsClient::GetBaseStructures  ( OBJHANDLE  hBase,  
  MESHHANDLE **  mesh_bs,  
  DWORD *  nmesh_bs,  
  MESHHANDLE **  mesh_as,  
  DWORD *  nmesh_as   
 )   const 

Returns meshes for generic base objects. 


Parameters:
 hBase  surface base handle  
 mesh_bs  mesh list for objects rendered before shadows (NULL if none) 
 nmesh_bs  list length of mesh_bs list  
 mesh_as  mesh list for objects rendered after shadows (NULL if none)
 nmesh_as  list length of mesh_as list  // 

Note:
The lists contain mesh objects as well as generic object primitives 
(blocks, tanks, hangars, etc.) 
All generic objects are separated into objects rendered before and 
after shadows, and compressed into one mesh each, such that all 
objects with the same textures are merged into a single group.

 

[orb]

And/or ( like i see it in one topic ):

SetMeshVisibilityMode() ?

I'd probably use oapiSetTexture() for it, but maybe SetMeshVisibilityMode() would be useful too.

But, what is that ?

void oapi::GraphicsClient::GetBaseStructures  ( OBJHANDLE  hBase,  
  MESHHANDLE **  mesh_bs,  
  DWORD *  nmesh_bs,  
  MESHHANDLE **  mesh_as,  
  DWORD *  nmesh_as   
 )   const

This is a function used by graphics client. It returns mesh definitions for objects in a given base.

 

[fort]

Thank you orb,

I put in a corner the topic that you linked in your '22' answer. Maybe, someday, if i begin to learn C++...

Concerning the "void oapi" etc, i think definitly that it will be a little useless, or expansive, to create a personal graphic client, only in the intention to show - with it's own criteria - a simple base.

Am i wrong ?

 

[orb]

Concerning the "void oapi" etc, i think definitly that it will be a little useless, or expansive, to create a personal graphic client, only in the intention to show - with it's own criteria - a simple base.

Am i wrong ?

In my opinion it isn't worth the trouble. The aforementioned function returns only meshes defined in the configuration of the base, and don't forget that external graphics clients don't support yet SOLARPLANTs at all, and not fully TRAINs (the stock animated base objects).

 

[fort]

Thank you,

And it was not in my intention to go so far with my nightlights work. I stay and i will stay - and i think that it is the most reasonable (? raisonnable, in french ) way to do it - with my simple meshes and their TEX tag in the cfg.