Hello,
I’d like to share with you my recent work on new flight deck of USS Enterprise. I hope you like it. If not let me know what could or shoud be done better.

StenneG (thank you!) inspired me to make weathering in different way, but unfortunatelly due to technical problems I was not able to make this time. Why I release it then? Because it is finished in the sense that is complete and I still consider it as an upgrade, but for sure there is a room for more improvements. Unfortunatelly I am little bit tired of spending evenings working on HUUUGE xcf file, so I need a little break and focus on something else. I would not want to keep it unreleased for ages too.

StenneG, dema - thank you!

Here is the download link:
https://drive.google.com/drive/folders/1H30ekQWhZ6-yLlvJwExxC0KyZPfd84c_?usp=sharing <–- NEW LINK here with corrected share settings (“EVERYONE”)

INSTALLATION:
1. make a backup of the following files from \Falcon BMS 4.34\Data\TerrData\Objects\KoreaObj:

• 96.dds
• 1756.dds
• 1757.dds
  2. copy the files from Google Drive to \Falcon BMS 4.34\Data\TerrData\Objects\KoreaObj

In the Google Drive you will find two 1756 dds files, the one called 1756.dds has the resolution of 8192x8192px , the second one called 4096_1756.dds is obviously 4096x4096px big. Just rename it to 1756.dds if you want to use the lower res version.

CHANGELOG:
07/06/2020 - release
09/06/2020 - cat#1 and cat#2 became shorter (screenshots have not been updated, yet)

Best regards,
sunrrrise

Nope, everything was and is fine from electric point of view. What a piece of junk, I am 99% it is because SW/FW, not hardware. Anyway, I was going to modify anyway, it will probably sooner than later then.

Great!:)

but wait… A-10C? I think A-10A it’s better idea - less compromises, less work, less chance of being compared to DCS A-10C (I mean talking like ‘what the purpose of this? you already have it in DCS!’).

My vote: A-10A, (if not then A-10C ;)) and F-15C.

Hi,
I know that keys are treated separately between F-16 and F-15, but can the same approach be implemented for axes?

I am using modified TM Cougar + TM Viper TQS for F-16 and TM Ava + heavy modified/DIY Suncom Talon for F-15, but setting up axes is kinda PITA, even in Alternative Launcher

Mower, have you tried to connect that card to PayPal? I have my prepaid card connected to PayPal and it works very well. Recently I was also able to link my company’s benefit card with some crazy restrictions to Google Pay. In both cases even if the shop does not support said payment methods you should be able to transfer money back to your bank account.

Nope, everything was and is fine from electric point of view. What a piece of junk, I am 99% it is because SW/FW, not hardware. Anyway, I was going to modify anyway, it will probably sooner than later then.

Hmm… for sure I have disconnected it recently (you mean in TQS box, not joystick one?), but the problem with axes appeared just after I had replaced mobo/CPU/RAM and reinstalled OS, not after opening it. Then I found I have a problem with Cougar… anyway, I am going to open it again today and check all the cables and connections one more time.

In the worst case scenario I will replace all electronics with 2 MMJoy2+ProMicros combo.

Woah, someone replied No, it is hardly possible, it was still sitting in my simpit. I have found that I am able to calibrate it with TM calibration tool and then main axis has full range (however center is a little bit off), but I am unable to calibrate cursor axes. What is strange it looks like main axis is impacting other axes while being not impacted by those other axes. Strange, isn’t it?

I have also found that electrically all connections are OK, I used multimeter to check that.

So it is something with the chip/EPROM?

@Radium:

Hello,

I’m very happy to share this trailer video of my J-20.

It was produced 8 months ago under BMS 4.35 for testing proposes, but not yet available. I’m eagerly waiting it to be released for the whole community !

Cheers,

Radium

Oh my, imagine J-20 being flyable.

Yeah, I know, it is still UFO, but **** that. I miss 90’ with their tons of F-22 simulators

Hi,
recently I have changed few parts in my PC and I am still working on making my PC great again!

Unfortunatelly I have a problem with my Cougar - initially I thought it is poorly (auto)calibrated cause I am getting something like 0-63%. Worse, it seems that main throttle axis impacts all other axes as well! I mean when I am increasing Z-axis I see that both S1 and XR (ANT ELEV and RANGE) are being increased as well and to the exacly value (58774/89.68%). Radar cursors are also impacted but due to their nature it is hard to tell how much.

It is very strange and this is the first time I see something like that. Have you exprienced similiar error?

What I have tried:

• reconnecting,
• connecting to different USB port,
• reinstalling,
• reflashing.

Nothing.

Kind regards,
sunrrrise

@Geraki:

DirectX 11 ???

It is 4.34.

Hi,
for sure both will work. Select joystick as master one and throttle axes for on tabs in Advanced page.

@Dee-Jay:

Hi!
If you still have contact with him … (?) could be nice to ask him the source code to adapt to the new 3DDB requirements. Otherwise, “soon”, LE will be dead once for all.

OMG!!! If “3-4 weeks” has been changed to “soon” 4.35 must be really around the corner :woohoo::drink: