• Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

SCS Tu-134 v2.0 FSX portover

Status
Not open for further replies.
Basically, until these two switches are in the lower position on their own accord after a load of the plane (in red) on the overhead, the plane doesn't seem to load correctly, that's my observation on the matter.

Overhead.jpg


What seems to be missing is that on the FS9 version you have to start the plane in 2D panel mode, otherwise it doesn't load correctly, it seems to be the same here too. I copied the 2D panel stack from the fs9 version into the FSX panel as a test, and as soon as the 2D panels did their preload all worked well!
 
I've altered the startup logic of the 134 for the load/save system so that the engines won't cut out if they're running. I'm having no problems whatsoever, regardless of the position of the fuel cutoff switches.

Just did a test. Started one engine, parking brakes worked. Energized the hydraulic braking system (plus emergency system). Reloaded the plane. Parking brakes and engine still worked.





In other news, I've reimplemented the switch sounds with the help of Doug Dawson's XML sound gauge and 750+ lines of code (lots of copy+paste tho').

The information and download is here, as usual:
https://docs.google.com/document/d/1LgF2KWc1IrFpyr0W9C-5wuPu0Ki0nxijZ0jHOf_8y0g/edit#



Also, if you find the flight attendant to be just too annoying (her voice sample triggers get buggy when you reload the plane often), go into SCS\Tu-134\Config\Soundfiles.ini and comment out (place two slahes in front of each line) or delete all entries relating to the stewardess.
 
Hello Bjoern. This Tushka (Author of manual). I can reassure you that my manual is not oudated, well... I wrote it for everyone to learn the old fashioned way in the Soviet Union instead of modern techniques due to the navigation systems and the nostalgic feel.

This manual is just in beta, more is coming. I have sent you a mail on avsim.su about it.

Also I thank you very much for improving the planes performance in FSX. It is very helpfull to all of us. Will test when I come back from work.

If anybody have any questions regarding the aircraft or the manual, feel free to sent me a PM or post in this topic.
 
In the link provided, Vlad share with us pdfs from a old Tu-134 addon not listed in the Google Document.
Maybe these documents are useful for any user.

Hello, manual was written for SCS Tu-134 for FS9 which is the original aircraft. It will work perfectly fine for FSX. Only the 2D screenshots of panels need change to 3D ones. If anybody interested I can upload the original word documents as they can be edited and contain some additional information in bad english.

If you mean my very old set of manuals then those were written for Ariane Tu-134 a decade ago. They will not work for SCS because that addon was not complex enough and lack all the vital features.
 
I believe no source files from SCS, but is there a way you could code the autopilot to follow a GPS? The real Tu-134s still in service have them despite their navigators are still using NAS-1 (believe it or not even on complex STAR procedures....). Works in Russia since most SID/STARs are based on NDB stations but not in foreign countries so well.

I just thought it would be useful for some people who wish to not fly the old Soviet way.
 
Just for you guys to know what to expect from me:

Adapted ground study manual for flying with VC (3D cockpit). Will also feature descriptions on how to use the air conditioning and navigation systems. This is the manual "Flight Manual Tupolev Tu-134A-3 English version beta" that you can download here: https://yadi.sk/i/8109Hg8ncuw3z

Then there will be a completely new manual that covers an entire tutorial flight step by step from start to shutdown (Bjoern you will know it as "flightmanual as i mentioned in my mail to you). It will cover a strech either from Moscow - Minsk, Leningrad - Tallin, Moscow - Leningrad, or even completely different. Users can vote. Also Im thinking about maybe a second tutorial flight covering a flight either Balkan Bulgarian, LOT, CSA, Malev, Air Koryo covering a flight not using Soviet navigational systems as they wouldnt be available outside the CCCP.

Then the SOP for flying with Aeroflot, the V3 least important manual. This one will be about Aeroflot. It will contain all the necessary briefing and information to make you feel that you're actually in the 80s going to fly a regional Russian flight with Aeroflot. It will contain the old timetables from Aeroflot, all the links to the sceneries, will have all the original flightplans, original charts (RSBN scenery has the old navaids making this possible) along with flying techniques and discipline on flying. It will cover and explain all the "strange" things you might encounter during the route and will effectively warn you on how to deal with them. And do not worry, refugees or drunk passengers will not be simulated :very_drunk:

All these manuals will contain information I wrote, that Bjoern wrote and then some additional info we pick up on the way.
 
Bjoern, could you possibly look into the 2D panel load thing? I get the distinct feeling that the lack of it in the FSX version is screwing over things.

BTW, as far as I understand through the in-build Chrome translator, something is supposedly wrong with the VC itself because of the guy who built it supposedly disappeared or something (question is mostly for Tushka). Is this true?
 
BTW, as far as I understand through the in-build Chrome translator, something is supposedly wrong with the VC itself because of the guy who built it supposedly disappeared or something (question is mostly for Tushka). Is this true?


Yes, there were big problems and this VC was built years ago. The programmer who designed the VC left the project years ago (and never returned) leaving it in an unfinished state for half a decade making us all believe we would never see anythig more from SCS, yet we did. I do not know how, the team did not explain.

There are bugs with the VC... small ones you wont notice, incorrectly functioning (synchronizing) switches, windows too big with an unusually small yoke in the way. My biggest concern with the VC is the fact that the VOR/ILS needles on the HSI are very hard to see as theyre very small lines. Especially in the dark. However the feel of the VC is 100%. It is small, crampy and feels true to life.
 
Yes, there were big problems and this VC was built years ago. The programmer who designed the VC left the project years ago (and never returned) leaving it in an unfinished state for half a decade making us all believe we would never see anythig more from SCS, yet we did. I do not know how, the team did not explain.

There are bugs with the VC... small ones you wont notice, incorrectly functioning (synchronizing) switches, windows too big with an unusually small yoke in the way. My biggest concern with the VC is the fact that the VOR/ILs guidelines on the HSI are very hard to see as theyre very small lines. Especially in the dark. However the feel of the VC is 100%. It is small, crampy and feels true to life.

I see. I am a 3D artist among other things you know, I'm already helping Kirill with the Il-62 VC. If Bjoern (since he did the Tinmouse VC) could help me with the port and animation xml, I could build a new one with proper reference, even expand it to the later models (the B is one I see a lot around too as an example). I'm used to making models which have multiple variations, so it wouldn't be a problem for me. You have examples of my work at nsadonis.deviantart.com to have an idea of my skills.
 
I see. I am a 3D artist among other things you know, I'm already helping Kirill with the Il-62 VC. If Bjoern (since he did the Tinmouse VC) could help me with the port and animation xml, I could build a new one with proper reference, even expand it to the later models (the B is one I see a lot around too as an example). I'm used to making models which have multiple variations, so it wouldn't be a problem for me. You have examples of my work at nsadonis.deviantart.com to have an idea of my skills.

Whilst I appreciate that you want to take time to design a new VC, I think it would be more logical to leave the old VC be as there is nothing wrong with it. (Well, it does have oversized windows and yokes blocking instruments in some phases of the flight). Your 3D modelling skills are good, so it would be nice to see a VC for Tu-134B and improved for Tu-134A-3. If it is possible, I say do it. But I do not know if it is because you would need the source files and I guess getting them from SCS would be a hassle.

I think better (in my personal opinion) to place all your efforts on the Il-62. We really need a long-range Russian airliner in PT quality. I hope there are any news regarding that project.
 
Whilst I appreciate that you want to take time to design a new VC, I think it would be more logical to leave the old VC be as there is nothing wrong with it. (Well, it does have oversized windows and yokes blocking instruments in some phases of the flight). Your 3D modelling skills are good, so it would be nice to see a VC for Tu-134B and improved for Tu-134A-3. If it is possible, I say do it. But I do not know if it is because you would need the source files and I guess getting them from SCS would be a hassle.

It would be a lot easier to build a new one from scratch than use the existing one and fix it in all honesty. That's a critique I gave Kirill about the Tu-154B-2's FSX VC too (that one is a royal mess in the modeling technical sense), plus that they use a lot of texture sheets (hence a lot of drawcalls in the FS9/FSX engine). I'll let Bjoern too chime in and give his thoughts on the matter since he is fixing up the gauges.

I think better (in my personal opinion) to place all your efforts on the Il-62. We really need a long-range Russian airliner in PT quality. I hope there are any news regarding that project.

I'll be able to get back on it after May 1st, then it's up to Kirill and who else is working on it.
 
It would be a lot easier to build a new one from scratch than use the existing one and fix it in all honesty. That's a critique I gave Kirill about the Tu-154B-2's FSX VC too (that one is a royal mess in the modeling technical sense), plus that they use a lot of texture sheets (hence a lot of drawcalls in the FS9/FSX engine). I'll let Bjoern too chime in and give his thoughts on the matter since he is fixing up the gauges.



I'll be able to get back on it after May 1st, then it's up to Kirill and who else is working on it.

Yup, I understand. I am sure nobody will complain if we get new VCs for Tu-134 and Il-62. Especially as it would be an FSX-native model. I can guess it is not easy to remove a VC from a complex plane and then build a new 3D cockpit from scratch (and make it fully compatible with SCS or PT if the Il-62).

I wish you all good luck with the project whatever happens, and hope to hear good news soon )))))
 
I believe no source files from SCS, but is there a way you could code the autopilot to follow a GPS?

I will not touch the AP code itself, but I could try to do a GPS-Driven gauge that automatically sets the Map Angle to the next waypoint.



Bjoern, could you possibly look into the 2D panel load thing? I get the distinct feeling that the lack of it in the FSX version is screwing over things.

First, try a reinstall and use the version I am using!



If Bjoern (since he did the Tinmouse VC) could help me with the port and animation xml, I could build a new one with proper reference, even expand it to the later models (the B is one I see a lot around too as an example).

Umm...you do realize that you'd need to remodel, retexture an reanimate the ENTIRE thing inside and out, right?

The fastest course of action would be finding someone from SCS and asking for the model source files.
 
First, try a reinstall and use the version I am using!

I am, minus the latest batch of updates you did since the start.

Umm...you do realize that you'd need to remodel, retexture an reanimate the ENTIRE thing inside and out, right?

The fastest course of action would be finding someone from SCS and asking for the model source files.

Actually no, it would be faster to build a new one from scratch than fix the current VC (trust me on this :p ).
 
Fixed two more bugs in the switch sound system.



Download (page 4):

https://docs.google.com/document/d/1LgF2KWc1IrFpyr0W9C-5wuPu0Ki0nxijZ0jHOf_8y0g/edit#



Replace "panel\SCS_TU134" and "panel\Tu134_Mods" with the folders from the download.






I am, minus the latest batch of updates you did since the start.

And the brakes still don't work? Do you actually do your startups according to the manual?

Actually no, it would be faster to build a new one from scratch than fix the current VC (trust me on this :p ).

I'll trust you when I see it (modeled, textured and keyframe-animated!). :)
 
And the brakes still don't work? Do you actually do your startups according to the manual?

EDIT: I have the Cessna172SP cold and dark except for the avionics as default flight,
If I load the Tu-134 and then load the flight and reload the plane, everything works
If I load the 172, and load the Tu-134 twice in a row, everything works
If I don't do the second load, the brakes don't work no matter what I do, and the pressurization system acts up.
In the first two instances the two engine switches in the overhead stay off, in the third it doesn't.

I'll trust you when I see it (modeled, textured and keyframe-animated!). :)

The better the reference I get (including orthos), the faster I can do it :p
 
Last edited:
Error with the latest, I get it for multiple sound files not just this one:

Tu-143_error.jpg


EDIT: After your last update, everything works fine on first load of the plane (mind you I don't use the load/save gauge out of personal preference).
 
Status
Not open for further replies.
Back
Top