New Orbiter SVN commit (r.71, Oct 14 2017)

martins

Orbiter Founder
Orbiter Founder
Joined
Mar 31, 2008
Messages
2,352
Reaction score
8
Points
0
Website
orbit.medphys.ucl.ac.uk
New Orbiter SVN commit (r.81, Aug 22 2018)

I thought I'd start a new thread, since it's a new year, and the other thread got quite long already ...

There is a new beta out. Change log:
  1. TileManager: planet surface tiles now support user-defined mesh grid resolution (33/65/129) - as discussed in the micro-elevation thread
  2. Canaveral: shifted reference point to VAB
  3. Mars: modified atmosphere render parameters in config file
  4. Utils/tileedit: now requires Matlab R2015a runtimes (not included)
Note that there is also a new commit to OVP (r.44) to go with this beta. This implements point 1 in the D3D7 client.

Regarding point 1: to see the micro-elevation updates around Cape Canaveral as shown in the micro-elevation thread, you need to update your Earth textures. I have uploaded a texture diff here:

http://mirror.orbiter-radio.co.uk/orbiter/assets/packages/Earth/EarthHi_10_08_diff.7z

This should be unpacked in the Orbiter directory ("extract here") and allowed to overwrite existing tiles. Note that this requires the high-resolution Earth textures already installed (either the full texture set, or the 10/08 tile from the map picker in the beta texture repository).

Note that the micro-texture area is quite restricted at the moment to the region around the SLF and the VAB. I'll do more as I find time. There may also be some minor artefacts (visible seams at tile edges). That will be addressed.

The tile mesh grid resolution can be selected under

Extra | Visualisation parameters | Planet rendering options | Tile patch mesh resolution

Play around with it (and also with the tile resolution bias) and see how it affects the visual quality and frame rate. Note that this will not yet work in the D3D9 client until the developers add support.

Regarding point 3: this is in response to a previous discussion about the colour of Mars. The point was made that the atmosphere has an effect on the colour balance of Mars as seen from distance. I tried to replicate that with modified config settings for haze and fog. This has a subtle effect on the colour without modifying the surface textures.

Regarding point 4: I don't know if this has been noticed yet, but there is a tool available to inspect (and to some extent modify) texture tiles:

Utils\tileedit.exe

This has a GUI to display surface textures/water masks/nightlight textures/elevation data side by side. Mainly it allows you to navigate the tile quadtree and identify a particular tile. There is some rudimentary editing capability for elevation data (this is what I used for the Canaveral microtextures). It's still a bit rough and probably not very stable, but may be useful. It tends to take a while to start up.

Note that this is a compiled Matlab script. In order to run it, you need to install the Matlab R2015a runtimes. There is a readme file that provides details.
 

Loru

Moderator
Addon Developer
Donator
Joined
Sep 30, 2008
Messages
3,733
Reaction score
0
Points
36
Location
Warsaw
Quick and dirty but should work both in black and white backgrounds.

 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,769
Reaction score
31
Points
123
I think you left out the new Visualisation Parameters options in the Orbiter_NG executable as the below screenshot shows (Orbiter.exe on the left, Orbitre_NG on the right).

Also will there be a way for us add-on developers to edit the terrain in the actual release version? I ask because for example, the SLF runway is still pretty uneven when it is supposed to be very flat and smooth and the LC39 Crawlerway is very uneven, possibly exceeding the Crawler's 1.82 m jacking ability (each corner can jack up a maximum of 1.82 m independently of the other corners to keep its payload level at all times).

 
Last edited:

N_Molson

Addon Developer
Addon Developer
Donator
Joined
Mar 5, 2010
Messages
6,856
Reaction score
0
Points
0
Location
Toulouse
I ask because for example, the SLF runway is still pretty uneven when it is supposed to be very flat and smooth
A bumpy SLF sure seems a bit dangerous :lol:
 

martins

Orbiter Founder
Orbiter Founder
Joined
Mar 31, 2008
Messages
2,352
Reaction score
8
Points
0
Website
orbit.medphys.ucl.ac.uk
I think you left out the new Visualisation Parameters options in the Orbiter_NG executable as the below screenshot shows (Orbiter.exe on the left, Orbitre_NG on the right).
You are right. I had missed the fact that the render options dialog wasn't globally available, but only applies to the inline client.
I have now added the missing bits to the corresponding D3D7 client options dialog (OVP r.45), but this also means that those options will also have to be added to the appropriate D3D9 configuration interface (sorry guys). Until then you can edit orbiter_ng.cfg manually, using
PlanetPatchGrid = [4|5|6]
PlanetResolutionBias = [-2...2]

Also will there be a way for us add-on developers to edit the terrain in the actual release version? I ask because for example, the SLF runway is still pretty uneven when it is supposed to be very flat and smooth and the LC39 Crawlerway is very uneven, possibly exceeding the Crawler's 1.82 m jacking ability (each corner can jack up a maximum of 1.82 m independently of the other corners to keep its payload level at all times).
Is the SLF runway still bumpy even with the latest micro-elevation update and at patch grid resolution 65? That shouldn't really be the case anymore. (The crawlerway, on the other hand, hasn't been fully hand-edited yet).

In any case, as I said, the Utils\tileedit tool should allow you to edit the terrain data. Did you try it?
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,769
Reaction score
31
Points
123
Is the SLF runway still bumpy even with the latest micro-elevation update and at patch grid resolution 65? That shouldn't really be the case anymore. (The crawlerway, on the other hand, hasn't been fully hand-edited yet).
Yes, I even upped it to the max setting and the 15 end noticeable uneven. This can be demonstrated by simply loading the Delta-glider\DG-S ready for takeoff scenario and throttling up the main engines and let the DG do a run of the full length of the runway. One early hint of the SLF's unevenness is that the pitch angle begins to drop by several degrees. By the time you reach the touchdown zone markers for the 15 end the DG will begin to tumble and spiral out of control. The SLF should conform to the very curvature of Earth, it's that smooth.

In any case, as I said, the Utils\tileedit tool should allow you to edit the terrain data. Did you try it?
I tried it in the past but got nowhere with it due to a lack of documentation.
 
Last edited:

martins

Orbiter Founder
Orbiter Founder
Joined
Mar 31, 2008
Messages
2,352
Reaction score
8
Points
0
Website
orbit.medphys.ucl.ac.uk
This can be demonstrated by simply loading the Delta-glider\DG-S ready for takeoff scenario and throttling up the main engines and let the DG do a run of the full length of the runway. One early hint of the SLF's unevenness is that the pitch angle begins to drop by several degrees. By the time you reach the touchdown zone markers for the 15 end the DG will begin to tumble and spiral out of control. The SLF should conform to the very curvature of Earth, it's that smooth.
Are you sure this isn't just a resonance instability due to overspeed? If you keep the speed below 200m/s, everything seems to remain rock stable until you hit the ditch at the end of the runway.
 

DaveS

Space Shuttle Ultra Project co-developer
Addon Developer
Donator
Beta Tester
Joined
Feb 4, 2008
Messages
8,769
Reaction score
31
Points
123
Are you sure this isn't just a resonance instability due to overspeed? If you keep the speed below 200m/s, everything seems to remain rock stable until you hit the ditch at the end of the runway.
OK, so I did a number of runs and as you wrote, as long as the speed was below 200 m/s everything remained level.
 

Post much?

New member
Joined
Sep 10, 2009
Messages
28
Reaction score
0
Points
0
Grid resolution 129 with maximum quality:



If this is what it looks like with the LOLA-only data, imagine the Terrain Camera DTM!
 

TCR_500

Developer of Solar Lander
Joined
Mar 3, 2009
Messages
580
Reaction score
0
Points
16
Website
www.tchapman500.com
Grid resolution 129 with maximum quality:



If this is what it looks like with the LOLA-only data, imagine the Terrain Camera DTM!
That would kill my GPU for sure. I never thought I'd see the day when Orbiter would become resource hungry without mods.
 

Post much?

New member
Joined
Sep 10, 2009
Messages
28
Reaction score
0
Points
0
This was made with only the onboard HD4600 of my i5 :)
I got roughly the same FPS martins did at the same settings.
 

turtle91

New member
Joined
Nov 1, 2010
Messages
303
Reaction score
0
Points
0
That's the textures I have used.
I installed all the low-res packs + one hires-tile for KSC.
Looks nice :thumbup:
 

GZR_Ranger

New member
Joined
Feb 15, 2013
Messages
11
Reaction score
0
Points
0
XR-2 issues with r.45 Beta

Hi. I'm not an expert, and could use some expert help! I see from other posts that several of you have the XR-2 working in the beta, but I'm having trouble. I hope it's something simple that I'm screwing up!

Due to the blizzard the east coast of the USA is having, I took time today to download the new beta. My last install (r.43) was CTD'ing, so this time I installed everything one-at-a-time and started Orbiter after each was installed:

  1. Orbiter Beta r45 (hires textures copied form older version)
  2. EarthHi_10_08_diff.7z
  3. D3D9ClientBeta15-forRev45.zip
  4. IMFD55.zip
  5. OrbiterSound40_20121120_setup.exe
  6. UCGO30_2010_20140109.exe
  7. XR2Ravenstar-1.6a.zip
  8. XR2Ravenstar-1.7-beta.zip

After the XR-2 install, Orbiter now CTD's shortly after initiating any scenario (even if it's not an XR-2 scenario).

Thank you!

From XR2Ravenstar.log
Code:
01.23.2016 17:14:44.424 - [] Loading XR2Ravenstar: Version 1.7 BETA-1, Build Date: Jul 22 2013
01.23.2016 17:14:44.475 - [XR2-01] Using configuration file(s): Config\XR2RavenstarPrefs.cfg (no override found [Config\XR2-01.xrcfg])
01.23.2016 17:14:44.475 - [XR2-01] Parsing config file 'Config\XR2RavenstarPrefs.cfg'
01.23.2016 17:14:44.510 - [XR2-01] Successfully parsed configuration file 'Config\XR2RavenstarPrefs.cfg'
01.23.2016 17:14:47.904 - [XR2-01] Using UMmu Version: 3.00
01.23.2016 17:14:50.076 - [XR2-01] Using OrbiterSound Version: 4.00
01.23.2016 17:14:52.052 - [XR2-01] Autodetected video window width: 1360 pixels
From Orbiter.log
Code:
**** Orbiter.log
000000.000: Build Jan 20 2016 [v.160120]
000000.000: Timer precision: 3.94741e-007 sec
000000.000: Found 0 joystick(s)
000000.000: Module AtlantisConfig.dll .... [Build 150906, API 150906]
000000.000: Module AtmConfig.dll ......... [Build 150906, API 150906]
000000.000: Module DGConfigurator.dll .... [Build 150906, API 150906]
000000.000: Module D3D9Client.dll ........ [Build 160121, API 160120]
000000.000: Module InterMFD55.dll ........ [Build 100826, API 100704]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiRegisterMFDMode
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Module OrbiterSound.dll ...... [Build 121120, API 100830]
000000.000: 
000000.000: **** Creating simulation session
000000.000: D3D9Client: [DirectX 9 Initialized]
000000.000: D3D9Client: Sytem has XNA math support
000000.000: D3D9Client: [3DDevice Initialized]
000000.000: D3D9Client: [Loading Stars]
000000.000: D3D9Client: [Loading Constellations]
000000.000: D3D9Client: [D3D9Client Initialized]
000000.000: Attempting to clear a texture 0x7319680 color=0x0
000000.000: Module Sun.dll ............... [Build 150906, API 150906]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
000000.000: Module Mercury.dll ........... [Build 150906, API 150906]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
000000.000: Module Venus.dll ............. [Build 150906, API 150906]
000000.000: Module VenusAtm2006.dll ...... [Build 150906, API 150906]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
000000.000: Module Earth.dll ............. [Build 150906, API 150906]
000000.000: Module EarthAtm2006.dll ...... [Build 150906, API 150906]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
000000.000: Module Moon.dll .............. [Build 150906, API 150906]
ELP82: Precision 1e-005, Terms 116/829
000000.000: Module Mars.dll .............. [Build 150906, API 150906]
000000.000: Module MarsAtm2006.dll ....... [Build 150906, API 150906]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
000000.000: Module Phobos.dll ............ [Build ******, API 060425]
000000.000: Module Deimos.dll ............ [Build ******, API 060425]
000000.000: Module Galsat.dll ............ [Build 150906, API 150906]
000000.000: Module Jupiter.dll ........... [Build 150906, API 150906]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
000000.000: Module Io.dll ................ [Build 150906, API 150906]
000000.000: Module Europa.dll ............ [Build 150906, API 150906]
000000.000: Module Ganymede.dll .......... [Build 150906, API 150906]
000000.000: Module Callisto.dll .......... [Build 150906, API 150906]
000000.000: Module Satsat.dll ............ [Build 150906, API 150906]
000000.000: Module Saturn.dll ............ [Build 150906, API 150906]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
000000.000: Module Mimas.dll ............. [Build 150906, API 150906]
SATSAT Mimas: Terms 113
000000.000: Module Enceladus.dll ......... [Build 150906, API 150906]
SATSAT Enceladus: Terms 33
000000.000: Module Tethys.dll ............ [Build 150906, API 150906]
SATSAT Tethys: Terms 101
000000.000: Module Dione.dll ............. [Build 150906, API 150906]
SATSAT Dione: Terms 59
000000.000: Module Rhea.dll .............. [Build 150906, API 150906]
SATSAT Rhea: Terms 68
000000.000: Module Titan.dll ............. [Build 150906, API 150906]
SATSAT Titan: Terms 100
000000.000: Module Iapetus.dll ........... [Build 150906, API 150906]
SATSAT Iapetus: Terms 605
000000.000: Module Uranus.dll ............ [Build 150906, API 150906]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
000000.000: Module Miranda.dll ........... [Build ******, API 060425]
000000.000: Module Ariel.dll ............. [Build ******, API 060425]
000000.000: Module Umbriel.dll ........... [Build ******, API 060425]
000000.000: Module Titania.dll ........... [Build ******, API 060425]
000000.000: Module Oberon.dll ............ [Build ******, API 060425]
000000.000: Module Neptune.dll ........... [Build 150906, API 150906]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
000000.000: Finished initialising world
000000.000: Module XR2Ravenstar.dll ...... [Build 130722, API 130101]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::CreateVariableDragElement
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
000000.000: Module ShuttleA.dll .......... [Build 151205, API 151205]
000000.000: Module ShuttlePB.dll ......... [Build 150906, API 150906]
000000.000: Module DeltaGlider.dll ....... [Build 160120, API 160120]
000000.000: Module LuaInline.dll ......... [Build 150906, API 150906]
000000.000: Finished initialising status
000000.000: Finished initialising camera
000000.000: Finished setting up render state
000000.000: WARNING: No texture data found for Mars (TileFormat = 2)
000000.000: D3D9Client: [Scene Initialized]
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: oapiBlt
000000.000: Colour key argument not supported by graphics client
000000.000: ---------------------------------------------------------------
000000.000: Finished initialising panels
000000.000: ---------------------------------------------------------------
000000.000: >>> WARNING: Obsolete API function used: VESSEL::GetHorizonAirspeedVector
000000.000: At least one active module is accessing an obsolete interface function.
000000.000: Addons which rely on obsolete functions may not be compatible with
000000.000: future versions of Orbiter.
000000.000: ---------------------------------------------------------------
 
Top