Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More PQSMods, LandControl and Rings #87

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

TheWhiteGuardian
Copy link

No description provided.

Copy link
Member

@DeltaDizzy DeltaDizzy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall Comments:

  • Currently h3 headings do not generate links.
  • Single-word headings do not need explicit tag declarations, though they are fine to leave in if you want
  • The razor pages and routing additions are needed.


AerialPerspectiveMaterial is a peculiar PQSMod. It appears to have no effect on the vertex height or color of the planet. Instead, it seems to partially configure the material of the planet's surface. It is suspected that the intent of this mod is to update certain shader parameters on every frame so as to correct any atmospheric effects.

## Example {#Example}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The anchor id ({#name}) is not needed, the C# side will autogenerate them based on the heading name.


|Property|Format|Description|
|--------|------|-----------|
|atmosphereDepth|Decimal|The altitude of the atmosphere in m.|
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use the full name (meters) in descriptions.

|atmosphereDepth|Decimal|The altitude of the atmosphere in m.|
|globalDensity|Decimal|Unknown, presumed to be an atmosphere density multiplier.|
|heightFalloff|Decimal|The PQSMod appears to calculate atmospheric density at the altitude of the camera. This parameter seems to control the density falloff with altitude. The suspected behavior is `localDensity = exp(-heightFalloff * observerAltitude)`.|
|oceanDepth|Decimal|The depth of the ocean in m.|
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use meters


The upshot is that parameters B and C essentially control the smoothness of the interpolation (possibly at the expense of actually passing through the height values recorded in the heightmap). Careless configuration may introduce unwanted artifacts, such as rippling effects around high contrast edges (IE what ought to be cliffs in the terrain) or blurring.

## Example {#Example}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heading ID unnecessary

}
```

## Properties {#Properties}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heading ID unnecessary

@@ -73,36 +75,83 @@ LandControl
}
```

## Parameters {#Parameters}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

heading ID unnecessary

@@ -112,9 +161,49 @@ Each `LerpRange { }` node describes a range of numbers to encompass, or lerp ove
|endEnd|Decimal|The true end of the LandClass coverage. Coverage before this point is sparse, while coverage after this point is non-existent.|

## Scatters {#Scatters}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Heading ID unnecessary (this slipped through the cracks when i purged them before)

## LerpRange {#LerpRange}
Each `LerpRange { }` node describes a range of numbers to encompass, or lerp over. These ranges are applied to each dimension. The image below describes the valid ranges for latitude and longitude, with a handy diagram at the bottom for a visual description of the coverage of the LandClass over a Float "dimension." Areas where coverage is not complete are determined by the `coverage___` properties.

![alttext](https://media.discordapp.net/attachments/717082915565076491/717506199100194876/LANDCONTROL.png)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably keep this image to illustrate it (I'll add it to the wiki repo directly)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants