seen from Netherlands
seen from Singapore
seen from United States
seen from Singapore
seen from Germany
seen from United States
seen from United States
seen from Colombia
seen from United States
seen from United States
seen from Singapore
seen from Netherlands
seen from Russia
seen from Malaysia
seen from Saudi Arabia
seen from Russia
seen from Australia
seen from Singapore
seen from United States
seen from Iraq
ENFJ trying to flirt with INTJ
INTJ: *Reading article on the cold war*
ENFJ: *Trying to get INTJ to pay attention to her*“So I heard INTJs are always thinking about world domination. Is that true for you?”
INTJ: *Without looking up* “No.”
ENFJ: *Smiling* “Really?”
INTJ: *Looks off into the distance with a crazed look on his face* “I would tear it down and start again”
ENFJ: …
Hi a while back I told you about float precision issues causing a camera jitter wth rigidbodys. You suggested that I use either a floating origin or use a static cockpit camera that doesn't move from the origin (like you use in Cockpit). Is it possible to get the source project to that please? I've been struggling to make anything work for the past month.
If you want to do a floating origin, then there’s not really any need for funky camera tricks like the disconnected cockpit I mentioned before. In the past when I needed a floating origin I used this script on the Unify wiki. I don’t know how up to date it is though, and a really cool thing is that as of 2018.2 you can now add support for LineRenderers and TrailRenderers using Get/SetPositions.
As for the disconnected cockpit, I can’t give you the source for that project because there’s a lot more in that project than just that stuff. Even if I wanted to, I didn’t bring that project with me, and it’s one of those that’s old enough that I don’t have it in an online repository.
However, my living situation in Prague has just been updated to include such luxuries as a table and chair, so I might look into doing a simplified and isolated version of it and then just uploading it to GitHub. It’d be a fun thing to do just to get back into the swing of things, and I’m kind of stuck in my flat at the moment anyway because I need to monitor the test flights of these laundry machines.
INTJ Caught
INFP: “Guys, I just saw ENFP and INTJ doing the weirdest thing”
*ENFJ and ENTP look up shocked
ENFJ: “Oh my god! what were they doing?”
INFP: “ENFP was dancing and INTJ was singing his heart out to The Lion Sleeps Tonight”
INFP: “When they noticed me, ENFP carried on dancing but INTJ was so embarrassed he walked out of the room and went home. He couldn’t even look me in the eye!”
ENFJ: *Turns to ENTP. “Please don’t”
ENTP: *Evil grin intensifies. “It must be done”
*ENTP gets up and walks towards INTJ’s apartment with a bounce in her step
You mentioned in one of your posts that you're writing a fancier engine script. The BMS falcon directory has a dat file for the F-16 versions that contain a thrust table (thrust = function(throttle, Mach number, altitude). That may be a good starting point for you. You could scale the thrust based on the nominal sea level static thrust you want to model. That's how I currently model thrust. I interpolate the table based on flight conditions. The thrust data is from NASA originally I think.
Oh wow! Very interesting! Thanks for the heads up. I’m having a bit of trouble understanding how to read it, but this is a great starting point for building a very simple engine model.
I haven’t written it yet, but it’s something I’ve been thinking about. The key features I’d like to get out of it are:
Thrust increases with speed
Thrust decreases with altitude
Thrust decreases with angle of attack
With those above, you have a jet engine model that is close enough in the same way that SimpleWings is close enough that you get a ton of realistic behavior when you use and set them up in a reasonable way.
Some bonus features, that might just be implementation specific:
Fuel flow rate affected by thrust
Thrust vectoring (optional, as it sometimes has undesirable physical implications)
Nice radar screen (guessing inspiration from BMS? :) ) How did you get the text to be so readable? Mine always looks blurry even when I use TextMeshPro. It ALWAYS looks better in the scene view than game view.
The radar screen and RWR are screenshots from the Falcon BMS manual. Nothing in that screenshot is functional, it’s just me testing visual ideas.
