[TEC] Link between clickable spot and camera?

Darkbluesky · 04-23-10, 04:31 AM

Hello

I was exploring .cam files in order to learn to mod some ideas I had.

I found, for example this: the highlighted proprierty defines the action to trigger when the parentID model (in this case the conning tower hatch 3D model, whose definition is inside the NSS_Uboat7_CR.dat file) is clicked.

The action is, afaik, to trigger the "Conning tower camera", according to what is shown in S3D (see screenshot), if I am not wrong. At this point I lose the link between this and the definition of the characteristics of the conning tower camera, which is defined in Cameras.dat.

I mean, how does the engine know that the command described here "Conning tower camera" relates to the CT camera in Cameras.dat (in Cameras.dat it is described as "_Dummy_Cam_ConningTower")? Is there still another file in between?

The node "_Dummy_Cam_ConningTower" in Cameras.dat does not have any ParentID, and there is no reference to the command "Conning tower camera" in commandes_en.cfg neither... Could some modder please help me?

Thank you very much for any advice!

Note: I am checking all of that with FM_New_Interiors files. Trying to learn from FM work, although I think the question is the same with stock files.

Darkbluesky · 04-23-10, 04:54 AM

Just seen this: in commands_en.cfg there is a "Conning_tower_camera" definition (with underscores), maybe the engine add the underscores itself?. But anyway I can't find a link between it and the camera definition (???!!)

Darkbluesky · 04-23-10, 05:06 AM

Another way to ask the same question is to know how it works when, for example, we click the Command Room icon in the shortcuts bar of the UI.

For this example (command room) I have seen that in menu_1024_768.ini there is that:

Code:

[G3F I32]
Name=Command room
Type=1032;Button
ItemID=0x3F020001
ParentID=0x3F020000
Pos=0,-7,40,41
Materials=4
Display=0;No stretch
Mat 0=data/menu/OLC/Shortcuts/CommandRoom.tga
Mat 1=data/menu/OLC/Shortcuts/CommandRoom.tga
Mat 2=data/menu/OLC/Shortcuts/CommandRoom.tga
Mat 3=data/menu/OLC/Shortcuts/CommandRoom.tga
MatFlags=0x21
TexFmt=0x9
Font=1
TextFlags=0x0
StatesColors=0xB0B0B0FF, 0xFF, 0xFFFFFFFF, 0xFFFFFFFF
;ToolTipText=2710

If we look for the ItemID in commands_en we find that

Code:

[Cmd10]
Name=Interior_fore_camera
Ctxt=1
MnID=0x3F020001
Key0=0x71,,"F2"
Page=0x33000000,3703

Which is ok, but then...what? how the engine knows that it has to apply the "_Dummy_Cam_InteriorFore" node parameters of cameras.dat?

Darkbluesky · 04-24-10, 12:43 AM

bump. Really nobody knows how it works or if it is not possible to know?

asanovic7 · 04-28-10, 01:43 PM

no it is not possible noone knows, just people are kinda lazy these days..

I think you didnt check every inch of the interior files..
I think..
cheers!

04-23-10, 04:31 AM	#1
Darkbluesky Sparky Join Date: Sep 2006 Posts: 155 Downloads: 61 Uploads: 0	[TEC] Link between clickable spot and camera? Hello I was exploring .cam files in order to learn to mod some ideas I had. I found, for example this: the highlighted proprierty defines the action to trigger when the parentID model (in this case the conning tower hatch 3D model, whose definition is inside the NSS_Uboat7_CR.dat file) is clicked. The action is, afaik, to trigger the "Conning tower camera", according to what is shown in S3D (see screenshot), if I am not wrong. At this point I lose the link between this and the definition of the characteristics of the conning tower camera, which is defined in Cameras.dat. I mean, how does the engine know that the command described here "Conning tower camera" relates to the CT camera in Cameras.dat (in Cameras.dat it is described as "_Dummy_Cam_ConningTower")? Is there still another file in between? The node "_Dummy_Cam_ConningTower" in Cameras.dat does not have any ParentID, and there is no reference to the command "Conning tower camera" in commandes_en.cfg neither... Could some modder please help me? Thank you very much for any advice! Note: I am checking all of that with FM_New_Interiors files. Trying to learn from FM work, although I think the question is the same with stock files. Last edited by Darkbluesky; 04-23-10 at 07:09 AM.

04-23-10, 05:06 AM	#3
Darkbluesky Sparky Join Date: Sep 2006 Posts: 155 Downloads: 61 Uploads: 0	Another way to ask the same question is to know how it works when, for example, we click the Command Room icon in the shortcuts bar of the UI. For this example (command room) I have seen that in menu_1024_768.ini there is that: Code: [G3F I32] Name=Command room Type=1032;Button ItemID=0x3F020001 ParentID=0x3F020000 Pos=0,-7,40,41 Materials=4 Display=0;No stretch Mat 0=data/menu/OLC/Shortcuts/CommandRoom.tga Mat 1=data/menu/OLC/Shortcuts/CommandRoom.tga Mat 2=data/menu/OLC/Shortcuts/CommandRoom.tga Mat 3=data/menu/OLC/Shortcuts/CommandRoom.tga MatFlags=0x21 TexFmt=0x9 Font=1 TextFlags=0x0 StatesColors=0xB0B0B0FF, 0xFF, 0xFFFFFFFF, 0xFFFFFFFF ;ToolTipText=2710 If we look for the ItemID in commands_en we find that Code: [Cmd10] Name=Interior_fore_camera Ctxt=1 MnID=0x3F020001 Key0=0x71,,"F2" Page=0x33000000,3703 Which is ok, but then...what? how the engine knows that it has to apply the "_Dummy_Cam_InteriorFore" node parameters of cameras.dat?

04-23-10, 04:54 AM	#2
Darkbluesky Sparky Join Date: Sep 2006 Posts: 155 Downloads: 61 Uploads: 0	Just seen this: in commands_en.cfg there is a "Conning_tower_camera" definition (with underscores), maybe the engine add the underscores itself?. But anyway I can't find a link between it and the camera definition (???!!)

04-24-10, 12:43 AM	#4
Darkbluesky Sparky Join Date: Sep 2006 Posts: 155 Downloads: 61 Uploads: 0	bump. Really nobody knows how it works or if it is not possible to know?

04-28-10, 01:43 PM	#5
asanovic7 Captain Join Date: Mar 2008 Posts: 516 Downloads: 70 Uploads: 0	no it is not possible noone knows, just people are kinda lazy these days.. I think you didnt check every inch of the interior files.. I think.. cheers!