New Orbiter Beta Released (r.13, Mar 7, 2015)

[Xyon]

Just wanted to note, the Orbiter Beta link on orbithangar.com now gives a 404.

Carry on.

Noted, I'll amend the link when I'm in there next.

 

[n122vu]

Noted, I'll amend the link when I'm in there next.

Just felt it was worth mentioning. Thanks.

It appears Time Warner may be throttling my torrent download (shocker!) of the Hi-res Earth textures. What was 3 hrs has now turned into 3d 21hr @ 68.7kB/s.

In the meantime, have managed to at least get up and running with lo-res Earth & Clouds. Can't wait to get a look at the hi-res for myself.

Thanks martins for this beta, and for all of your time & effort!

 

[martins]

I'm just wondering if this is the normal behavior for the moon textures at the moment?

I think getting the same issue as well and I downloaded the whole package for the Moon. They do not go away once the scene has settled and camera zoom doesn't make much of a difference.

I also have the artifacts described above, it seems like they occur at the edge, where the last terrain mesh-tile merges with the flat planet surface that loads far away from the camera.

OK, this is definitely not the intended behaviour. It looks as if below a certain resolution level no elevation data are loaded at all. Just to confirm: you all downloaded the low-resolution pack in addition to the high-res ones? If you look into Textures\Moon\Elev, do you see nine directories 04 to 12, each containing subdirectories, each of which containing *.elv files?

It's possible that I made a mistake when packaging the elevation files. I'll check it, but it may take me a little while, because I'm on a slow connection at the moment.

 

[Kyle]

I did originally download the low-resolution tiles for the Moon, however I do not see nine directories, I only see 09 to 12 with their respective subdirectories.

 

[martins]

I did originally download the low-resolution tiles for the Moon, however I do not see nine directories, I only see 09 to 12 with their respective subdirectories.

Oh boy, the Moon (and probably Mars) lores packages are incomplete. :blush:
I spotted the bug in my packager script. I'll upload a fixed version soon. Sorry about that.

 

[n122vu]

Confirmed, same thing definitely happening on Mars.

Probably related, but the Shuttle-A scenario "Olympus Spaceport on Mars" has the base structures floating in the middle of the sky far above the 3 landed vessels.

 

[Pipcard]

The higher-res graphics remind me of this

By the way, I think it should be possible to download the high-res textures and the elevation data separately? I mean, if I just want to view the prettiness of Earth from orbit, where the terrain isn't really that noticeable, and save a few dozen gigabytes in hard drive space. Or can I just delete the *\Textures\Earth\Elev folder?

edit: I see, the terrain of the mountain ranges is noticeable.

 

[martins]

I have now updated the Moon and Mars Low-res packages on Xyon's orbiter-radio.co.uk mirror. The updates should propagate to the alteaaerospace.com mirror by tomorrow.

Probably related, but the Shuttle-A scenario "Olympus Spaceport on Mars" has the base structures floating in the middle of the sky far above the 3 landed vessels.

No, that's related to the fact that for now bases are blissfully unaware of elevation, and stubbornly cling to sea level (if such a thing exists on Mars).

 

[Xyon]

I have now updated the Moon and Mars Low-res packages on Xyon's orbiter-radio.co.uk mirror. The updates should propagate to the alteaaerospace.com mirror by tomorrow.

This has completed. You'll also note I've made more unlinked md5sum files, MarsLo.zip.md5sum and MoonLo.zip.md5sum. These should help you verify you've got the new, complete file.

 

[4throck]

Just to say that it looks good on my end. The DG drives / lands / lifts off well in sloped terrain.
Did notice that for some reason it appears somewhat sunk. I guess that it needs some mesh offset.
But in general it behaves as it should.

Nice 2D VC for the Shuttle-A :tiphat:


May I suggest that bases that simply flatten the surface around the origin point up to a certain distance from center ?

 

[Loru]

May I suggest that bases that simply flatten the surface around the origin point up to a certain distance from center ?

Not sure if it's best idea. For example on the moon you can have base with landing pads at different elevations (few on the hill and few below them).

Yes - you could make it 2 bases but I think it will be better to adjust base handling to terrain than terrain to base. I know it's more work for base developers but I think it'd look better than every base on the flat dish.

My :2cents:

 

[Phoenix]

The terrain engine is brilliant. Well done, Martin. The frame rate is good on my almost 5-year-old laptop with integrated Intel graphics chip. The below images are using the low resolution dataset.

 

[fort]

Not sure if it's best idea

Hello,

To the question, "Do you know why a dog wags its tail when it is happy", it is not silly to to answer "because the tail can not wag the dog".

Otherwise, I gradually discovered this version and except a cloud a little square above Penemunde this morning, nothing to say beyond what has already been said. I like a lot.

However, three questions:
- a value of 0 (elevation above the ground) for a runway is not identical to a 0 value for a building? And what about the future of MapObjectsToSphere and object shadows ?
-. Pltex and .tex files, if i well understand it is over ?
- and, in a total confusion: what about D3D9 version from the team Jarmonik and this version ?

Thank you to all and thank you Docteur

 

[Phoenix]

I have one question, however, now that I have downloaded a patch of high resolution lunar terrain.

I have studied the lunar elevation data from LROC during a time when I was doing a bit of terrain rendering myself, and I found that the radar derived elevation data was not as good as the data derived from stereo imaging from the Wide Angle Camera (WAC). The radar derived data had frequent north to south running gaps. At these locations data was interpolated and looked a bit ugly. I think I am seeing this from a patch of terrain in Tsiolkovsky crater.

I have attached an image showing the central peak of the crater.



My apologies if I am wrong.

Thanks

 

[billeinstein]

Get Error while loading Scenarios
Oribiter.log:

**** Orbiter.log
Build Apr 16 2014 [v.140416]
Timer precision: 4.09589e-007 sec
Found 3 joystick(s)
Devices enumerated: 6
Devices accepted: 5
[ ] RGB Emulation (SW)
[ ] Direct3D HAL (HW)
[x] Direct3D T&L HAL (HW)
[ ] Direct3D HAL (NVIDIA GeForce 9800 GTX/9800 GTX+) (HW)
[x] Direct3D T&L HAL (NVIDIA GeForce 9800 GTX/9800 GTX+) (HW)
Module AtlantisConfig.dll .... [Build 140410, API 140412]
Module AtmConfig.dll ......... [Build 140412, API 140412]
Module DGConfigurator.dll .... [Build 140410, API 140412]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1674 x 1022 x 32
Graphics: Hardware T&L capability: Yes
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: 8
Loading 15382 records from star database
---------------------------------------------------------------
>>> ERROR: DDraw error DDERR_BLTFASTCANTCLIP
>>> [OrbiterGraphics::clbkBlt | .\OGraphics.cpp | 1556]
---------------------------------------------------------------

Error log in Windows event :

日志名称:          Application
来源:            Application Error
日期:            2014/4/20 18:38:15
事件 ID:         1000
任务类别:          (100)
级别:            错误
关键字:           经典
用户:            暂缺
计算机:           BillEinstein-PC
描述:
错误应用程序名称: orbiter.exe，版本: 0.0.0.0，时间戳: 0x534dfedc
错误模块名称: MSVCR90.dll，版本: 9.0.30729.6161，时间戳: 0x4dace5b9
异常代码: 0xc0000417
错误偏移量: 0x000512be
错误进程 ID: 0x2ad0
错误应用程序启动时间: 0x01cf5c84a165de40
错误应用程序路径: O:\mydoc\orbiterbeta\orbiter.exe
错误模块路径: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
报告 ID: e07d2c50-c877-11e3-a746-90e6ba1e2b75
事件 Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-04-20T10:38:15.000000000Z" />
    <EventRecordID>428170</EventRecordID>
    <Channel>Application</Channel>
    <Computer>BillEinstein-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>orbiter.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>534dfedc</Data>
    <Data>MSVCR90.dll</Data>
    <Data>9.0.30729.6161</Data>
    <Data>4dace5b9</Data>
    <Data>c0000417</Data>
    <Data>000512be</Data>
    <Data>2ad0</Data>
    <Data>01cf5c84a165de40</Data>
    <Data>O:\mydoc\orbiterbeta\orbiter.exe</Data>
    <Data>C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll</Data>
    <Data>e07d2c50-c877-11e3-a746-90e6ba1e2b75</Data>
  </EventData>
</Event>

CTD After this. Not back to launcher.
Orbiter_ng.exe can go without this error.

 

[fort]

For illustration, one of the Heathrow terminals.

With or without "objectsize" and with or without "MapObjectsToSphere" (only the values ​​of ground level of the HANGAR, in POS, whatever these choices, will differ) in the cfg:

...the...HANGAR
POS 23019.77 -105 -33793.57
SCALE 170 40 390
ROT -269.4
TEX1 osb2 10 2
TEX2 osb2 6 1
TEX3 Roof09 1 2
END

... successively placed at
POS xxx -125 -xxx, image2
POS xxx -115 -xxx, image3
POS xxx -105 -xxx, image4

... can not "join" the ground. At the low(s) positions in these trials (-125, -115), the lower part of the walls are as deleted, without thereby succes to put the building on the floor.

 

[fort]

At Canaveral:
standard POS: image1;
POS -30: image2.

 

[Loru]

As stated by Martins himself in first post bases are not implemented yet (they use legacy model which has to be reworked). Patience dear sir.

 

[Ripley]

I've also noticed many elevation issues around bases, but Martin said:

...[*] Planetary surface bases don't yet support the new elevation model. This is known and will be addressed in future betas. There is no need yet to file bug reports regarding this...

 

[fort]

As stated by Martins himself in first post, bases are not implemented yet

I've also noticed many elevation issues...

No, no: I read the previous messages from Martin Schweiger:

Planetary surface bases don't yet support the new elevation model. This is known and will be addressed in future betas. There is no need yet to file bug reports regarding this...

...and:

No, that's related to the fact that for now bases are blissfully unaware of elevation, and stubbornly cling to sea level (if such a thing exists on Mars).

but ... I thought it was possible to solve this problem locally:ninja:, by hand, by acting on the ground distance but...