OHM Spaceports v1.1

[OrbitHangar]

Author: igel

"Landscaping" surface bases for famous spaceports, to serve as a background for other historical addons. Dense area buildups (accurate to specifit time periods), mockups of the launch facilities (replacable by real launchpad "vessels" from the dependent historical addons), demo scenarios set in the isolated Solar System. Initial version includes only a few areas of Baikonur Cosmodrome, but may eventually be expanded to any area in any time period. Optimized for fast loading and smooth simulation performance in Orbiter 2010 with D3D9Client.



DOWNLOAD

 

[Cosmic Penguin]

igel AND Thorton both alive on O-F......and pushed out a new add-on that pushes Baikonur in Orbiter to the same high level standard as the Cape/CSG!?

Wow.

 

[IronRain]

Thank you very much!

 

[Delta glider]

Thank you!:thumbup:

 

[Interceptor]

Thanks igel,I have been waiting a long time for something like this.

 

[PhantomCruiser]

This looks gorgeous. A really nice bit of eye candy to enhance the experience.

 

[Cosmic Penguin]

Now I wonder if Plesetsk is in development? After all, that's the REAL secret R-7 missile and military base out there... :hmm:

 

[igel]

Plesetsk is definitely considered for future updates, but unfortunately it is the hardest of all R-7 sites, because its pads are hanging off the river bank. It was hard enough to approximate the 3D terrain shapes for current sites... So it is hard to estimate what may come first - Plesetsk terrain meshes or new Orbiter release with native support for 3D terrain.

 

[Cosmic Penguin]

Plesetsk is definitely considered for future updates, but unfortunately it is the hardest of all R-7 sites, because its pads are hanging off the river bank. It was hard enough to approximate the 3D terrain shapes for current sites... So it is hard to estimate what may come first - Plesetsk terrain meshes or new Orbiter release with native support for 3D terrain.

Yeah, I figured out that once I knew how the terrain there looked like.

Maybe you should try Vostochny first - don't worry I won't go into a hunger strike if this one didn't appear in Orbiter before its real inaugural launch. :rofl:

 

[Wolf]

I have got this....:hmm:

View attachment 13671

here is my logfile

**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 3.66623e-007 sec
Found 1 joystick(s)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module D3D9Client.dll ........ [Build 130512, API 100830]
Module OrbiterSound.dll ...... [Build 121120, API 100830]
Module Framerate.dll ......... [Build 100830, API 100830]
Module FlightData.dll ........ [Build 100830, API 100830]
Module ExtMFD.dll ............ [Build 100830, API 100830]
Module UnivPTG.dll ........... [Build 110305, API 100830]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module RPOP.dll .............. [Build 131222, API 100830]
Module ORBTGT.dll ............ [Build 140124, API 100830]
Module GPCMFD.dll ............ [Build 131213, API 100830]
Module DscovrMFD.dll ......... [Build 150205, API 100830]
Module AutoFCS.dll ........... [Build ******, API 050206]
Module transx.dll ............ [Build 100824, API 100823]
Module BaseSyncMFD.dll ....... [Build 100616, API 100603]
Module BurnTimeCalculator.dll  [Build 110227, API 100830]
Module GS2.dll ............... [Build 130106, API 100830]
Module STSGuidanceMFD.dll .... [Build 120225, API 100830]
Module RPOP_MFD.dll .......... [Build ******, API 060425]
Module VistaBoost.dll ........ [Build ******, API 060425]
VistaBoost 1.0: Warning: font smoothing already disabled; nothing to do.
Module SoyuzGuidanceMFD.dll .. [Build 120225, API 100830]
Module LaunchMFD.dll ......... [Build 130423, API 100830]
Module Attitude4MFD.dll ...... [Build 121004, API 100830]

**** Creating simulation session
D3D9Client: [DirectX 9 Initialized]
D3D9Client: Sytem has XNA math support
D3D9Client: [3DDevice Initialized]
D3D9Client: [Compiling Effects for Shader Model 3.0]
D3D9Client: [Loading Stars]
D3D9Client: [Loading Constellations]
D3D9Client: [D3D9Client Initialized]
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
ERROR in configuration file for Spaceports\Earth: Syntax error in SURFBASE list
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Finished initialising world
Finished initialising status
Finished initialising camera
Finished initialising panels
Finished setting up render state
D3D9Client: [Scene Initialized]
D3D9Client: [Session Closed. Scene deleted.]
**** Closing simulation session

what am I missing/done wrong?

do I have to delete the comments in the Earth.cfg file base list?....

 

[igel]

Not sure... Comments in the Earth.cfg should not be a problem: they indeed cause these 'ERROR' messages in the log file, but do not have any 'material' consequences to simulation. And I'd rather live with them - as the list of the bases in the config file will become totally unmaintainable without them.

I have three possible guesses. First, my D3D9Client is newer than yours: (Build 140930 in my log, Build 130512 in yours). Second, I have much-much shorter list of enabled external modules than you - so it may be possible that some other activated module is colliding with textures. Third, maybe the textures themselves got renamed/corrupted... did you deploy the Baikonur2010_SurfaceTiles_v1.0(101011) addon that contains the files referenced in the new Baikonur bases?

 

[Wolf]

did you deploy the Baikonur2010_SurfaceTiles_v1.0(101011) addon that contains the files referenced in the new Baikonur bases?

Negative Sir. No Baikonur addon installed other then yours

 

[igel]

Negative Sir. No Baikonur addon installed other then yours

Aha! Here it is: that addon is required as a prerequisite, it contains the actual surface tiles, my addon only references them (see the manual in the doc folder).

 

[Wolf]

Thank you igel! (my bad I haven't double checked the manual..) Problem fixed.
Wonderful addon :thumbup:

 

[geoair]

Have you planned an update to be able to use Vostok from this fantastic scenery ?

 

[igel]

Of course we plan... someday. It takes more time, so we did not want to delay the release "until the whole universe is included"

 

[geoair]

Thank you for the good news :thumbup:

 

[thammond]

No Earth Lables showing up in Visual Helper

I recently installed First in Space v1.0 and also installed at the same time, Baikonur 2010 Surface Tiles, and Spaceports v1.0 as recommended in First in Space document. I noticed for all the First in Space and Spaceport scenarios, I don't get any cities to show up on the surface of the earth.

I double checked to make sure that Surfaces was check marked in the Visual Helpers window and clicked on the config button. In the Configure Surface Markers window I select Earth for the Object, then the Labels box is empty. There is noting to select or deselect such as cities.

All the other standard or addon scenarios that I have tested, all have the normal options to select or deselect under Earth and the cities show up when selected.

I suspect that I messed up something during the installation. I don't recall what order I installed them for sure, but I think it was Baikounor, then Spaceports, and then First in Space. I remember one of them replaced many existing files, but don't remember which one. Does the order of installation matter?

Does anyone know what might be causing this, or how to fix it so I can get the surface labels to show up?

 

[igel]

What you see is correct (however strange it may seem), and your installation is perfect.

The reason you see different set of objects in Spaceports (and First in Space, and in R-9 addons) is that they all act in the "parallel universe" inside Orbiter. It is described in more detail in the manual. Orbiter allows such flexibility, to create "cleaner" environments for different groups of addons. In this case I use different Solar System, with separate model of Earth and Moon. Not only it speeds up scenario loading (without need to load distant planets) but also prevents loading other, mostly futuristic addons from getting into my historical landscapes (and, correspondingly, prevents my historical addons from polluting other futuristic environments).

The Earth used in the historical addons is - by default - cleaned from default bases, or markers or cities. Those are mostly used for features like radio comm simulations and airfields, not implemented in the histortical addons.

This 'separation' design is not carved in stone - it is possible to mix and match "parallel worlds" in Orbiter, or transfer addons from one Solar System to another. But it may not be that easy. For 'flyable' vessels, like in First in Space, all it takes it to modify the corresponding line for Solar System in scenario. But for a landscaping addon like Spaceports, the configuration file for Earth needs to be updated or copied to introduce directories for new bases - another strong reason for 'parallel universe', as I don't want to mess with everyone's default Earth .

I hope this explains the differences. If you want to bring missing Earth features to the Spaceports universe - you can copy them from the default Earth into custom Earth used by the addon.

 

[thammond]

Igel,

Thanks for the quick reply and explanation. So if I want the city markers or labels to show up in all the First in Space and Spaceports scenarios. Could I do that by coping the file CITIES.MKR located at ...config/earth/marker to ...config/spaceports/earth/marker?