# New ReleaseD3D9Client Development

#### Donamy

Donator
Beta Tester
Figuring out this awesome camera. i.e. focused vessel is Cupola, press F1 for cockpit view, select generic camera, change "VES" to TVstanchion1 view. Looks beautiful !! Press F8 for VC view. Camera view reverts back to Cupola attachment.

Could you make it so the camera retains the different vessel view, when switched to VC mode in Spacecraft3/4 ?

#### Chris74

##### New member
sorry for the noob question.
do celestial bodies cast shadows on each other?
i.e. at solar eclipses, does Moon cast a visible, moving shadow onto Earths surface? :hmm:

thx :thumbup:

Here's a latest version of the client. It's build by using an automated build script, so, let's hope the automatics got it right.

#### DaveS

##### Space Shuttle Ultra Project co-developer
Donator
Beta Tester
sorry for the noob question.
do celestial bodies cast shadows on each other?
i.e. at solar eclipses, does Moon cast a visible, moving shadow onto Earths surface? :hmm:

thx :thumbup:
No, they don't. So no eclipses.

#### Donamy

Donator
Beta Tester
These cameras are fun to use. Could you add no near clipping to the cockpit view ?

#### Attachments

• 198.8 KB Views: 77

#### Chris74

##### New member
No, they don't. So no eclipses.
lol thx meanwhile i figured it out too, after munching thru like 50 threads about REAL solar eclipse observations, which i have absolutely no clue about what on EARTH are those doing in a forum about a spaceflight simulator...

(sorry OP for the off )

but its kinda weird that no eclipses in 2018, not?

Donator
Beta Tester

#### fred18

Donator
Not sure on what you are asking for. I'm not on the team, just curious.
I think he's referring to the fact that on an MFD if you have to increase a value by a lot you usually keep the mouse button clicked and it increases. But it's not immediate to do, there is some sort of a trick, other wise you must click once for each small increment, so if you need a big increment you need to click 1000 times.

For the record Ripley I knew how to do it but I can't remember it now, if nobody else replies to this soon, I'm goona go look in my addons to see how to do it

#### Ripley

##### Tutorial translator
Donator
Exactly Fred18, and (in behalf of Abdullah, I guess) thank you for your offer!

#### jarmonik

Beta Tester
These cameras are fun to use. Could you add no near clipping to the cockpit view ?

Could you be little more specific about what you mean with cockpit view ?

If it's virtual cockpit camera you are talking about then, No. Near clipping can't be removed but can be reduced. If it's reduced too much, z-fighing will start to occur. However, the biggest issue is that often there is a pilot sitting on pilot's chair and the VC camera is inside the head/helmet. Reduction of near clip plane would make the faceplate to become visible. That's been a problem with stock DeltaGlider. It would be possible to grant a user application a possibility to specify the near clip distance in a per vessel basis via gcAPI.

---------- Post added at 01:55 ---------- Previous post was at 01:51 ----------

The next build of the client/docking camera will have crosshairs and vessel specific instances. So, switching between cockpit modes and vessels won't reset the view.

#### Donamy

Donator
Beta Tester
Many thanks !!!

---------- Post added at 10:48 PM ---------- Previous post was at 01:16 AM ----------

Could you make it so only Child attachments with a "CAM" id, work with the Child attachment views ? Leaving the docking and parent attachments as they are.

Last edited:

#### kuddel

##### Donator
Donator
@Donamy: That could possibly be made, but DockingCamera MFD is more like a "general Docking Camera MFD".
If you like to restrict yourself to only use specific attachments I would recommend that you just restrict yourself (that's by the way the option with the least amount of coding )

But let me think about an configuration option for this:

a) Does it have to be specific to the MFD we use (Left, Right, etc..)?
b) The restriction(s) should also be configurable, not only "CAM". Something like this:
or
or

These restriction(s) should be done in the scenario-file.

Note: Implementation might not be done immediately

#### Donamy

Donator
Beta Tester
Could they be assigned to the preset views from the camera section ? That way they are saved to the scenario.

#### kuddel

##### Donator
Donator
Could they be assigned to the preset views from the camera section ? That way they are saved to the scenario.
Only if you want that camera to *exactly* and *only* show that attachment point.
As software can not read your mind it is impossible to guess what kind of rule we should derive from the current setting. Sorry that is plain simple: not possible at all!

As you see it starts to get complicated to even just describe the behavior. Which is usually a good indicator of a messy design

If one (read: you) wants to restrict the MFD to show only one specific attachment all the buttons that select the docking-port rsp. attachment-point are useless, opening up future "why do this buttons not work?" questions.

I would still go for the "mask" solution that would only be read from a scenario, but never be automatically created and written. The "mask settings" would however be copied when saved.

Last edited:

#### Donamy

Donator
Beta Tester
If they could be assigned in the Scenario, that would be great. :thumbup:

#### kuddel

##### Donator
Donator
Could you make it so only Child attachments with a "CAM" id, work with the Child attachment views ? Leaving the docking and parent attachments as they are.
So, finally I found a little time to code this. My first thoughts however were much to complicated I think
I thought that the IDs were some kind of "CAM1", "CAM2", "CAMx". But I believe, that all attachments share the same ID ("CAM" in this case),right?

The attached DockingCamera now includes the possibility to only show attachments with a specific ID.
To enable it, just add the ATCH_MASK configuration to the MFD section of the scenario.
Example:
Code:
BEGIN_MFD Left
TYPE User
MODE Generic Camera
END_MFD

BEGIN_MFD Right
TYPE User
MODE Generic Camera
END_MFD
This however is also a limitation, as you can not "pre"configure MFDs of other (not focused) ships.
If someone has any good idea how this could possibly be made, please give me a hint (I'm curious).

Disclaimer: This is for Orbiter BETA + DxD9Client :thumbup:

Edit 2018-11-12: Attachment removed as to this new post

Last edited:

#### Donamy

Donator
Beta Tester
Any chance it will work with regular 2016 + DxD9 client ?

#### kuddel

##### Donator
Donator
Any chance it will work with regular 2016 + DxD9 client ?

(ZIP includes DLLs for both BETA and 2016)

#### Attachments

• 145.2 KB Views: 11

#### kuddel

##### Donator
Donator
@Donamy: By the way, what vessel uses the "CAM" attachments?