View Single Post
Old 29 December 2019, 14:26   #5
VladR
Registered User

 
Join Date: Dec 2019
Location: North Dakota
Posts: 142
I hear ya with quick Build/Deploy (was in same boat myself) but Edit&Continue environment has sped up experimenting tremendously for me. Sometimes I finish some experiments in 2 hours which would be utterly impossible with constant rebuild/deploy.
Don't forget that a Visual Studio has 4 tabs with Watches and at any time you see up to 50 variables in one watch window. That's huge for productivity.
Then, as an added bonus, you see the Output Window below the source code, where you can dump several arrays worth of data, so you really always see every single variable at any time without any effort. The code kinda debugs itself...


Looks like you're trying to get all 3 aerodynamic properties going at the same time.

Why don't you first experiment with a simple linear decrease of atmospheric density (say, a lerp between MaxDensity and MinDensity based on your altitude) and adjust thrust/speed accordingly ? The Density could really be just a simple floating point value <0.25f, 1.0f>

Once you got maximum thrust/speed at highest altitude going, as a second step, add the dependency on the gravity:
- your highest thrust is when your direction vector is Down (0,-1,0) : Full Engine + Gravity
- your lowest thrust is when your direction vector is Up (0,+1,0) : FullEngine - Gravity

And you simply lerp the thrust between the two.


Only when the above is working, I would go and introduce the weight into the equations.
VladR is offline  
 
Page generated in 0.04300 seconds with 11 queries