I haven't posted here in a long long long time but there are some things OP can reconsider before teaching formulas:
If we're measuring tilt position, then we can use degrees. Since we're measuring distance travelled (walking is mainly based of finding optimal leg path per energy consumed, ie distance travelled per leg for a given W per sec or calories/joules) we should use radians
The other simpler way to properly calc elliptical motion is to use the rule of thumb - if we have π or float numbers from mult/div operations then we have to use radians (at least for more precision). If numbers are mainly integers, then use degrees
Motion losses induced by slipping, twisting or for example lack of symmetry makes results very unstable. Models should have very high precision in their design/construction to be deterministic in their movement. A week ago checked again and sadly can say that this SP engine still lacks stability in that area (even a perfect symmetrical designs tend to go at left or right). That's why elliptical motion makes models to go in one specific direction
Don't use ^ as power of number (pow) because some ppl don't know that it's bitwise exclusive OR. Better use (a * a) or something like pow(base, exponent)
@metaphysicalgnome I understand more or less what is written or spoken, but I speak it very poorly
Долу-горе разбирам какво е написано или се говори по ТВ, но много слабо го говоря.
After changing the system they changed the school program and drove us more in English, the Russian language was 3 years 2 hours a week
След като смениха системата го изместиха с английския, руския остана около 3 години по 2 часа през учебната седмица
If this isn't a 1st April joke, then I have one suggestion to you:
Move the whole downloadable content to torrent like - each copy of SP running can be used as nearest download source, including the site (it can be perfectly incorporated as subsystem in the game, a lot of popular titles use that shit)
Btw that amazing idea of banlisting airbrakes from future tournamets because "We have bug and don't know how to fix it" is a the real deal here. Then the flick why you added this part in the game without testing it? Hello?
@SuperSanic Relax bro ... My design failed at first match, and you know what - it was built for that. I was hoping for two crashes in a row, won a new machine because exactly 5 idiots bet against me that there's no bug in the engine. TL;DC (too lame, but don't care) a new ASUS WS C621E Sage Extreme Power motherboard + CPUs were ordered ;)
Ok, I'm almost out - no time to spare fixing the inadequate behavior of the autopilot. All are free to use my design from 2017's Daredevil tourney, only need a better balance of CoM/CoL for the tight corners (average run time 0:49-0:51):
@Jetpackturtle I'm wondering if the old dogs are still here. K1No seems gone, Zkillerwolfe too :| otoh you, Baldovino, ddwreck32, Kerbango and Tully2001 are still lurking
Sad thing that the bug with two unstable designs is still here. It's not possible to win against a little bit more shaking model than yours - seems engine skips calculations for changing position when an event occurs in calculations for the other's plane physics
@doge Multiple gyros won't exclude each other - first you are not forced to put gyros only at CoM ... the whole point of making stable rotorcraft is to have proper balance. Impossible when there is lack of correct autorotation physics in the game
Sorry to say it but don't bother with building a heli ... Game engine is very bad for VTOL from this type. Not possible to stabilize it even with enough gyros
Don't bother to suggest something about control surfaces. Their behaviour is far away from correct physics and they sill haven't an option to choose their hinge position
@jamesPLANESii I was 13 or 14 years old when learned about that. That's why I still remember the plane must have g sensors at or near CoM of each main part to get somewhat accurate data. This "counter" can be very hardly mounted even at plane's CoM
For example on one of my coworker's rc models there are at least seven 3-axis G sensors - two on the left/right side at the plane's CoM, two at each wing tip, three at the tail's (one per each stabilizer) and there was an optional for (behind) the camera on the nose
@TheDepressedPig Honestly dude, if you can't calculate ((a + g) / g) it's ur fckin problem to smile at creations like these while the game needs fixing and have better UI at least (to show g force as example). And no, I don't like putting the toxic word card on the table, it's not mature
WHY on Earth I need this when we have a formulas for G-Force? FFS use google if you can't remember or never learned that in school (I highly doubt it's the case here)
@Maximis Personally (and knowing the age of some benchmark sites/apps) I prefer to take the full advantage of a given software on a given hardware. If I manage to have the same deterministic result on slow and fast computer, I'll call it superb programming.
@AndrewGarrison
Care to share settings of the server (Windows performance settings and the game ones)? Let's make our PCs as similar as possible to the tournament's hardware/software environment
I second that. Using Slow Mo changes the behaviour, in fact your plane can crash when expected to clean some dangerous tight turn. Moving/changing the camera during flight also reflects on the simulation stability. Seems most stable camera is that in cockpit, followed by Orbit, then Chase
It went wrong once or two times when crashed but it was expected. A former co-worker and friend suggested that there's a chance the AI enters in something similar to gimbal lock but only for Roll or Pitch axis (probably Roll). In a broken autopilot design a very high speed model cannot be reoriented to point center of the ring. If this happens and the model is going to overshoot the ring, autopilot tries to fix that and usually crashes in two manners: vertically into the ground or horizontally into the rocky mountains, impossible to set proper Roll/Pitch angle
Your design tracks more smoothly and faster the ring center at very high speed
Sharing old data, still valid though - 1:20 with old model, I already tested it when 1.7 came; 248 test runs, 0 missed rings, 0 crashes. Sudden drop in fps or spike in cpu load makes the simulation unstable and plane crashed exactly 15 times from 100 runs. Ran at 100 and 120fps, more stable simulation, 2 crashes from 100 runs
Only upvoting because you still have the nerves to be here \o/
@AndrewGarrison Consider to remove the FPS cap and adding "Benchmark" feature in the main menu?
I haven't posted here in a long long long time but there are some things OP can reconsider before teaching formulas:
@metaphysicalgnome It was. Money talks everywhere :(
България
@metaphysicalgnome I understand more or less what is written or spoken, but I speak it very poorly
Долу-горе разбирам какво е написано или се говори по ТВ, но много слабо го говоря.
After changing the system they changed the school program and drove us more in English, the Russian language was 3 years 2 hours a week
След като смениха системата го изместиха с английския, руския остана около 3 години по 2 часа през учебната седмица
@metaphysicalgnome imma give you an upvotes too on Крокодила Гена и Електричка, both were part of my life
If this isn't a 1st April joke, then I have one suggestion to you:
Move the whole downloadable content to torrent like - each copy of SP running can be used as nearest download source, including the site (it can be perfectly incorporated as subsystem in the game, a lot of popular titles use that shit)
Just for the fun checked that instability of the engine while doing tests on tournament tracks is still here, even worse
What exactly was brought by this update to the users?
+1@Zkillerwolfe Working and preparing for the end of the world xD
@MAHADI !ROFLCOPTER
@MAHADI
Class: Prop ... So?
Btw that amazing idea of banlisting airbrakes from future tournamets because "We have bug and don't know how to fix it" is a the real deal here. Then the flick why you added this part in the game without testing it? Hello?
@Zkillerwolfe Sad loss, mate :D
This airbrake propulsion is one of the oldest exploits of the engine. Very weird that devs found it during a tournament xD
Should I join this tourney? Made some modifications on my model from the last Airstrip Drag which lowered medium time at 24-25s
Pro-tip: Reversed avionics+active suspension
@SuperSanic Relax bro ... My design failed at first match, and you know what - it was built for that. I was hoping for two crashes in a row, won a new machine because exactly 5 idiots bet against me that there's no bug in the engine. TL;DC (too lame, but don't care) a new ASUS WS C621E Sage Extreme Power motherboard + CPUs were ordered ;)
@AndrewGarrison Validation check, please. Decided to enter the tourney because found some issues with dimensions and wanna test my 'fix'
Ok, I'm almost out - no time to spare fixing the inadequate behavior of the autopilot. All are free to use my design from 2017's Daredevil tourney, only need a better balance of CoM/CoL for the tight corners (average run time 0:49-0:51):
Old White Hound
@Zkillerwolfe The sorrow of perfect(ly) flai... failing plane design
@AndrewGarrison Sorry, but what was the drawing frame rate limit used on the machine for the tournaments?
@Jetpackturtle Interesting ... didn't see him in the game or the chat (im still mod here and joined to watch if the server will make a poo)
@Jetpackturtle I'm wondering if the old dogs are still here. K1No seems gone, Zkillerwolfe too :| otoh you, Baldovino, ddwreck32, Kerbango and Tully2001 are still lurking
Sad thing that the bug with two unstable designs is still here. It's not possible to win against a little bit more shaking model than yours - seems engine skips calculations for changing position when an event occurs in calculations for the other's plane physics
+1Just tried some old model in latest 1.8 that makes it 0:49-55 and wondering if it's good? Don't know what changed here last 2 years ...
+1@mikoyanster This doesn't work in all designs and pixel perfect positioning is not my cup of coffee
Yeah, they should make setting the color per part instead of per type
@AndrewGarrison Seems CoM of aircraft is not calculated properly when the fuel is depleted and is a lot at take off time
@doge Multiple gyros won't exclude each other - first you are not forced to put gyros only at CoM ... the whole point of making stable rotorcraft is to have proper balance. Impossible when there is lack of correct autorotation physics in the game
Sorry to say it but don't bother with building a heli ... Game engine is very bad for VTOL from this type. Not possible to stabilize it even with enough gyros
Don't bother to suggest something about control surfaces. Their behaviour is far away from correct physics and they sill haven't an option to choose their hinge position
@jamesPLANESii I was 13 or 14 years old when learned about that. That's why I still remember the plane must have g sensors at or near CoM of each main part to get somewhat accurate data. This "counter" can be very hardly mounted even at plane's CoM
For example on one of my coworker's rc models there are at least seven 3-axis G sensors - two on the left/right side at the plane's CoM, two at each wing tip, three at the tail's (one per each stabilizer) and there was an optional for (behind) the camera on the nose
@TheDepressedPig Honestly dude, if you can't calculate ((a + g) / g) it's ur fckin problem to smile at creations like these while the game needs fixing and have better UI at least (to show g force as example). And no, I don't like putting the toxic word card on the table, it's not mature
WHY on Earth I need this when we have a formulas for G-Force? FFS use google if you can't remember or never learned that in school (I highly doubt it's the case here)
As I suggested the game needs autoversioning (incremental backup) w/o need to manually save
@Zkillerwolfe Yo, I noticed the same on my machines. As winner on this course your model shouldn't do that :\
+1Nope, doing my old hobby of building/repairing RC models.
+1My crashed also while even wobblier it never crashed in tests, so I moved on more interesting hobby than building virtual models
Seems I missed how my car crashed but whatever, that is rly my last tournament ...
@Maximis Personally (and knowing the age of some benchmark sites/apps) I prefer to take the full advantage of a given software on a given hardware. If I manage to have the same deterministic result on slow and fast computer, I'll call it superb programming.
@AndrewGarrison Can you make some tests on the machine with:
and post the results? To be sure that those benchmarks won't create performance problems, just clone the drive to a second one and install them on it
+1@AndrewGarrison
Care to share settings of the server (Windows performance settings and the game ones)? Let's make our PCs as similar as possible to the tournament's hardware/software environment
0:21-22, full reliability ... Some changes set the timer at 0:19
:}
Edit: Just for the lulz - 2 gallons are too much xD
I bought a tomatoes yesterday. Should I review them?
I second that. Using Slow Mo changes the behaviour, in fact your plane can crash when expected to clean some dangerous tight turn. Moving/changing the camera during flight also reflects on the simulation stability. Seems most stable camera is that in cockpit, followed by Orbit, then Chase
It went wrong once or two times when crashed but it was expected. A former co-worker and friend suggested that there's a chance the AI enters in something similar to gimbal lock but only for Roll or Pitch axis (probably Roll). In a broken autopilot design a very high speed model cannot be reoriented to point center of the ring. If this happens and the model is going to overshoot the ring, autopilot tries to fix that and usually crashes in two manners: vertically into the ground or horizontally into the rocky mountains, impossible to set proper Roll/Pitch angle
Your design tracks more smoothly and faster the ring center at very high speed
When the tournament bracket opened, I saved the model under the name 'Presto by ABC123 winner of Bandit Run'
Counting the crashes and the reason(s), found that this is the failest tournament in the history of SP. Glad I excluded myself from this bs*ery
I'm partially working in the industry and wil say that there's no net neutrality since the first website
Nope, fastest is 0:58 with no crashes on both lanes :}
Sharing old data, still valid though - 1:20 with old model, I already tested it when 1.7 came; 248 test runs, 0 missed rings, 0 crashes. Sudden drop in fps or spike in cpu load makes the simulation unstable and plane crashed exactly 15 times from 100 runs. Ran at 100 and 120fps, more stable simulation, 2 crashes from 100 runs