Plane Fs22

0 views
Skip to first unread message

Magnhild Lachowicz

unread,
Aug 5, 2024, 4:35:44 AM8/5/24
to vallacarspick
similarto the other water plane pack, but it's a 20x20km square, there's a single black pole in the middle to make it possible to sell, you have one that's ground level, 1m above ground, 2m above ground and 10m above ground (that one is kinda useless unless your on hills lol)

Plane are used in FS22 animal feeders and drinkers. But they are not suitable for my models of feeders, they stick out on semicircular ones (I learned from one mapper that there is a script or an xml line that sets a changeable Scale when filling). And what it is and where to find it, I have no idea and I can't clarify it again from him.


In FS19 when tipping to ground I am almost sure it was the actual terrain that was used to create the heap by reducing the terrain size from unitsPerPixel="2" to unitsPerPixel="0.5" around the tip area


I think what he means is that a plane is visible at lower levels if the object the plane is supposed to be in, changes shape. For example an icecream cone shape, the plane is big at the top and would stick out either side at the bottom.


Just thought of another method using the vertex paint system, much like the snow density on roofs going from small to large, though whether this can be implemented without extra scripting I don't know


In the following example one plane is extruded 'upwards' (the left-hand one) and the other is extruded 'downwards' (the right-hand one). The 'upwards' plane has correct normals but the other has inverted normals.


When adding a Glass material the glass acts based on the Index of Refraction (IOR). For normal glass in air the IOR is usually around 1.45 - ie, the default setting for the glass. However, with the flipped normals the mesh actually behaves as if it is a cavity of air within a glass solid and this causes the "surface" to refract unexpectedly and behave as if the IOR is the inverse (in the case of an IOR of 1.45 it behaves as if the IOR is 1/1.45 - ie, 0.69).


I've got a question regarding the Airbus A320. When planning a flight in the main menu and selecting a VFR flight plan with more than 10,000ft in height, the navlog indicates that the selected aircraft (a320 neo) has a cruise speed of somewhere around 450kts.




450 knots is your airspeed over the ground; High in the air you're moving 350 knots.



If it's hard to understand, visualize the individual atoms of air. On the ground, they're close together. Up high, they're far apart. If your plane wants to hit 12 septillion particles each hour, it must move faster up high where the particles are further apart to do so. The number of particles your plane hits per hour is, arguably, called airspeed.


The Flight Management Computer has a Cost Index which tells the box to prioritize time (speed) at the expense of fuel burn. At a typical CI of 45 you would see climb speeds from 290 to the 320's based on weight, winds aloft and cruise altitude. As you reach the 33,000 to 37,000 feet where the 320 is happiest you will see your low speed cues "the hook" of VLS, Alpha Prot and Alpha Max come towards you as the Max Operating Mach comes down the airspeed indicator. The Green Dot is lift over drag max, which is optimum for climb rate and fuel efficiency (although it is slow in cruise - Only American Airlines pilots fly that speed during contract negotiations).


On departure I followed ATC instruction until it told me to resume own navigation. Seemed to be working fine but later I realised it was a coincidence that my heading was the same as my flight plan. When I got to my first VOR the aircraft started to turn but then just kept turning. Tried this a few times but same thing happened.


All to no avail. My autopilot is working ok because it cantrols all the other parameters, Speed, Hdg, Flight Level, etc. I mention Hdg because I've even tried GPS HDG (knowing that wasn't going to work)


Try opening up the GPS gauge and see how the plane is flying it. The current leg will be highlighted pink. It almost sounds like you've got an extra waypoint in the plan, or the plane is flying past a waypoint, but not close enough to it that it's not tripping to the the next leg. If it's the first, just take out that waypoint from your flight plan. If the second is what's happening, the plane will fly circles around the waypoint, trying to get close enough to it to trip to the next leg.


I've had that happen to me a couple of times, especially on take offs. i stray off the plan enough because the tower wants me to fly 'runway heading', then they will tell me to turn to..... and proceed, only to find out the waypoint we just far enough away that the plane started to circle around. I was able to get into the GPS and tell the plane to fly to the next waypoint. In cases where I have a crazy departure, I will set the GPS and NAV on about 30 seconds or so after I takeoff, and let the plane find it's way.

3a8082e126
Reply all
Reply to author
Forward
0 new messages