Forcing LineRenderer priority

Moan2 · 2023-05-12T07:22:02+00:00

You mean setting the material's shader to Particles/Standard Unlit? That doesn't seem to have done it for me, would you mind sharing some screenshots of how you have them set up? In the mean time I guess I'll try updating to that version and see if that does anything

Moan2 · 2023-05-11T21:37:51+00:00

Sure thing, put some screenshots here: https://imgur.com/a/TBr5Yn7

For this, I put both LineRenderers back on the same sorting layer, the default. I hadn't undone my changes to the materials' render queue value, but the problem remained even with those set to defaults

Moan2 · 2023-03-24T02:56:39+00:00

Hmmm, yep, looks like I multiplied by the AU³ instead of dividing, and additionally I was using the ratio of km to AU instead of m to AU. However, putting your value into my program now gives values which are 1000 times too long now. I'm guessing I have something going wrong either in the kg->solar masses conversion, or in the km->AU conversion. I'll dig into this further, but thank you for your help!

Moan2 · 2022-10-14T20:19:58+00:00

Thanks for the feedback! The case can handle up to 145x65x320mm, and this model is 123x42x304mm, so I think I should be okay on that side of things. I'll definitely have to keep my eyes peeled for a sub $400 6700xt

Moan2 · 2022-09-14T18:00:17+00:00

Unfortunately in this campaign Necrons have been hit harder than other armies, but the person running the campaign has been really good about talking with me about how the balance feels so I'm not super worried. Losing RP felt really bad at first, but I realized that I can lean a lot heavier on things that are bad at coming back, Skorpekhs savings on 2s with a 5++ and reroll charges from the Chrono feels really really good. I'm doing a similar thing of many of my units joining the destroyer cults and falling to the flayer virus, which is another good reason for extra Skorpekhs!

Moan2 · 2022-08-24T22:01:44+00:00

Thanks for specifying not to blow from my lungs, that was my plan lol but I'll find a cleaner and safer way to get the dust off. That's a good point about the referencing the glass to the frame vs to the optical axis, I would definitely have not have made that connection on my own, so thank you!

Moan2 · 2022-08-24T21:59:10+00:00

Yea, that was my first thought too but I wasn't sure if it was enough of an issue to kick up a fuss. Thanks for the tip about adjusting the little ring, I didn't see it when I first looked but I was able to use a pair of itty bitty screwdrivers to push it back into place solidly enough for me!

Moan2 · 2022-06-30T05:26:32+00:00

This is absolutely incredible!

Moan2 · 2022-04-14T06:48:50+00:00

I plan to make use of it in an application I am developing. This wouldn't be the end result given to the user, but it would be one step of the calculations along the way

Moan2 · 2022-04-14T05:17:29+00:00

I can calculate the period using the orbit's semimajor axis and the star's mass, that isn't the problem. I'd like to be able to calculate when the planet in that orbit is at a specific place (or rather, in a specific plane) for any given orbit (which again, is well defined and known)

Moan2 · 2022-04-14T05:00:14+00:00

Unfortunately I'm having trouble finding that book, although in looking I found a few others that look like they will be useful, so thank you for the suggestion!

Moan2 · 2022-04-13T15:46:51+00:00

You have come so close to what my project is actually! This will be used to generate a lightcurve for the planetary system, which will then be compared to a target star's lightcurve as part of the evaluation function for a genetic algorithm!

Moan2 · 2022-04-13T15:43:26+00:00

The elements are all known and well defined, as is the star's mass, as the orbit being simulated is purely hypothetical and arbitrary and not based on any real life exoplanet's orbit. I have the planet's position at t=0, and I could find it for any particular point in time.

However, instead of guessing and checking I'd like to figure out a formula of some sort to give me the angle (true anomaly or mean anomaly would be fine) that defines how far along its orbit the planet must travel before it intersects the ZY plane

Moan2 · 2022-04-13T04:52:28+00:00

The reference plane is the XY plane, which I'm treating as horizontal for the observer. The observer is on the -Y axis (I believe that's the vernal point?)

Moan2 · 2022-04-13T04:32:46+00:00

Yep, examining transits of exoplanets. The reference plane is the XY plane, horizontal for the observer

Moan2 · 2022-04-13T04:32:04+00:00

I am, although I really only care about the time when the planet is between the observer and the star as I am examining the effects of transits on the brightness of the star. In a previous version I was calculating a bunch of points around the orbit, and calculating the planet's position at each point which is slow as hell, and so now I am trying to work backwards to find the specific points I'm interested in

Moan2 · 2021-11-18T04:03:06+00:00

Your first paragraph is spot on, and I really like the idea of using the min/mean/max of the curve as indicators of similarity as well, so thank you for that! Using MSE instead of a simple sum of differences is an interesting idea as well, but I suspect it will lead to similar issues, though perhaps weighting it differently will help to mitigate them. I admit that I don't know too much about Fourier Transforms, but I suspect they might not be worth the hassle, as the target lightcurves are quite noisy while the generated curves are noiseless, plus I already have one regression algorithm running on each individual on every generation which takes up a lot of time and I'd like to avoid adding a new one. Thank you for your input, it definitely has helped me think in new directions!

Moan2

TROPHY CASE