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

Round firemarbles #71

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Round firemarbles #71

wants to merge 1 commit into from

Conversation

Hazado
Copy link
Contributor

@Hazado Hazado commented Aug 21, 2021

Changed the firemarbles in Relto, Neighborhood and Kirel to be actually round.

@Hoikas Hoikas added conflict This pull request modifies binary files in a way that conflicts with history or other pull requests technical An issue or fix that is primarily technical labels Aug 21, 2021
@Hoikas
Copy link
Member

Hoikas commented Aug 21, 2021

Conflicts with #65

Relto
[Generic Physical - MarblePhy06] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy07] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy08] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy09] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy10] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"

Neighborhood
[Generic Physical - MarblePhy01] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy02] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy03] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy04] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy06] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy07] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy08] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"

Neighborhood2
[Generic Physical - MarblePhy01] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy02] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy03] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
[Generic Physical - MarblePhy04] Changed Bounds to kSphereBounds with Radius of "0.75" and Vector of X="0" Y="0" Z="0", Changed Friction to "1" and Mass to "4"
@Hoikas
Copy link
Member

Hoikas commented Aug 28, 2021

Based on discussion on discord, this is currently blocking on visual issues with the firemarbles. The ViewFaceModifiers seem to rotate in the "opposite" direction of the physical movement with this change applied. While the marbles tend to roll on a more realistic way with this change, the VFM problem is rather disorienting, so we should not accept until this is corrected.

@ZarothYe
Copy link
Contributor

ZarothYe commented Jun 5, 2022

I don't fully understand what it would take for the VFM issue to be resolved, but this PR will need to be rebased at the very least since there have been Neighborhood and Relto changes in the past 10 months. I imagine it will need to be rebased yet again after all the pending Relto page PRs, too. Or, if it's not likely to be able to be completed any time soon, perhaps this needs to be closed or moved to draft state until someone can pick this back up.

@Hazado Hazado marked this pull request as draft June 5, 2022 15:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conflict This pull request modifies binary files in a way that conflicts with history or other pull requests technical An issue or fix that is primarily technical
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants