I could be wrong, but something from the back of my head suggested me: could you try to rename the file Device.dat in your Orbiter root folder, and see if it gets recreated upon next start?
About these new Titan textures, I've taken 4 screenshots (scenario is "The Solar System - Titan", starting paused):
Orbiter2016, default textures
Orbiter2016, D3D9Client2016-R3b, default textures
Orbiter2016, HiRes Titan textures + new config
Orbiter2016, D3D9Client2016-R3b, HiRes Titan textures + new config
Is there any new information on this problem with the new Titan textures in the D3D9 client?
I'm running r84 and have both a Callisto\Archive\Surf.tree and a Ganymede\Archive\Surf.tree, and both look normal on MOGE and D3D9.I was clicking through the "The Solar System\Grand tour.scn" scenaio and found that Callisto and Ganymede were just black rsp. white spheres.
I could circumnavigate the problem by
1. getting Textures\Callisto.tex and Textures\Ganymede.tex from Orbiter 2016
2. remove/comment-out the "TileFormat = 2" line(s) in Config\Callisto.cfg and Config\Ganymede.cfg so that the "old .tex" files are used.
My question is: Did I miss some Hi-Res package that contain those two moons? (Minor bodies doesn't)
or are we lacking Hi-Res textures for them and the (Orbiter BEAT) repository should be "modified" as I did locally?
 black when using D3D9Client, white when using the inline client
Thanks for the hint![...]
Note that the texture maps for most of the planetary bodies are not included in the SVN repository. You need to install those separately. The easiest way is to re-use the texture directory from an existing Orbiter 2016 installation
Nailed it!...So my theory is: any orbit-drawing add-on enabled?