There seems to be an up tick in Political commentary in recent months. Those of us who are long time members of the site we know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religiours commentary out of the fourms.
If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.
Please note any post refering to a politicion will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment amoung members. It is a poison to the community. We apprciate compliance with the rules.
The Staff of SOH
As long as keep a few things in mind, the electrical system is actually very docile...
Dead radios are caused by the MSFS-internal battery draining because the MSFS-internal alternators are - by default - not connected to the MSFS-internal engines. That was my very first fix and the generators are now always active. The battery will still drain if the engines are not running.
The systems and indicators freezing up despite there being elelctrical power is either due to a bug or due to generator overload. In any case, the "Connect Lock" button on the elctrical panel will fix it.
If you've got too much stuff on the electrical buses you can't start up the APU anymore, but that's okay if kept in mind during operation.
Roll back the edits you need to do for the Load/Save mod if you actually want that stuff back in.
I won't touch it.
For the last time: I AM NOT REBUILDING THE F'IN 2D PANELS. End of discussion.
I doubt it. It was an edit akin to replacing "(Variable) 0 > if{...}els{...}" with "(Variable) 1 == if{...} (Variable) 0 == if{...}". Same result, but more explicitly expressed.
Whatever the motivation for the original edit, I totally concur with it. I've never liked writing "||" for "or" and "&&" for "and".
Nope, didn't change. Quite peculiar as one could have simply used a custom animation powered by an "L:" var. But I don't mind, it's fixed now.
I'm still not much of a fan for going a completely separate route from the default MSFS autopilot systems (as they have very good PID controllers), but whoever did this did a commendable job because autoland works.
Payload points did not change from the FS9 version.
[weight_and_balance]
max_gross_weight = 108026.5
empty_weight = 65978
reference_datum_position = 0, 0, 0
empty_weight_CG_position = -6.75.000, 0, 0
empty_weight_pitch_MOI = 3000000
empty_weight_roll_MOI = 1800000
empty_weight_yaw_MOI = 3000000
empty_weight_coupled_MOI = 0
max_number_of_stations = 50
station_load.0= "176.000, 54.95, 0.000, 0.000, ШТУРМАН"
station_load.1= "530.000, 48.79, 0.000, 0.000, ЭКИПАЖ"
station_load.2= "12566.000, 5.91, 0.000, 0.000, 76 ПАСС"
station_load.3= "253.532, 34.45, 0.000, 0.000, б/ПР+ПРОД"
station_load.4= "143.400, -21.98, 0.000, 0.000, б/ПР/ЗАД"
station_load.5= "1322.774, 42.01, 0.000, 0.000, ПЕРЕД/БАГ"
station_load.6= "3968.321, -27.72, 0.000, 0.000, ЗАДН/БАГ"
[weight_and_balance]
max_gross_weight = 108026.5
empty_weight = 65978
reference_datum_position = 0, 0, 0
empty_weight_CG_position = -5, 0, 0
empty_weight_pitch_MOI = 3000000
empty_weight_roll_MOI = 1800000
empty_weight_yaw_MOI = 3000000
empty_weight_coupled_MOI = 0
max_number_of_stations = 4
station_load.0 = "680, 43, 0, 0, Crew"
station_load.1 = "0, 0, 0, 0, Passengers"
station_load.2 = "0, 35, 0, 0, Front Baggage"
station_load.3 = "0, -25, 0, 0, Rear Baggage"
Nope, can't be fixed. The clickspots are invisible polygons in the model file.
Native FSX models (*) could simply declare the entire selector as clickable without any tricks.
*Probably FS9 models as well. It's been a while.
It's clickable alright, but it doesn't seem to affect any variable.
Adding a "Cold&Dark" button to get your stupid cold&dark condition back in.
- Edit:
The button only works on the ground and after a right-click on the confirmation question to avoid accidential triggering.
For the last time on my part, drop the arrogance and talk to Vlad/Tushka/vl82m!
And I don't care about a partial plane turn on. Takes you 2 seconds worth to get that out yourself, and it serves no practical purpose to any of us who know this plane.
For something that would realistically take like 10 minutes for you to accomplish and put as a separate panel option, I really don't understand your aversion to this. And no need to shout with uppercase.
You have any idea what that change could do to the gauge now that you know what it is?
I cannot find any of those instances in the FS9 version of the gauge.
Only that with your version of the plane's load it starts open, without it it starts closed on the external model mind you.
This is again something you seem to not know, the autopilot logic in Russian planes is different to western systems (which the stock system simulates BTW). This is the reason for example that the TU-154's don't even use the default joystick system at all but use a gauge specifically written for them. Plus, the autopilot needs to be disconnected and manually landed at most 30 meters altitude.
They actually did:
FS9 version:
...
Original FSX version right after the install:
...
station_load.0 = "680, 43, 0, 0, Crew"
station_load.1 = "0, 0, 0, 0, Passengers"
station_load.2 = "0, 35, 0, 0, Front Baggage"
station_load.3 = "0, -25, 0, 0, Rear Baggage"
station_load.0 = "680, 43, 0, 0, Crew"
station_load.1 = "0, 0, 0, 0, Passengers"
station_load.2 = "0, 35, 0, 0, Front Baggage"
station_load.3 = "0, -25, 0, 0, Rear Baggage"
station_load.0= "176.000, 54.95, 0.000, 0.000, Navigator"
station_load.1= "530.000, 48.79, 0.000, 0.000, Pilots"
station_load.2= "0, 5.91, 0.000, 0.000, 76 PAX"
station_load.3= "253.532, 34.45, 0.000, 0.000, Front Steward+Eq"
station_load.4= "143.400, -21.98, 0.000, 0.000, Aft Steward+Eq"
station_load.5= "0, 42.01, 0.000, 0.000, Front Bag"
station_load.6= "0, -27.72, 0.000, 0.000, Aft Bag"
It's goes (from left to right) COMM2/BOTH/COMM1/RSBN/NDB1VOR1/NDB2VOR2.
And to make one thing clear:
I'm not interested in making this the most realistic simulation of a Tu-134 ever. If something doesn't work exactly like on the real plane, it shall not be my problem.
Then you are of absolutely no use to people who fly this plane in Flight Simulator at all.
I've been follwing this thread for a while now with much interest and admire the work and efforts people are willing to put into such a project and share the results with others in the community.
From that standpoint I personally think this insulting remark is absolutely way over the top since you don't represent "all the people who fly this plane..." and I'm sure there are a lot of people who appreciate Bjoerns efforts here.
My 2ct.
Mark
Ok, from this point on information will be directed at the topic at hand, the SCS Tu-134 v2.0 port over. Disparaging remarks about people or their abilities are not tolerated. I would much rather see this thread stay open and productive. If that is not possible it will be closed.
Adding a "Cold&Dark" button to get your stupid cold&dark condition back in.