Search the Community

Всем привет. Мы RTFC - разработчики игровых устройств для авиасимуляторов. Сегодня хотим рассказать вам о нашем новом устройстве панель - Navigator. Об устройстве: панель Navigator обладает множеством элементов управления, обеспечивающих высокую скорость взаимодействия с летательным аппаратом. Устройство поможет сократить время введения навигационных координат, курсов, радиочастот, таймеров и прочей цифровой информации. Помимо кнопочной клавиатуры в устройстве уделено особое внимание контролю радиостанций. Благодаря энкодерам и хаткам можно удобно пролистывать встроенные игровые радиокоманды и отдельно управлять радиостанциями самолета. В дизайне устройства учитывались также пожелания любителей полетов в VR очках и шлемах. На цифровой клавиатуре на кнопках «5» и «0» добавлены горизонтальные насечки для слепого ввода, между правой и левой колонкой дополнительных кнопок L1 и R1 добавлены вертикальные разделители. Хатки разнесены на разные стороны лицевой части панели во избежание случайного нажатия, колпачки хаток разные. Энкодеры разделены при помощи размещения на разной высоте так же для тактильного восприятия. Установка панели: разместить устройство в своем летном месте можно как самостоятельно на столе среди других устройств для управления полетом, так и сформировать комплексное решение для управления, установив панель между двумя MFD - Bullseye от RTFC. Панель устанавливается на подставку с регулировкой угла наклона, ножки подставки прорезинены, основание подставки утяжелено, чтобы панель не скользила по столу и не опрокидывалась, кабель, подключенный к устройству, вложен в направляющую для провода. Комплектация: в коробке вы найдете все необходимое для полета. панель Navigator – x1 Кабель подключения USB - 1.5 метра – x1 регулируемая подставка – x1 Комплект крепежа – х1 Техническая информация: корпус панели выполнен методом 3д печати из ABS пластика с дальнейшей постобработкой. Тактильные элементы изготовлены на фотополимерном принтере. Электронные компоненты ALPS EOM высокого качества, программное обеспечение собственной разработки, печатные платы собственной разработки, монохромная зеленая подсветка «Emerald Green», 5 режимов яркости. Для оформления предзаказа: Вступайте в нашу группу или напишите нам на Contact@rtfc.pro Все актуальные цены и информация о доставке публикуются в группе. Если хотите нас поддержать подписывайтесь на наш Бусти.

Hello everyone. Is there anyone who has the Komodo TEDAC? Could you please PM me. Thanks in advance.

Hi everyone, A somewhat minor issue, that's trivial to fix - a complete S-300PS missile battery doesn't work without the SAM SA-10 S-300 "Grumble" C2 unit (5K56S PBU). IRL this unit is a regiment/brigade-level command and control unit, used primarily for forwarding targets detected via 5N64S RLO [Big Bird-B] radar to 2-6 missile batteries. The analogue to the Patriot system would be the AN/MSQ-116 ICC, which in DCS (as it should), is not required for a Patriot battery to function. The 5N63S RPN [Flap Lid-B] fire-control radar has a cabin (F2K) mounted on the rear of the vehicle, which provides battery-level command and control (the Patriot analogue would be the AN/MSQ-104 ECS). The missile batteries should be able to perform their own target search, independent of the command unit, using either the 5N66M NVO [Clam Shell] radar (albeit only against terrain-following targets) - which is required against NOE targets anyway, or via the autonomous target search mode of the 5N63S (which is 105° in azimuth by 1° in elevation (though this can be elevated up or down as needed and the radar itself can be rotated through 360°)). The F2K cabin of the 5N63S RPN should then provide all the command and control functions for the battery, including target acquisition via the NVO or the fire-control radar. The 5N64S RLO [Big Bird-B] radar is already not required to have a working S-300PS missile battery (just the acquisition capabilities of the battery will be greatly diminished), the same should be true of the 5K56S PBU (SAM SA-10 S-300 "Grumble" C2). Without the 5N64S radar and/or with only a single missile battery, the 5K56S should be redundant (just as the AN/MSQ-116 ICC is redundant for Patriot without IADS functionality). However, despite this, without the 5K56S PBU in DCS, the missile battery doesn't function - as if the 5K56S is treated as the sole command and control unit, which isn't the case. This means that if the command and control unit is disabled or destroyed, or is in the process of relocating, the missile batteries aren't usable, which also shouldn't be the case - they should still function, albeit with quite degraded acquisition capability. The only difference between the 2 tracks below is that the noPBU track doesn't have the 5K56S unit and the wPBU track does. You can see that the target is not engaged if the PBU isn't present. As above, without the RLO and with only a single missile battery, the 5K56S is redundant - the 5N63S RPN's F2K cabin provides all the necessary command and control functions for the battery, just as the AN/MSQ-104 ECS does for Patriot. To fix this issue, all that needs to be changed is that the "depends_on_unit = { { { "S-300PS 54K6 cp" } } }," needs to be removed on line 23 of S-300PS 5H63C 30H6_tr.lua (for the self-propelled mount) and on line 19 of S-300PS 40B6M tr.lua (for the 40V6M mast-mounted version). In case anyone is wondering what the structure of an S-300PS brigade/regiment looks like, see the spoiler below: S-300PS_missilebatt_test_noPBU.trk S-300PS_missilebatt_test_wPBU.trk

Super Hornet inspired UFC Control app for the F\A-18C for DCS World. I've been working on this app for a while, since UFCs are difficult to build i decided to make this app and use it with a 8 inch fire HD tablet in my cockpit setup. I added some extra features like the ability to control some of the panels and i currently working on adding a Data Cartridge feature to input way points faster. I tested everything i could and everything seems to be working so far. I would really appreciate if you guys can report bugs back to me. I'm also open for suggestions on extra features to add, etc. For now the APP is only available for Android but I'm in the process of submitting the app to the Apple App Store. Let me Know what you think! Hope you guys Enjoy The APP! INSTRUCTIONS: Video Tutorial: Coming Soon 1- Get The App: Android https://play.google.com/store/apps/details?id=com.embarcadero.HornetUFCDCS iOS https://apps.apple.com/us/app/hornet-ufc-dcs/id1604694496#?platform=ipad 2- Download the lastest release of HornetUFCDCSAppServer from the GitHub Repository https://github.com/AlphaMikeSimulation/HornetUFCDCS/releases 3- Unzip The Content somewhere in your hard drive( Desktop Or C Drive For Example) 4- Copy the DCS-BIOS Folder yo your Scripts folder ( C:\Users\USERNAME\Saved Games\DCS.openbeta\Scripts) 5- Edit your export.lua file and add this to the end of the file: dofile(lfs.writedir()..[[Scripts\DCS-BIOS\BIOS.lua]]) 6- Open the HornetUFCDCSAppServer.exe and go to settings and inpiut the IP Address of the Tablet or Phone that you are using for the HORNET UFC DCS App 7- Click in Shutdown Server and Start the server again for the new IP to take effect 8- Open HORNET UFC DCS In your phone or tablet and go to settings, input the IP of the computer that you are using for running DCS World 9- Open DCS World and wait for HornetUFCDCSAppServer status to change status from DCS Not Running To Waiting for DCS... 10- Open any Mission and wait for the HornetUFCDCSAppServer status to change to Connected 11- Now you can control the UFC from your phone or tablet, ENJOY!

Recently I got the f-18 hornet and tried flying it with vr hand controllers, my original plan was to use it exclusively in vr with them, but that hope is dashed so I was wondering what hotas under 200 would you suggest for the hornet in vr?

Hi everyone, It seems that units (at least amphibious ones) can now be spawned on the decks of ships, including ships that are moving, and will stay put through turns and speed changes (previously when I had tested this, they would spawn at the sea surface, requiring them to be jumped onto ships, though the mission editor restriction still restricts you from placing non-amphibious units onto ships). However, if you use CA to take control of a unit placed on a ship, it will immediately start floating upwards. It's almost as if the unit is being abducted by aliens or something. On the Tarawa at least, they appear to come to a stop and level out at 288 ft MSL and continue to follow the ship (albeit not exactly in the same place and orientation). But it gets weirder still - if you switch to another unit, other members of the group may start doing some other weird things. In the tracks below, when player control is relinquished to another unit, the remaining units in the group fly off of the deck and start travelling in unexpected directions, behaving quite oddly (drifting, jumping around, appearing to snap between pitch angles). GroundUnitsTarawa.trk GroundUnitsTiconderoga1.trk GroundUnitsTiconderoga2.trk

Using a Thrustmaster HOTAS setup. I had been flying the F-16 offline all afternoon and no problems (was not connected to wifi). On the second online mission, during startup I went to the Adjust Controls option to check a binding on my throttle. Upon pressing throttle buttons, no actions were shown/highlighted on the binding/control page. The #1 engine throttle was moving the rudder (not my setup). I then noticed the control setup was (I think) the default F-16 one, not the LUA(s) I've created. I found I could not access/find in the drop down menu any of the control LUA setups I have made. I could not select Open Profile (it was grey). When I pressed buttons on the joystick they showed/highlighted the default actions; not my settings. After pressing a joystick button, the Open Profile was white and I could select from my LUA files, but when they loaded, they are not the ones I've created; they are the games default F-16 controls. Also note the file size of the F-16 LUA's "I've" created compared to the other aircrafts. 1kb is pretty small - I think they've been changed somehow. When flying other aircraft, the controls work properly to my created LUA, but if I go into the Adjust Controls, they are switched to the F-16 default control setup. Is this a virus from online? No issues til the second online game, and I was so involved in trying to figure out my binding issue, I don't remember what server I was on.

My problem is (only with the F18 module!) that the axis control of the ailerons sometimes no longer reacts and even get stuck in the last position for a couple of seconds (1-2 sec) The joystick works perfectly and the control diagram in-game shows no reaction to the inputs during this time, but as I said only for 1-2 seconds. The problem occurs from time to time, whether during flight or even on the ground as soon as you want to move the ailerons. With other modules such as F15E and F16 the problem does not occur at all, no matter how long I fly. (Both ST and MT variants of the game are affected) I have also tried reinstalling the F18 module, but this didn't help. I had this problem even with the previous patch, but now I decided to open a ticket since the problem has been not solved with the current patch.

It would be most effective if further peripheral controllers were permitted to be bound to the F10 Coordinate Picker tool. Currently, it is only permitted to be bound to keyboard. Further controllers like throttle and sticks would be great. Mainly however, mouse controls would be most effective and a natural place to bind such a tool. Myself, I have an extra 5 buttons on my mouse I could bind to this otherwise very excellent tool