- add a skybox color (required making boundary around environment transparent)
- use CollisionHandlerPusher and spheres to detect collisions with obstacles
- add ability to walk backwards
- increase minimum distance between follow camera and terrain, to avoid clipping through
- make Ralph run slightly less ridiculously fast
Closes#565
Co-authored-by: rdb <git@rdb.name>
This isn't working properly at the moment, since the state gets set for the *next* object, causing significant artifacts. I wasn't entirely sure whether to restore the "proper" behavior or not, since applications may be relying on one or the other behavior, but enabling this feature for shaders is a minefield and it's a lot better to just tell people to use p3d_ColorScale instead.
This lets one use multiple ShaderTerrainMesh tiles effectively, with Panda automatically disabling ones that are certainly not in view. It may be worth an attempt to call `set_bounds_type(BoundingVolume::BT_box)` or set `bounds-type best` in Config.prc to get a tighter volume.
Rather than xforming after the fact, which does not work properly for boxes, we need to apply the transform to the vertices around which the box is generated.
Fixes#506
The copyright header was removed, apparently by mistake,
in c310c29a7712a06fe68fcb838b8c8a64caa5914b. I've put the
header back, carefully referencing the original to be
certain that I'm not inadvertently changing the copyright
status.
This is because building with tiff seems to have an issue on termux, and it's not actually necessary to build any of the image loaders on Android as we can use the built-in Android APIs.
- DisplayInformation now gives the list of display modes returned by XRRGetScreenResources if RandR 1.2 is supported, which is apparently more reliable than the previous XRRSizes/XRRRates approach.
- Switching fullscreen on X11 to the current resolution on the CRTC that the monitor is on will make the window cover the CRTC properly, rather than forcing the window to have an origin of (0, 0).
- Passing in the pipe's display width/height is commonly done to go fullscreen at native res, but this may not correspond to a real display resolution. It now detects when this is done, and interprets this as "go fullscreen at the native resolution on the current CRTC".
Fixes#575
