Luqman_IDRISSI wrote:

awesome-llama wrote:

-snip-

I see. So if an expert like you took 10 whole months, a team of starters like me and 98129182 (possibly with more people contributing soon) might take 1-2 years. Anyways, how did you found all the calculations with high accuracy to ensure the flight simulator's realisticness?

winstonchurchill2020 wrote:

is your flight 737-flight simulator a kind of like a real plane drive (no cockpit though)? It's kind of hard, you know…

DMLL4305 wrote:

OK! Thanks for the clarification
Just some other things I want to know for clarification:
me^{\left(\left(\left(x+o\right)\cdot0.04879\right)-17.4\right)}\cdot1.2
For this equation the only numbers I need clarification on what they are for are : 1.2, 0.04879, and -17.4
me^{1.002+\left(\left(x+o\right)\cdot-0.004988\right)}\cdot2.1
For this equation the same thing: -0.004988, 2.1 and 1.002
Basically what do those numbers represent in the equation. (The ones I asked clarification for.)


Besides that, I should be OK, If I have any more questions I will contact you

Thanks for the helpful information!

DMLL4305 wrote:

Hey @awesome-llama

Another question:
How did you find/calculate the total frontal area for the 737-800? I started to calculate the frontal area of some parts of the 777-9 (Mainly the cockpit/nose area and the 2 turbofan engines) since I could not find any formulas or much helpful information, but I was not sure about the rest, and I don't want to put any guessed values in the simulator, How did you do yours? Did you find a website that had the Frontal area? Or is there a formula that I can use to calculate it?

Thanks.

awesome-llama wrote:

DMLL4305 wrote:

OK! Thanks for the clarification
Just some other things I want to know for clarification:
me^{\left(\left(\left(x+o\right)\cdot0.04879\right)-17.4\right)}\cdot1.2
For this equation the only numbers I need clarification on what they are for are : 1.2, 0.04879, and -17.4
me^{1.002+\left(\left(x+o\right)\cdot-0.004988\right)}\cdot2.1
For this equation the same thing: -0.004988, 2.1 and 1.002
Basically what do those numbers represent in the equation. (The ones I asked clarification for.)


Besides that, I should be OK, If I have any more questions I will contact you

Thanks for the helpful information!

They adjust the shape of the graph. What is important is that it is shaped correctly so that what you input (x axis, velocity) gets the right output (y axis, drag).

DMLL4305 wrote:

awesome-llama wrote:

DMLL4305 wrote:

OK! Thanks for the clarification
Just some other things I want to know for clarification:
me^{\left(\left(\left(x+o\right)\cdot0.04879\right)-17.4\right)}\cdot1.2
For this equation the only numbers I need clarification on what they are for are : 1.2, 0.04879, and -17.4
me^{1.002+\left(\left(x+o\right)\cdot-0.004988\right)}\cdot2.1
For this equation the same thing: -0.004988, 2.1 and 1.002
Basically what do those numbers represent in the equation. (The ones I asked clarification for.)


Besides that, I should be OK, If I have any more questions I will contact you

Thanks for the helpful information!

They adjust the shape of the graph. What is important is that it is shaped correctly so that what you input (x axis, velocity) gets the right output (y axis, drag).

OK! Thanks very much for that clarification and your outstanding help!
When I finish working on the 777-9 sim remix, do you mind if I put the link for you on your profile so you can see it?

awesome-llama wrote:

DMLL4305 wrote:

Hey @awesome-llama

Another question:
How did you find/calculate the total frontal area for the 737-800? I started to calculate the frontal area of some parts of the 777-9 (Mainly the cockpit/nose area and the 2 turbofan engines) since I could not find any formulas or much helpful information, but I was not sure about the rest, and I don't want to put any guessed values in the simulator, How did you do yours? Did you find a website that had the Frontal area? Or is there a formula that I can use to calculate it?

Thanks.

I had to guess it along with some of the details of the drag coefficient.

awesome-llama wrote:

DMLL4305 wrote:

awesome-llama wrote:

DMLL4305 wrote:

OK! Thanks for the clarification
Just some other things I want to know for clarification:
me^{\left(\left(\left(x+o\right)\cdot0.04879\right)-17.4\right)}\cdot1.2
For this equation the only numbers I need clarification on what they are for are : 1.2, 0.04879, and -17.4
me^{1.002+\left(\left(x+o\right)\cdot-0.004988\right)}\cdot2.1
For this equation the same thing: -0.004988, 2.1 and 1.002
Basically what do those numbers represent in the equation. (The ones I asked clarification for.)


Besides that, I should be OK, If I have any more questions I will contact you

Thanks for the helpful information!

They adjust the shape of the graph. What is important is that it is shaped correctly so that what you input (x axis, velocity) gets the right output (y axis, drag).

OK! Thanks very much for that clarification and your outstanding help!
When I finish working on the 777-9 sim remix, do you mind if I put the link for you on your profile so you can see it?

Go ahead.

Luqman_IDRISSI wrote:

awesome-llama wrote:

Luqman_IDRISSI wrote:

Well I wonder if me and 98129182 can actually defeat this flight simulator with our work in progress XFS320neo.

Also @awesome-llama, how long do you take to finish the Boeing 737-800 flight simulator?
Well getting the answer to that can help me estimate how many months it shall take to complete my flight simulator.

https://api.scratch.mit.edu/projects/341589959/

{"created":"2019-11-04T01:44:25.000Z","modified":"2021-02-23T12:05:46.000Z","shared":"2020-09-22T14:53:29.000Z"}

I created it on the 4th of November 2019. I shared it in the 22nd of September 2020. That is 10 months. It's the longest I have spent on a project. Most of them only take around 1 month.

I see. So if an expert like you took 10 whole months, a team of starters like me and 98129182 (possibly with more people contributing soon) might take 1-2 years. Anyways, how did you found all the calculations with high accuracy to ensure the flight simulator's realisticness?

when green flag clicked
say [wow]

DMLL4305 wrote:

Another thing I was just wondering, with how you use the Flight Data code to debug glitches on the Sim, do you have another private version of the Simulator that has a tool where you just paste the Data, and it recreates the scenario, and that's how you find bugs, or do you just use the Flight Data as a guide and manually try to recreate the scenario on the Sim? I know you can read what the data says, but I would think you would need not just the Data, but also an exact visual representation of the problem to see whats going on.

ExportedSimulation_(2021-3-4/7732)_v.1.6.2_alt:1910_ter.h:-3_spd:127_thr:5/5_pt:4_fl:0_sp:0_br:0_fuel:14235_wgt(t):69.2_a/t:arm_||_imp.spd:0_wthr:1_fps:16_zm:1%_t(s):43326_clone:168_x.pos(m):12852_||_route:ksfo-kord_||_lists_ptlc:0_terr:15048_stmp:40_||_len.exp:251

awesome-llama wrote:

DMLL4305 wrote:

Another thing I was just wondering, with how you use the Flight Data code to debug glitches on the Sim, do you have another private version of the Simulator that has a tool where you just paste the Data, and it recreates the scenario, and that's how you find bugs, or do you just use the Flight Data as a guide and manually try to recreate the scenario on the Sim? I know you can read what the data says, but I would think you would need not just the Data, but also an exact visual representation of the problem to see whats going on.

I can usually read them without importing. The code isn't that complicated. It is just an output of all the important variables. Here's one:

ExportedSimulation_(2021-3-4/7732)_v.1.6.2_alt:1910_ter.h:-3_spd:127_thr:5/5_pt:4_fl:0_sp:0_br:0_fuel:14235_wgt(t):69.2_a/t:arm_||_imp.spd:0_wthr:1_fps:16_zm:1%_t(s):43326_clone:168_x.pos(m):12852_||_route:ksfo-kord_||_lists_ptlc:0_terr:15048_stmp:40_||_len.exp:251

Note that I don't need to use every variable when trying to figure out something. I can ignore those and think about the basic position, speed and pitch.

Now, I do sometimes manually put this data in to the simulator to understand exactly what is going on.
For this, I use the command system which is available by holding space and pressing 0. There are many commands available (located in the stage if you want to see them all).

Now, I do sometimes manually put this data in to the simulator to understand exactly what is going on.

DMLL4305 wrote:

awesome-llama wrote:

DMLL4305 wrote:

Another thing I was just wondering, with how you use the Flight Data code to debug glitches on the Sim, do you have another private version of the Simulator that has a tool where you just paste the Data, and it recreates the scenario, and that's how you find bugs, or do you just use the Flight Data as a guide and manually try to recreate the scenario on the Sim? I know you can read what the data says, but I would think you would need not just the Data, but also an exact visual representation of the problem to see whats going on.

I can usually read them without importing. The code isn't that complicated. It is just an output of all the important variables. Here's one:

ExportedSimulation_(2021-3-4/7732)_v.1.6.2_alt:1910_ter.h:-3_spd:127_thr:5/5_pt:4_fl:0_sp:0_br:0_fuel:14235_wgt(t):69.2_a/t:arm_||_imp.spd:0_wthr:1_fps:16_zm:1%_t(s):43326_clone:168_x.pos(m):12852_||_route:ksfo-kord_||_lists_ptlc:0_terr:15048_stmp:40_||_len.exp:251

Note that I don't need to use every variable when trying to figure out something. I can ignore those and think about the basic position, speed and pitch.

Now, I do sometimes manually put this data in to the simulator to understand exactly what is going on.
For this, I use the command system which is available by holding space and pressing 0. There are many commands available (located in the stage if you want to see them all).

I see, Yes it is quite readable, zm is zoom, fps is frames per second, what does this one represent?: t(s):43326_clone:168_x.pos(m):12852 Does it represent the location of a terrain clone?
True, speed altitude and pitch will tell you if the plane is stalling, climbing, descending, or landing. Tells you what the plane is doing. That is if the glitch involves the airplane itself.

Now, I do sometimes manually put this data in to the simulator to understand exactly what is going on.

I knew it
For the command system, How do you exactly use it? Do you type in the required variables in the Flight data?
I will definitely take a look at the commands! I also found out that's where you put in the values for the Specifications

awesome-llama wrote:

DMLL4305 wrote:

I see, Yes it is quite readable, zm is zoom, fps is frames per second, what does this one represent?: t(s):43326_clone:168_x.pos(m):12852 Does it represent the location of a terrain clone?
True, speed altitude and pitch will tell you if the plane is stalling, climbing, descending, or landing. Tells you what the plane is doing. That is if the glitch involves the airplane itself.

Now, I do sometimes manually put this data in to the simulator to understand exactly what is going on.

I knew it
For the command system, How do you exactly use it? Do you type in the required variables in the Flight data?
I will definitely take a look at the commands! I also found out that's where you put in the values for the Specifications

t for time, s for seconds.
It is the current second in the day (in the project, not real life time). It's the value used to display the time on the chronometer and what sets the brightness of the world.

ss - set airspeed
sh - set height (altitude)
frz - freeze mode (basically "creative mode")
sf - set fuel
sp - set pitch
sx - set x position
st - set time
sz - set zoom (very useful, allows for extreme values too!)
repair - repair the airplane
weather - set weather
stats - get flight statistics

awesome-llama wrote:

DMLL4305 wrote:

awesome-llama wrote:

DMLL4305 wrote:

Another thing I was just wondering, with how you use the Flight Data code to debug glitches on the Sim, do you have another private version of the Simulator that has a tool where you just paste the Data, and it recreates the scenario, and that's how you find bugs, or do you just use the Flight Data as a guide and manually try to recreate the scenario on the Sim? I know you can read what the data says, but I would think you would need not just the Data, but also an exact visual representation of the problem to see whats going on.

I can usually read them without importing. The code isn't that complicated. It is just an output of all the important variables. Here's one:

ExportedSimulation_(2021-3-4/7732)_v.1.6.2_alt:1910_ter.h:-3_spd:127_thr:5/5_pt:4_fl:0_sp:0_br:0_fuel:14235_wgt(t):69.2_a/t:arm_||_imp.spd:0_wthr:1_fps:16_zm:1%_t(s):43326_clone:168_x.pos(m):12852_||_route:ksfo-kord_||_lists_ptlc:0_terr:15048_stmp:40_||_len.exp:251

Note that I don't need to use every variable when trying to figure out something. I can ignore those and think about the basic position, speed and pitch.

Now, I do sometimes manually put this data in to the simulator to understand exactly what is going on.
For this, I use the command system which is available by holding space and pressing 0. There are many commands available (located in the stage if you want to see them all).

I see, Yes it is quite readable, zm is zoom, fps is frames per second, what does this one represent?: t(s):43326_clone:168_x.pos(m):12852 Does it represent the location of a terrain clone?
True, speed altitude and pitch will tell you if the plane is stalling, climbing, descending, or landing. Tells you what the plane is doing. That is if the glitch involves the airplane itself.

Now, I do sometimes manually put this data in to the simulator to understand exactly what is going on.

I knew it :)
For the command system, How do you exactly use it? Do you type in the required variables in the Flight data?
I will definitely take a look at the commands! I also found out that's where you put in the values for the Specifications :)

t for time, s for seconds.
It is the current second in the day (in the project, not real life time). It's the value used to display the time on the chronometer and what sets the brightness of the world.

awesome-llama wrote:

awesome-llama wrote:

DMLL4305 wrote:

I see, Yes it is quite readable, zm is zoom, fps is frames per second, what does this one represent?: t(s):43326_clone:168_x.pos(m):12852 Does it represent the location of a terrain clone?
True, speed altitude and pitch will tell you if the plane is stalling, climbing, descending, or landing. Tells you what the plane is doing. That is if the glitch involves the airplane itself.

Now, I do sometimes manually put this data in to the simulator to understand exactly what is going on.

I knew it :)
For the command system, How do you exactly use it? Do you type in the required variables in the Flight data?
I will definitely take a look at the commands! I also found out that's where you put in the values for the Specifications :)

t for time, s for seconds.
It is the current second in the day (in the project, not real life time). It's the value used to display the time on the chronometer and what sets the brightness of the world.

Looks like I missed a question. My previous reply was done quite quick so I didn't see everything you asked.

The commands are all in the stage. It's a huge if-else script so you won't miss it.

So, the system works with the ask and wait blocks and the commands are set in that linear way. When the input box is opened up, you can first input the command name. I use shortened names because it is almost always going to be me using it.
The names like this:

ss - set airspeed
sh - set height (altitude)
frz - freeze mode (basically "creative mode")
sf - set fuel
sp - set pitch
sx - set x position
st - set time
sz - set zoom (very useful, allows for extreme values too!)
repair - repair the airplane
weather - set weather
stats - get flight statistics

So, if one of these were to be put in (except for repair, stats, and frz listed), a new inputs asks for the value to be set. If you want to set the speed, type ss in to the first input, press enter and in the second input, type in the speed you want to set. Remember, the simulator uses metric. The speed is put in as metres per second. You are from the US (I checked your profile), so I assume you are familiar with mph. 60 mph is 27 m/s. Also, a knot is roughly twice the value of metres per second for your information.

For the important parts of the flight data, e.g. position, airspeed, I will set those using the above commands.