Announcing Tu-22M3 Troika by Black Cat Simulations

I have 32 pages????? Got a post number??

No one should say what page or what post number as different people have different post count per page.

Every post has the post number that is a link to it. Just right click it and copy the link and paste it to directly link people to specific post. THen everyone can click on top right generated link to go to the discussion on the position that post is, by their own personal settings.

C'mon man.. you know its in bad taste to hijack someone else's thread...

But it IS a Brian Cooper mod.......

and the discussion was about him.....

He was posting here.....

However, I apologize if any offense was taken.

None was intended.

Signing off.......:pilotfly:

Incase something happend to the guy, it's a good idea to check and see if well ... the worst didn't happen. It would be a pity if he was going to upload/send his work to you guys after realizing he won't be able to do anything for sometime, but maybe he couldn't do it and it was too late, the data could be sitting there on the PC and it could be destroyed forever if the house gets sold or family sells or repurposes (format) the computer.

Anyway looks like there's some rumors about future use of Tu-22M3 for the new Kinzhal hypersonic missile to extend it's range so that's quite positive news for the long term, but unconfirmed.

http://tass.com/defense/1013794

...(not customers, as we did never even pay a penny, yet) not even an update or anything.

I actually did, 15 Eur or USD, can't remember. I think it was to pay for expenses travelling to the Museum and there was some kind of wooden beermat reward with a Tu-22 on it. But I never heard of that again. Was that reward cancelled or simply put back? I'm glad I could contribute to the development but I kept wondering.

More news about the Tu-22M3 upgrade. http://tass.com/defense/1016295

"Tu-22M3M"

Workin it, workin it! Sirius, sorry, I owe you a response too!

After 6 months non words from him. :music_whistling:

After 6 months non words from him. :music_whistling:

It's dead. Don't torture yourself by waiting on him to draw a line under the project and give you closure.

yep dead. everyobody unsubscribe this thread and check main DCS Mods forum for new threads + user download files every few weeks to check if a new mod has been released.

/over & out

Seems brianacooper11 has re-appeared on the radar. Hopefully some good news!

Last Activity: 10-05-2018 09:21 PM

Announcing Tu-22M3 Troika by Black Cat Simulations

Fingers crossed!

I quit working on the project for two reasons. First, although I was very open and honest about everything, the project still became a bureaucratic security issue for my employer, as a US Air Force contractor. I ended up resigning partly because of it. But more importantly, I had established a relationship with some Tu-22M people in Russia who were happy to contribute to the project, but eventually had to ask me politely to cease my research efforts. I won't say exactly why, but the request was reasonable, they had been very fair with me, and I agreed to drop the project.

While I was trying to make the Air Force job work, the best thing for me to do was cease all communication about the project while I was investigated. I resigned in March, but remained silent while I looked at other work (the security headaches would potentially follow me to any government related job), but I ended up getting out of engineering entirely. I have moved to Alaska to fly professionally, and can say something now.

Bloody hell, that blows.

I quit working on the project for two reasons. First, although I was very open and honest about everything, the project still became a bureaucratic security issue for my employer, as a US Air Force contractor. I ended up resigning partly because of it. But more importantly, I had established a relationship with some Tu-22M people in Russia who were happy to contribute to the project, but eventually had to ask me politely to cease my research efforts. I won't say exactly why, but the request was reasonable, they had been very fair with me, and I agreed to drop the project.

 

While I was trying to make the Air Force job work, the best thing for me to do was cease all communication about the project while I was investigated. I resigned in March, but remained silent while I looked at other work (the security headaches would potentially follow me to any government related job), but I ended up getting out of engineering entirely. I have moved to Alaska to fly professionally, and can say something now.

Thanks for letting us know, even though it's not what we hoped for.

That shows once more how difficult it is legally to develop modern aircraft for DCS, especially russian aircraft.

this was the only mod project that i had been waiting for. that's very sad to hear that.

after phantom delaying news, this is also devestating.

can you at least share some pics of the project?

Hate to hear that brian! Was very well looking forward to this mod. Does this mean that the Tu-22M3 is a more openly "free" project now for people to help with? (kind of like community effort)

I quit working on the project for two reasons. First, although I was very open and honest about everything, the project still became a bureaucratic security issue for my employer, as a US Air Force contractor. I ended up resigning partly because of it. But more importantly, I had established a relationship with some Tu-22M people in Russia who were happy to contribute to the project, but eventually had to ask me politely to cease my research efforts. I won't say exactly why, but the request was reasonable, they had been very fair with me, and I agreed to drop the project.

 

While I was trying to make the Air Force job work, the best thing for me to do was cease all communication about the project while I was investigated. I resigned in March, but remained silent while I looked at other work (the security headaches would potentially follow me to any government related job), but I ended up getting out of engineering entirely. I have moved to Alaska to fly professionally, and can say something now.

First of all thank you for telling us and informing us,I understand your position and I am also really careful legally in terms of my SU-57 Project,so I'm aware of what your going thru and I understand why you had to Stop.

Sorry to hear this, Brian. Appreciate your dedication, time and sacrifice for our little hobby in the virtual skies.

Good luck in your future endeavors.

Devastating, probably the mod I was anticipating the most.

Any chance you talk to the Buccaneer folks and help them get that one wrapped up?

Congrats on the Alaska job! My pops flew Corsairs in Korea, was a USMC pilot for 14 years total, then flew for United for 29 years. He said the guys who flew in Alaska, airlines and bush guys, were hands down some of the best pilots in the world. Good luck in your new adventures!!

I chose my words carefully when I said I stopped working on the project. I didn't say it can't be done. It might be done, even with official support, and that is the way I think it should be done. I will write a longer post about my successes and mistakes, and what I think it would take for someone else to succeed.

I quit working on the project for two reasons. First, although I was very open and honest about everything, the project still became a bureaucratic security issue for my employer, as a US Air Force contractor. I ended up resigning partly because of it. But more importantly, I had established a relationship with some Tu-22M people in Russia who were happy to contribute to the project, but eventually had to ask me politely to cease my research efforts. I won't say exactly why, but the request was reasonable, they had been very fair with me, and I agreed to drop the project.

 

While I was trying to make the Air Force job work, the best thing for me to do was cease all communication about the project while I was investigated. I resigned in March, but remained silent while I looked at other work (the security headaches would potentially follow me to any government related job), but I ended up getting out of engineering entirely. I have moved to Alaska to fly professionally, and can say something now.

OMG...I mean you were under investigation because you were conducting research about the module???? And what about your employer? So what it is really said is that you were forced to leave the USAF becuase of a DCS module???:shocking::shocking:

Thanks for the update Brian, stay safe in Alaska....there are no old bold pilots...best wishes for the future and if you get bored and get another project going, it would be great to see. There comes a point when it's just not worth the hassle.

I had intended to do a follow up post about what I meant when I said, in reference to the Tu-22M3, "I didn't say it can't be done. It might be done, even with official support, and that is the way I think it should be done."

The short explanation is that this project needs resources FROM THE START to make it happen. My 'free load first, money later' approach would never have worked. Knowing what I know now, I'm kind of embarassed to think about what went through ED and Heatblur/Leatherneck people's minds as they watched me push this along. Man, I was so pie-in-the-sky! To state in hindsight what should have been elementary from the beginning, this is not a Yak-52. The external model and cockpits (plural!!) are complex, as would be the flight model and aircraft systems. The thought that really got me going on this project is that the analog nature of all its systems would make it easier to program than an aircraft with digital displays and systems. I would not be surprised if that's incorrect, though I still think along those lines. Regardless, this is a project on the scale of the F/A-18 or F-14. Look at the resources they've consumed, and how hard the slogging still is, though in the end I think they will be economic successes. I had thought the main obstacle was technical data, but it's not. It's the usual stuff: time, money, and people. Time is really just money in another form. People, great people, require money and so there's money in yet another form. And that forms my short, unhelpful answer to the question, "How do you make a DCS Backfire happen?" Money. ED's licensing requirements at first seemed like an unhelpful obstacle to getting money, but really they're just trying to head off what can become larger problems for everyone in the long run. If you have sufficient resources in the first place, what ED wants to see up front is not inconvenient. In fact it forces you to get your priorities straight in the beginning. Good on them!

If money is the main thing that is needed, I do have two smaller points to make. First, the project should either be a prodominantly Russian/Ukrainian effort, or at least lead by a Russian/Ukrainian. Although everyone loved the project and generally believed my intentions were not malicious, in the end I was a US-person asking for priviledged information about a Russian military plane. It was 2015-2017, not 1994, and my citizenship was a problem. I'm convinced a Russian could get the portions of the flight manual necessary to simulate in DCS the Tu-22M3 as it was around the end of the Soviet Union.

Second, I'm not the guy who should actually manage a project like this. I'm learning my limits. Research is fun, as is programming flight models, aircraft systems and avionics. Learning about models and texturing, OK, I can learn enough about them to know what they need from programmers. Schedules: meh. Money: ugh. Forming a business case, fundraising, actually building a company? I'd rather clean my toilet. Person-who-is-perhaps-NOT-Matt-Wagner-but-is-LIKE-Matt-Wagner should lead this project.

So, big obstacles, the project is dead, and I'm not really working to make it happen, but I'm still nursing little bits of it along, in the hope that someday Matt Wagner announces that somebody got a license to do DCS Backfire. It's a pipe dream, but a pleasant one. One of the things that excited me most was the prospect of doing a flight model for the Backfire, so I'm trying to put that together so people can at least play with the default Tu-22M3 in external view. I've only just now gotten back to it, after a break of at least a year (has it been two?) I'm in the middle of trying to switch career fields from engineering to commercial flying. It's a very cyclical industry, in the US at least, with periods of furloughs and bankruptcies, and many airline pilots have a backup source of income. I've decided to make mine programming, since it's something that permits flexible hours. I'm trying to finish the Backfire flight model to include in a portfolio to present to potential employers, so it might actually get done...

Knowing what I know now, I'm kind of embarassed to think about what went through ED and Heatblur/Leatherneck people's minds as they watched me push this along. Man, I was so pie-in-the-sky! To state in hindsight what should have been elementary from the beginning, this is not a Yak-52.

These words truly frighten me, as this is/was my current ideology. And assuming what would and would not be easy, with the complexity of an aircraft this large of a beast, I think I would have kept myself blind and ignorant to the truth all along than to listen to the warnings. :(

It's sad to no longer see this project led by you. I do honestly hope that somebody can continue these efforts as the progress made was remarkable in terms of the dedicated development on the models and research on the systems. Let us please get a Tu-22 module for the future!