New Release D3D9Client Development

gattispilot

Addon Developer
Addon Developer
Joined
Oct 17, 2007
Messages
6,154
Reaction score
575
Points
188
Location
Dallas, TX
so in the scn:
STS-49:Shuttle2016Bearly

So i made a cfg folder:
Shuttle2016BEARLY_ecam
CONFIG_VERSION 2

BEGIN_CAMERA 0
LPOS 0.0 0.0 0.0
DO_NOT_OMIT_FOCUS
END_CAMERA
I have a file Shuttle2016BEARLY also in the GC folder
It has the mesh and settings,....
Code:
CONFIG_VERSION 2
; =============================================
MESH 2016SPACESHUTTLE\Challenger\Challengerlate2016H2
; ---------------------------------------------
MATERIAL 2
REFLECT 0.866667 0.866667 0.866667
ROUGHNESS 1.00000000

But I see the edwards base on the inside of the bay
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,873
Reaction score
200
Points
153
Lose the CONFIG_VERSION 2 part and only have what I posted in the cfg file. To see what your vessel's class name is, when in game press Ctrl-I to bring up the Vessel Information window. Under Designation you should see the "Class" field, it will tell you the vessel class name you need to use as the file name prior to the _ecam suffix.
 

Attachments

  • VesselInfo.jpg
    VesselInfo.jpg
    1.7 MB · Views: 7

Face

Addon Developer
Addon Developer
Beta Tester
Joined
Mar 18, 2008
Messages
4,194
Reaction score
136
Points
88
Location
Vienna
» Changed syntax to Ellipse -6172 -33.220001 19.129999 2000 2000 (are drop off and angle values not used ?)

The simple parser allows for the last three values to be optional. You could even skip the last 2000 there, because the default for the minor dimension is the major dimension (making it a circle in the ellipse case and a square in the rectangle case). The defaults for the angle and falloff are both zero. A falloff of zero means a hard edge, though "hard" depends on the resolution level, of course. In essence, the FilterElevation function "draws" over the elevation pixels. It would be interesting to know what levels the function gets from the Orbiter collision core when you zoom in, so we would know what level the elevation is at vs. the level of the visual grid.

I'll need to get a working DX9 SDK environment again to check that for my own, unfortunately the machine I used last year is gone already.
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,873
Reaction score
200
Points
153
Could you post the actual scenario in question? I have few suspicions but I want to confirm them before posting them.
 

gattispilot

Addon Developer
Addon Developer
Joined
Oct 17, 2007
Messages
6,154
Reaction score
575
Points
188
Location
Dallas, TX
Here it is.

Code:
BEGIN_DESC
Current scenario state


Contains the latest simulation state.
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 48758.9566071473
  Help CurrentState_img
END_ENVIRONMENT

BEGIN_FOCUS
  Ship STS-49
END_FOCUS

BEGIN_CAMERA
  TARGET STS-49
  MODE Cockpit
  FOV 56.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE HSI
  NAV 0 1
  OBS 5.76 5.76
END_MFD

BEGIN_MFD Right
  TYPE Surface
  SPDMODE 1
END_MFD

BEGIN_VC
END_VC

BEGIN_SHIPS
STS-49:Shuttle2016Bearly
  STATUS Landed Earth
  POS -117.8756941 34.9099651
  HEADING 240.62
  ALT 5.242
  AROT -64.385 60.511 -114.040
  RCSMODE 0
  AFCMODE 7
  NAVFREQ 524 94
  CONFIGURATION 3
  GEAR 1 1.0000
  HATCH 0 0.0000
  ADTA 0 0.0000
  SSMES 0 0.0000
  PETD 1 1.0000
  SETD 1 1.0000
  OV 105
  SPIN0 
  RMSARM 
  ARM_STATUS 0.5000 0.0000 0.0000 0.5000 0.5000 0.5000
  Armtilt 0 0.0000 0 0.0000
  PLB_CAM 0.0010 -0.0020 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 -0.0010 0.0020
  PL1_OFS 0.0000 -1.5000 5.4800
  PL1_DIR 0.0000 1.0000 0.0000
  PL1_ROT 0.0000 0.0000 1.0000
  PL2_OFS 0.0000 0.0000 0.0000
  PL2_DIR 0.0000 1.0000 0.0000
  PL2_ROT 0.0000 0.0000 1.0000
  PL3_OFS 0.0500 0.7000 -2.2800
  PL3_DIR 0.0000 1.0000 0.0000
  PL3_ROT 0.0000 0.0000 1.0000
  PL4_OFS -2.0000 2.0000 -4.0000
  PL4_DIR 0.0000 1.0000 0.0000
  PL4_ROT 0.0000 0.0000 1.0000
  PL5_OFS 0.0000 0.0000 0.0000
  PL5_DIR 0.0000 1.0000 0.0000
  PL5_ROT 0.0000 0.0000 1.0000
  PL6_OFS 1.8500 8.0200 3.9550
  PL6_DIR 0.0000 1.0000 0.0000
  PL6_ROT 0.0000 0.0000 1.0000
  PL7_OFS 0.0000 6.2200 -7.7950
  PL7_DIR 0.0000 1.0000 0.0000
  PL7_ROT 0.0000 0.0000 1.0000
  PL8_OFS 0.0000 6.2200 -7.7950
  PL8_DIR 0.0000 1.0000 0.0000
  PL8_ROT 0.0000 0.0000 1.0000
  PL9_OFS 0.0000 0.0000 0.0000
  PL9_DIR 0.0000 1.0000 0.0000
  PL9_ROT 0.0000 0.0000 1.0000
  pl10_OFS 0.0000 0.0000 0.0000
  pl10_DIR 0.0000 1.0000 0.0000
  pl10_ROT 0.0000 0.0000 1.0000
  ft_pad_att_pos 0.0000 0.7000 11.3210
  ft_pad_att_dir 0.0000 1.0000 0.0000
  ft_pad_att_rot 0.0000 0.0000 -1.0000
  ft_pad_att1_pos 0.0000 0.7000 11.3210
  ft_pad_att1_dir 0.0000 1.0000 0.0000
  ft_pad_att1_rot 0.0000 0.0000 -1.0000
  ft_pad_att2_pos 0.0000 0.7000 11.3210
  ft_pad_att2_dir 0.0000 1.0000 0.0000
  ft_pad_att2_rot 0.0000 0.0000 -1.0000
  ft_pad_att3_pos 0.0000 0.7000 11.3210
  ft_pad_att3_dir 0.0000 1.0000 0.0000
  ft_pad_att3_rot 0.0000 0.0000 -1.0000
  KEEL_CAM 0.1452 -1.5000 -1.3560
  FLOOD1 0
  FLOOD2 0
  FLOOD3 0
  FLOOD4 0
  FLOOD5 0
  FLOOD6 0
  DOCK_LIGHT 0
  AFT_LIGHT 0
  RMSLIGHT 0
END
PAYLOADBAY:STS49
  STATUS Landed Earth
  POS -117.8756712 34.9099757
  HEADING 240.62
  ALT 3.415
  AROT 0.000 -0.000 0.000
  ATTACHED 0:2,STS-49
  AFCMODE 7
  NAVFREQ 0 0
  XPDR 0
END
MPESS:MPESS49
  BOX1 0 0.0000
  BOX2 0 0.0000
  RAIL1 0 0.0000
  RAIL2 0 0.0000
  ASEM 0
  STATUS Landed Earth
  POS -117.8757448 34.9099417
  HEADING 60.62
  ALT 2.839
  AROT 0.000 -0.000 0.000
  ATTACHED 0:0,STS-49
  AFCMODE 7
  NAVFREQ 0 0
  XPDR 0
END
RMSPFR:RMSPFR
  YAWARM 0.0033
  ROTATION 0.5000
  PITCH 1.0000
  STATUS Landed Earth
  POS -117.8758064 34.9099081
  HEADING 60.62
  ALT 5.616
  AROT 0.000 -0.000 0.000
  ATTACHED 0:0,PAYLOADBAY
  AFCMODE 7
  NAVFREQ 0 0
  XPDR 0
END
ASEM:STS_Payloads\ASEM
  ASEM 0
  STATUS Landed Earth
  POS -117.8757450 34.9099416
  HEADING 60.62
  ALT 2.837
  AROT 0.000 -0.000 0.000
  ATTACHED 0:5,STS-49
  AFCMODE 7
  NAVFREQ 0 0
  XPDR 0
END
RAILPFR:RAILPFR
  YAWARM 0.5000
  ROTATION 0.5040
  PITCH 0.9938
  CPITCH 0.5000
  STATUS Landed Earth
  POS -117.8757408 34.9099320
  HEADING 60.62
  ALT 6.082
  AROT 0.000 -0.000 0.000
  ATTACHED 0:0,MPESS
  AFCMODE 7
  NAVFREQ 0 0
  XPDR 0
END
TUBEPFR:TUBEPFR
  YAWARM 0.4731
  ROTATION 0.5000
  PITCH 0.5512
  CPITCH 0.5000
  STATUS Landed Earth
  POS -117.8757529 34.9099495
  HEADING 60.62
  ALT 6.082
  AROT 0.000 -0.000 0.000
  ATTACHED 0:1,MPESS
  AFCMODE 7
  NAVFREQ 0 0
  XPDR 0
END
END_SHIPS

BEGIN_Attachment Manager
END
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,873
Reaction score
200
Points
153
Try renaming Shuttle2016Bearly_ecam.cfg to PAYLOADBAY_ecam.cfg. If what I'm suspecting is correct, then that should work. The problem could be that you're using this external vessel as the actual payload bay interior and not the main shuttle vessel itself. And make sure that the file extension really is .cfg and not .txt. To check this, in Windows Explorer, click on Display and then make sure File extensions is checked.
 

gattispilot

Addon Developer
Addon Developer
Joined
Oct 17, 2007
Messages
6,154
Reaction score
575
Points
188
Location
Dallas, TX
So in the scn The payload is just the extra stuff. like GAS,.... The Shuttle2016Bearly is the whole shuttle exterior, interior. Yes the ext is .cfg
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,873
Reaction score
200
Points
153
Just thought of something else. In SetMeshVisibilityMode make sure that EXT_PASS is enabled. The entire line should read as follows: SetMeshVisibilityMode(mesh_orbiter, MESHVIS_EXTERNAL | MESHVIS_VC | MESHVIS_EXTPASS);
 

gattispilot

Addon Developer
Addon Developer
Joined
Oct 17, 2007
Messages
6,154
Reaction score
575
Points
188
Location
Dallas, TX
Code:
mesh_orbiter = AddMesh(hOrbiterMesh);//mesh 1
    SetMeshVisibilityMode(mesh_orbiter, MESHVIS_EXTERNAL | MESHVIS_VC | MESHVIS_EXTPASS);
    
    
    If it matters the view is from the vc looking into the bay
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,873
Reaction score
200
Points
153
Then I don't know what might be wrong.
 

jarmonik

Addon Developer
Addon Developer
Beta Tester
Joined
Mar 28, 2008
Messages
2,128
Reaction score
99
Points
48
Website
users.kymp.net
PS: -6172 is the altitude in meters, shown on the DG MFDs

Ok, thanks. In my case the instruments show -3659 meters. I am downloading the latest elevation and texture maps. It seems that I got the "stock" (default) maps only for Mars in this installation. I saw 3km depth hole in the ground with -6172. I wonder how good idea it is to relay in a fixed value, would it be better to sample the elevation from the center of the ellipse or try to average it somehow ?
 

jarmonik

Addon Developer
Addon Developer
Beta Tester
Joined
Mar 28, 2008
Messages
2,128
Reaction score
99
Points
48
Website
users.kymp.net
It would be interesting to know what levels the function gets from the Orbiter collision core when you zoom in, so we would know what level the elevation is at vs. the level of the visual grid.

Code:
(220: 4.7s 35.18ms)(0x3F34) FilterElevation[Physics][Mars]: Level=7, ilat=54, ilng=31
(250: 5.7s 06.33ms)(0x3F34) FilterElevation[Physics][Mars]: Level=5, ilat=12, ilng=26
(251: 5.7s 00.80ms)(0x3F34) FilterElevation[Physics][Mars]: Level=5, ilat=12, ilng=26
(267: 5.9s 05.80ms)(0x3F34) FilterElevation[Physics][Mars]: Level=5, ilat=12, ilng=26
-------
(397: 7.2s 450.52ms)(0x2320) FilterElevation[Graphics][Mars]: Level=0, ilat=0, ilng=0
(398: 7.2s 00.08ms)(0x2320) TileCreatedFromFile: Level=0, ilat=0, ilng=0
(399: 7.5s 330.22ms)(0x2320) FilterElevation[Graphics][Mars]: Level=1, ilat=0, ilng=1
(400: 7.5s 00.09ms)(0x2320) TileCreatedFromFile: Level=1, ilat=0, ilng=1
(401: 8.0s 479.81ms)(0x2320) FilterElevation[Graphics][Mars]: Level=2, ilat=1, ilng=3
(402: 8.0s 00.08ms)(0x2320) TileCreatedFromFile: Level=2, ilat=1, ilng=3
(403: 8.4s 369.49ms)(0x2320) FilterElevation[Graphics][Mars]: Level=3, ilat=3, ilng=6
(404: 8.4s 00.08ms)(0x2320) TileCreatedFromFile: Level=3, ilat=3, ilng=6
(405: 8.5s 104.64ms)(0x2320) FilterElevation[Graphics][Mars]: Level=3, ilat=2, ilng=6
(406: 8.5s 00.06ms)(0x2320) TileCreatedFromFile: Level=3, ilat=2, ilng=6
(407: 8.6s 51.40ms)(0x2320) FilterElevation[Graphics][Mars]: Level=4, ilat=6, ilng=12
(408: 8.6s 00.13ms)(0x2320) TileCreatedFromFile: Level=4, ilat=6, ilng=12
(409: 8.6s 51.91ms)(0x2320) FilterElevation[Graphics][Mars]: Level=4, ilat=6, ilng=13
(410: 8.6s 00.10ms)(0x2320) TileCreatedFromFile: Level=4, ilat=6, ilng=13
(411: 8.8s 154.33ms)(0x2320) FilterElevation[Graphics][Mars]: Level=5, ilat=12, ilng=26
(412: 8.8s 00.12ms)(0x2320) TileCreatedFromFile: Level=5, ilat=12, ilng=26
(413: 8.8s 52.43ms)(0x2320) FilterElevation[Graphics][Mars]: Level=5, ilat=12, ilng=25
(414: 8.8s 00.09ms)(0x2320) TileCreatedFromFile: Level=5, ilat=12, ilng=25
(415: 9.0s 153.43ms)(0x2320) TileInterpolatedFromParent: Level=6, ilat=25, ilng=52
(416: 9.1s 101.97ms)(0x2320) TileInterpolatedFromParent: Level=7, ilat=50, ilng=104
(417: 9.2s 154.03ms)(0x2320) TileInterpolatedFromParent: Level=8, ilat=100, ilng=208
(418: 9.3s 103.08ms)(0x2320) TileInterpolatedFromParent: Level=9, ilat=201, ilng=417
(419: 9.4s 102.83ms)(0x2320) TileInterpolatedFromParent: Level=10, ilat=403, ilng=834
(420: 9.5s 50.49ms)(0x2320) TileInterpolatedFromParent: Level=10, ilat=403, ilng=835
(421: 9.5s 51.40ms)(0x2320) TileInterpolatedFromParent: Level=11, ilat=806, ilng=1669
(422: 9.6s 50.88ms)(0x2320) TileInterpolatedFromParent: Level=11, ilat=806, ilng=1670
(423: 9.6s 00.65ms)(0x2320) TileInterpolatedFromParent: Level=12, ilat=1612, ilng=3339
(424: 9.6s 51.16ms)(0x2320) TileInterpolatedFromParent: Level=12, ilat=1612, ilng=3340
(425: 11.3s 1710.41ms)(0x2320) TileInterpolatedFromParent: Level=6, ilat=25, ilng=51
(426: 11.5s 153.32ms)(0x2320) TileInterpolatedFromParent: Level=6, ilat=24, ilng=52
(427: 13.5s 2019.60ms)(0x2320) TileInterpolatedFromParent: Level=10, ilat=402, ilng=835
(428: 16.4s 2926.07ms)(0x2320) TileInterpolatedFromParent: Level=10, ilat=402, ilng=834
(429: 17.8s 1373.17ms)(0x2320) TileInterpolatedFromParent: Level=12, ilat=1612, ilng=3340
 

Face

Addon Developer
Addon Developer
Beta Tester
Joined
Mar 18, 2008
Messages
4,194
Reaction score
136
Points
88
Location
Vienna
Thanks for the info, Jarmonik. This looks like both physics and graphics filter level 8 at last (the level value obviously needs 3 added to represent the literature level value).
What I don't get: if level 8 is the last tile it filters for the visual grid, you have approx. 1,5km per elevation pixel on Mars at ca. 56° in there. Why is there actually a visual pancake with the 200m radius zero falloff example, then?
 

jarmonik

Addon Developer
Addon Developer
Beta Tester
Joined
Mar 28, 2008
Messages
2,128
Reaction score
99
Points
48
Website
users.kymp.net
What I don't get: if level 8 is the last tile it filters for the visual grid, you have approx. 1,5km per elevation pixel on Mars at ca. 56° in there. Why is there actually a visual pancake with the 200m radius zero falloff example, then?

That screen shot is likely from the previous version where the filter was applied to the interpolated (lvl 12-14) results as well. This problem should be fixed from the zip I attached a few post earlier (i.e. yesterday)
 

Face

Addon Developer
Addon Developer
Beta Tester
Joined
Mar 18, 2008
Messages
4,194
Reaction score
136
Points
88
Location
Vienna
Ah, that makes sense, yes. Level 14 would be 22m, which would explain the visible curvature of the pancake.
 

4throck

Enthusiast !
Joined
Jun 19, 2008
Messages
3,116
Reaction score
335
Points
108
Location
Lisbon
Website
orbiterspaceport.blogspot.com
That screen shot is likely from the previous version where the filter was applied to the interpolated (lvl 12-14) results as well. This problem should be fixed from the zip I attached a few post earlier (i.e. yesterday)

For the screenshots and tests I used the latest one. On loading Orbiter indicates R4.8 (Aug 20 2020)
 

4throck

Enthusiast !
Joined
Jun 19, 2008
Messages
3,116
Reaction score
335
Points
108
Location
Lisbon
Website
orbiterspaceport.blogspot.com
...sample the elevation from the center of the ellipse... ?

Being able to define desired elevation relative to the center of the ellipse would be good. And simpler to use.
Other calculations like area average, minimum or maximum altitude would also be useful. But only of they don't take time to implement.
I prefer a single functionality that works well and is well tested.
 

jarmonik

Addon Developer
Addon Developer
Beta Tester
Joined
Mar 28, 2008
Messages
2,128
Reaction score
99
Points
48
Website
users.kymp.net
There is a new build 4.9 out for Orbiter 2016 containing some fixes and adjustments to the terrain flattening.
It did pass all of my test scenarios pretty well. The deviation between physics and graphics should be no more than a few centimeters.
With very high resolution elevation (lvl 14-17) there seems to be some unknown issues. Also tiles where the "scale" factor is less than 1.0 are problematic since the physics seems to round it to nearest full meters.
 

4throck

Enthusiast !
Joined
Jun 19, 2008
Messages
3,116
Reaction score
335
Points
108
Location
Lisbon
Website
orbiterspaceport.blogspot.com
There is a new build 4.9 out for Orbiter 2016

Thanks! Works fine here :salute:

Tried with Ellipse -6162 -33.220001 19.129999 200 200 0 1
I'm raising terrain here about 10m so that we can see the results better.
Had to move the Pathfinder mesh a bit to match the flat area. That's expected because of coordinate / terrain point rounding.

Visual/physical surface match perfectly. I can drive around with no problems, and stop easily on the flat surface.

No complaints here, seems solid ;)
It's seamless if one uses realistic altitudes. Will be very useful for realistic terrain tweaks on the Apollo landing sites....


1598188979135.png
 
Top