Oolite Bulletins

One more expansion in the series of showcasing the latest Oolite planetary texturing capabilities. This time, we have Diso converted into the gas giant Jupiter, using a brand new 8k diffuse texture map.

The map used is taken from Bruce Murray's Space Image Library and is a merged image based on the Cassini map of Jupiter, with images of the poles from the Juno mission. This is probably the most up to date texture of Jupiter we have at this time. The original map was at 14k resolution and was scaled down to 8k for use in the game. The brightness of the original image was also lowered a bit to compensate for the pre-exposure applied by the game's shaders.

It makes Diso become this:






This expansion is licensed under CC BY 3.0. It is available for download from both the in-game Expansion Pack Manager and its page on the wiki.

Nice work, sir!

Are you planning to use Moon texture as the next example?
I'm assembling Leesti using 8k Moon diffuse and normal maps, so I'll present it if it will not clash with your's next plans.
Thank you for advice to setup red and green channels in normal map! It was very valuable info and I was prepared to do it in advance.

stranger wrote: ↑Sat Sep 12, 2020 12:19 am

Nice work, sir!

Thank you very much, glad you like it!

Are you planning to use Moon texture as the next example?
I'm assembling Leesti using 8k Moon diffuse and normal maps, so I'll present it if it will not clash with your's next plans.

Go ahead and deliver your version of the Moon. It does not clash with my plans at all. It will be great seeing fresh planets / moons content from expansion pack creators.

Well, I'll prepare my Moon for upload.

Awesome!

Who should be registered as the author for this expansion? Apparently, the manifest.plist contains noone...
https://ooliteproject.github.io/oolite- ... ter8k.html

That's mine.

another_commander wrote: ↑Sat Feb 17, 2024 1:45 pm

That's mine.

Do you mind if I update the oxz with that information?
What else could go into the manifest if I am at it anyway?

Sure, go ahead and update if you want.

Other info that might be filled in:
Tags: Ambience, Planets
Required Oolite Version: 1.90

That should be all I think.

another_commander wrote: ↑Sat Feb 17, 2024 6:04 pm

Sure, go ahead and update if you want.

Other info that might be filled in:
Tags: Ambience, Planets
Required Oolite Version: 1.90

That should be all I think.

Done. I was hesitating as for a moment the expansion vanished from the catalog. I have no found any reason but now it is back. Maybe a caching issue somewhere.

Since in many places the OXZ mention 1.89 as minimum required version I left it as it was.

I had to reload the oxz. You’d zipped it at the wrong level, so it was showing a bunch of nulls/blanks on the listing.

phkb wrote: ↑Mon Feb 19, 2024 7:49 am

I had to reload the oxz. You’d zipped it at the wrong level, so it was showing a bunch of nulls/blanks on the listing.

The nulls I noticed. What was the wrong level? How did you zip it correctly? And how did you notice so quickly something was wrong in first place?

Your zip file had a folder structure of: The OXZ format requires you to make it like this:

phkb wrote: ↑Mon Feb 19, 2024 12:15 pm

Your zip file had a folder structure of:

Code: Select all

DisoIsJupiter8k (folder)
   Config (folder)
   Textures (folder)
   manifest.plist
   requires.plist

The OXZ format requires you to make it like this:

Code: Select all

Config (folder)
Textures (folder)
manifest.plist
requires.plist

Ah, that is actually easy to spot. Usually I do not build archives via the GUI so I know where the mistake happened. When checking I focused on the content of the manifest - not it's location.

I was confused that the catalog generator consumed this invalid OXZ I created without complaints. This shall change.
But I am still interested: how did you spot it so quickly?

hiran wrote: ↑Mon Feb 19, 2024 1:57 pm

But I am still interested: how did you spot it so quickly?

I happened to be publishing some of my own updates, and was checking the OXP list page to make sure everything had gone through successfully. That's when I saw a line with "null" as the title.