Leaderboard

F-4 Cockpit from Heatblur Discord.

Jabbers twitter be like...

Better resolution picture of incoming update for the Hind.

M551 LT (USA) version 1.0.0 released! Changelog Version 1.0.0 Release version

In the thumbnail, notice the mixed hellfire loadout on the launcher, and the climbing pilot animation.

Vom Heatblur Simulation Discord

Hello, I find People struggling with reflections in the Cockpit. Or in the Tomcat where the lights of the buttons are not that bright. In these scenarios a function like the flashlight would be helpfull just instead of a light, there´ll be the shadow of a hand. So people could partly read/see their instruments or sensors even in very bright conditions. You can call it the Anti-Flashlight or just Hand-Feature. I hope you get the point.

Great to hear about improving radar simulation but I also like to hear the answers to the earlier questions: - RCS vs target aspect and loadout - plans for propagation of new radar simulation to other modules

It was changed a while ago. The RBS-15KA needs the UndE 23 STR to work. But the PrSM AShM uses AWACS. I just ran a test and had no problem with either of them. Check my attached mission. PrSM and RBS15 test mission.miz

по 1) : это чем?? ПТУРом? 1) ограничение DCS - далеко не каждую постройку /препятствие можно разрушить боеприпасом здравый смысл реальной жизни - бревна ПТУРом разрушать весьма дорого (и не разрушишь)... т.е. за это за я...подвешивтаь надо) 2) если КЭ (игрок) будет иметь возможность пускать ПТУР сам, то нахр.. мы так до этого старались ? Можно было и оператора тогда не мудрить.. категорически против такого.

Yes, that's because AoA sensors are more as ideal , feather like. They move with every minimal breeze or turbulence while on the ground. IRL sensors have some mass and a little bit of friction, so they will be stuck on the ground if winds are light. They can show a similar behavior under very strong turbulent wind. In many cases the aircraft will ignore value below a threshold CAS. So yes, it's not 100% correct, but not 100% a glitch either. Should be improved, but not a big priority at the moment.

На счет этих пока не скажу. Но новые технологии БРЛС будут использоваться на других модулях ED и, в переспективе - внешников. Когда доработка и отладка закончится.

It is an official image actually, Cobra posted it on the Discord today.

Great news guys, it's done, it's finished, it's aaaliiiive! Now I can proudly say I have actually finished the force sensing project, after what.. like 3,5 years?! Although in 2021/22 pretty much zero work was done due to family and C19. I had all of the mechanical parts already laying around but the electronics were still very much rudimentary. In early 21 I had made a few for a commercial project, but with a completely different electronics layout as they wanted I2C comms with sigma delta ADCs for a very specific MCU. I am super happy with the electronics now. It is already the third tested revision of this PCB layout and I spent a lot of time optimizing filters. The supply filtering as well as output filtering are spot on and noise is several factors lower than on the FCC3. Contributing to a low noise floor is a different type of resistor that I changed to recently, they are about 25x the cost compared to standard 1% resistors but in bulk it's still just penny stuff. In the following picture you can see rev 1.2 and 1.3 in my Cougar prototype setup. The production units will have all standard nuts replaced with locking nuts, but for ease of dis/assembly I chose not to use them. Also you can see wires sticking out on the side, that's just the prototype so I can switch between PCBs and quickly solder them back on. Second pic shows the FCC controller installed in the Cougar base working in combination with the FCC R4. The joystick button cable for the shift regs is not soldered on, again for ease of swapping out PCBs. However, I did test it separately and it works flawlessly. The FCC controller mounts without any problems to the Cougar base and would be a good replacement for broken Cougar mainboards even if using the standard Cougar gimbal. I've also 3D printed a jig for sensor placement, although the slits are too wide on this one and I will reprint it. The FCC controller is still missing two LEDs for hardware indication of X&Y axis center position, but the ADC filter is now complete. Since I needed new connectors for the Cougar Ministicks which can currently only be sourced from Japan, I ordered some quality filter components together with them. In hindsight that was a pretty bad decision, because the Japanese electronics supplier sent me several packages and for each of them I had to pay a ridiculous amount of import taxes and DHL fees.. Well, s.. happens, at least the filters are working well! The FCC controller has a reset button to activate the bootloader. That way one can even easily flash MMJoy2 and I've made a preconfigured profile as well. The small 6pin connector is for the Warthog joystick buttons, the larger 5pin for the Cougar. For Warthog installation I'll need 90deg connectors, which are already in the mail. That's where I made a stupid mistake.. To get the Warthog mounting holes correct I actually took the time to make an accurate CAD model of the Warthog base lower ring (third pic). Next, I mistyped the measured distance by exactly 1mm on the PCB layout editor and now the Warthog mounting hole spacing of the FCC controller is off. I think it still fits, but can only be mounted with one screw... bummer! Fourth pic shows the comparison to Cougar and Warthog mainboards. In terms of Software, the FCC controller will be running @uri_ba amazing software as standard option. I will contact him regarding a few minor quirks I found and maybe he will find the time to iron them out! First pic shows the FCC controller interface with the optional sensor rotation enabled, as it is in the real aircraft. I moved the stick only vertically and horizontally and the software does the offset. You also have the option of proportional force mapping accurate to the real F-16 analog or digital FLCS. Now the preconfigured sensitivity settings will not be accurate, as my FCC R4 has higher max force limits than the FCC3 (which has ~4-6kgf at max output). Second picture shows the FCC controller configured with MMJoy2 and no filtering whatsoever, so plain raw signal. On the right side you can see me jitter perpendicular to the input axis at higher forces, as apparently I need to give the gym a visit (and I was simply holding down the Cougar base on the table with my second hand). I noticed even when walking around in the room it picked up the vibrations... pretty crazy. Flashing MMJoy2 over uribas software can simply be done via the reset button, the other way around is not so straightforward as it turns out. MMJoy2 apparently overwrites the bootloader and I needed to reflash it via my trusty old USBasp (third pic). I actually tried the older style analog SSC forces required on my prototype (a ridiculous 40.46 lbf / 18.35kgf for full pitch up) and it is simply no fun whatsoever. No wonder the pilots complained, I get tendinitis just by thinking about it.. Therefore I decided to go for the modern digital SSC force limits with 25lbs max pitch and that can be digitally turned down to a flightsimmer friendly 13lbs/ 6kgf or even lower if desired. Now here is the question to you guys. Would you prefer the real deal digital SSC limits aka 25lbf / 11.34 kgf or the usual 6kg such as FCC3/ FSSB R3. I'd always go for realism, but it definitely still is a workout and you do lose some precision when digitally setting lower force settings. Currently I have enough parts for 20 units. Three of them are already reserved for people who helped me out massively in designing the FCC R4 and will be sold for parts cost. The first unit, aka my prototype will stay with me, so there are 16 units left to be sold in the first batch. For this first batch I will include a set of replica F-16 DMS & CMS hatswitches for the Cougar/ Warthog as a thank you gift (see pictures below). The electronics on the FCC R4 will have a three year warranty included, but that's for legal reasons and honestly if something breaks after these three years I'll likely fix it anyway, as I've done with my older mods. If you manage to break any of the metal parts, then I'd be really surprised. If you legends would help me spread the word and sell these 16 units, then I will have recouped all my R&D costs and even have some funds left over for my next projects. These next projects will include a replica F-16 force transducer Slew for Cougar and Warthog Throttles, based on similar electronics as the FCC R4. Secondly forged carbon fiber F-16 pedals and angled Cougar/ Warthog tailpieces. As you may know the CAD models for these are done, I just need to spend the cash to buy the composite materials and make compression moulds. Hey mate, hope you are doing well! Happy to see you are still following my projects after so many years! Let's talk prices then. FCC R4 aka simpit version: 299€ optional Cougar/ Warthog mounting plate + hardware: 10€ optional FCC controller: 35€ Shipping: need to research that, but I'm aiming for 10€ Edit: Prices include VAT already.

In 2.9 MiG-21 original missiles were replaced with ours, so many of problems you have described should be fixed. Rb24/J and Rb74 for AJS-37 were also replaced.

A new DCS movie, Jippiee!

I had the same error. I thought it was the program until I saw Rudel_chw post that it was working for him. So I did some investigation and found it is the CJS Super Hornet mod in my case. I disabled that mod and now Kneeboard Builder works for me again. Thank you Rudel_chw for the heads up.

Probably to protect the gyros and such from the landing impact forces. Like in the Dos Gringos song I'm a pilot: "And I'll Over-G the targeting pod with a smile on my face!"

Labels look good without saltwater in the air.

When I got 64gb of memory I started using Primocache to use part of my memory as a super fast cache. I have 12gb for my Windows drive and 12gb for my App drive. Can't say it helps DCS directly, but it does improve overall system performance.

100% necessary. Ideally we should also have easy ways of accessing what a specific unit or group has detected. Options for sorting by detected type (plane, missile, etc) would also be nice.

The first type of data to discuss is sending and receiving messages through the COM page. Select COM and then SEND from the Message (MSG) options along the bottom. We now have three options, send a text message, send current mission data, or send either Mission 1 or Mission 2 data. To send a text message, select TEXT from the top row and then you can choose to send a Mission Planning System, or MPS, preconfigured message, or a FREE text message. To send an MPS message, select the push tile next to the message you wish to send, and then select SEND. It will then send this message to all Team members within the Gunslinger, Preset 1, network over the selected radio on the EUFD, in this case the VHF. To send a free text message, select FREE and you’ll then be able to compose a message of four lines using the keyboard unit. As you might imagine, the TEXT 1 to 4 allows you to compose each line, with a maximum of 44 characters in each line. Once satisfied with your witty message, select SEND to push over the selected radio and team member network as set on the EUFD, box. If you wish to send over a different radio, use the rocker on the far left to move the box symbol to the radio that you wish to transmit over. Note that you will be listening on all the radios based on the selected frequencies. If though you send a message and a recipient aircraft’s modem does not acknowledge its reception, you’ll see an XMIT NAK and the transmitting radio message on the EUFD. This means that the transmission was not acknowledged, which may be caused by terrain blocking the line-of-sight to the recipient, or if that recipient isn’t monitoring that frequency for datalink messages. In addition to sending messages, you can also receive them. When you receive an MPS or FREE message, you’ll see a notification on the EUFD and an REC, or Receive, option will appear next to SEND within the MSG bracket on the COM page. Upon selecting REC on the COM page, the list of received messages is displayed, and you can select them to review them. Pressing COM, we will select SEND again, but this time select Current Mission. From here, we can select our entire Waypoint and Hazard file, our entire Targets and Threats file, or our entire Control Measures file, Laser Codes, Routes, or All to our Team members on the Gunslinger network over the selected radio, in this case VHF to L1, Preset 1 Gunslinger. For example, if I have numerous Targets created, I can select TGT-THRT from our SEND Current Mission page and press SEND to provide all Target points at once to each Team member within the Gunslinger network. The first report we’ll discuss is Present Position, or PP. This is the current location of our helicopter and those of our Primary members. As mentioned earlier, this is a static position that is not continually updated. For it to update, you’d need to send a new one that would replace the prior one. To send our PP, we select RPT, or Reports, select PP, and then select SEND to L1 over the VHF. If wish to request a PP from our Primary members, we select Report, select PP, and at the bottom where is says MSG for Message, toggle that from SEND to Request, or RQST. As before, then press SEND and all Primary members will send you their current PP. Before leaving Reports, one last item to note is that we can select our aircraft to automatically reply to the receipt of data by setting REPLY to AUTO, or if we want to reply to it only manually, we can set it to OFF. Last, we can also send individual Waypoints, Hazards, Control Measures, or Target-Threat points on our TSD to Primary members. To do so, enter the TSD POINT page, select XMIT, cursor select the point you wish to send, in this case a Control Measure, select which Primary members you wish to send it to, and then press SEND. You can also manually enter the index of the point using the keyboard using the POINT option at L1 instead of selecting it with the cursor. If we receive a point, we’ll see a white REC on the left side of the TSD. If we select to receive that point from within the REC list, upon which pressing displays point on our TSD. NOTE 1. As with the real-world AH-64D, the DCS version cannot exchange data with other aircraft like the F-16C, FA-18C, and A-10C. NOTE 2. From the RPT sub-page of the TSD, you can elect to set the REPLY to automatically (AUTO) send data that is requested of you from other network members, or you can set to OFF and manually reply with the requested data. NOTE 3. As always, these videos provide a preview of an upcoming feature to assist you in understanding a new feature. Later, it is quite possible that the feature will change, and the feature functionality has changed. As much as I’d like to, I lack the time re-record these videos.

Looks amazing

So thrilled by the upcoming changes to A/A radars. Amazing steps towards a more realistic simulation. Enviado desde mi ELE-L29 mediante Tapatalk

That's actually incorrect. 161 MHz is in the marine VHF band, that's absolutely FM only. The only band that you can choose manually is 225 to 399.975 MHz.

Не понял, переспроси. Неуважения с моей стороны не было, видимо что-то привидилось. Будь добр, следи за собой, а я сам разберусь, как мне себя вести, без твоих подсказок. Прежде чем учить кого-то жизни, научись сам. По поводу иИ. Мне кажется, такого рода изменения могут поломать уже существующую модель.

Yes indeed, also from me: Congrats! and PM sent

Great achievement [emoji122][emoji122] !! PM sent :) Gesendet von iPhone mit Tapatalk

Thanks a lot guys! J.P.

Look for the next F-15E update.

Ok... Then I suggest a solution to cast a shadow over an MFD by pressing and holding the right mouse button on its screen. For I wouldn't like to have another 3 or even 4 buttons to bind. Edit: this wouldn't break immersion even in VR because for a shadow you have to get one hand from the HOTAS and use it for this purpose in a similar way.

AMD released new preview drivers with Frame Generation (AMD Fluid Motion Frames) yesterday. Compatable with 6000 Series as well now.

I think it's a good idea to think that anything that Jabbers posts is already posted by one of the devs in the discord. They've been posting a lot in there as of late.

Siehe einfach einen weiter oben den Post von Yurgon. Lies die verlinkten Vorkommnisse und welche konkreten Probleme dadurch entstehen und entscheide halt für dich selber aber informiert. Ist halt blöd, wenn der Algorithmus in deinem Onedrive ein Foto fälschlich als "Nicht den Nutzungsbestimmungen entsprechend" registriert und daraufhin dein MS Account gesperrt wird. Extrem ärgerlich wenn auch alle verknüpften Services wie Outlook/O365, Teams, Onedrive etc. gesperrt sind incl. der Möglichkeit dich an deinem Rechner einzuloggen und wenigstens mit MS Kontakt zu suchen, um das zu klären... Extremst dumm, wenn du niemanden überzeugen kannst, dass das ein Fehler bei denen war und du nur unter extremen Schwierigkeiten an die Daten auf deinem Rechner kommst. Zu verbergen hab ich auch jede Menge. Zum Beispiel Kontoverbindung, Sozialversicherungsnummer, Personalausweisnr , eigentlich alles was man zum Identitätsdiebstahl nutzen kann, Details zu Krankengeschichte, Finanzunterlagen, private Daten meines Freundeskreises (Adressbuch) die ich grundsätzlich nicht an Fremde weitergegeben darf, Passwörter und zig andere Sachen, die nicht unbedingt in falsche Hände geraten sollten, wie bspw. geschehen beim Playstation Network Hack, dem Hack bei Visacard, dem Hack letztens bei MoveIT oder unserem regionalen ÖPNV Anbieter der gerade versucht rauszufinden welche meiner Daten bei ihm "abgezogen" wurden... P.S. ich war auch noch nie Opfer eines Datenleaks durch eine gehackte Firma... bis Anfang des Jahres, dann kam der Brief der mich darüber informierte, dass ich jetzt in den nächsten Monaten/Jahren bitte beobachten soll "ob es ungewohnte Transaktion" gibt, weil sie noch nichtmal genau wissen, welche Daten abgezogen wurden. Letztens habe ich auf Discord versucht ein Foto meiner Ferse (Fuss) bei Discord hochzuladen und der Pornofilter hat meinen Hacken vermutlich für eine "weibliche Brust" gehalten! (Weil rundlich und Hautfarbe?!). Keine Ahnung auf welchen Fahndungslisten ich jetzt, als potentiell Auffällig geführt werde. Aber das hätte evtl. schon reichen können, um mit dem Account stress zu bekommen... wegen einem Foto von einer wundgelaufenen Ferse, weil ich mir auf ner Flugshow ne Blase gelaufen hab?

Thank you @Tim_Fragmagnet , I appreciate your efforts to simplify the description of this issue. The issue is now reported internally. Sorry for the delay.

Adding more IRL content on the Ka-50: Pictures of Ka-50 Bort #25: https://www.net-maquettes.com/pictures/kamov-ka-50-hokum-walkaround/ Pictures of Ka-50 Bort #23 (blue cockpit): https://ionovmike.livejournal.com/3756.html For refernce, there were until not long ago, still six Ka-50´s at Torzhok: - Ka-50 Bort #20 - Does not fly anymore. - Ka-50 Bort #23 - Maintained cockpit and basic equipment, might be able to fly, but isn´t flown. - Ka-50 Bort #24 - Is supposedly now moved to Voronezh (no confirmation) for studies within the aerodynamics. - Ka-50 Bort #26 - Does fly actively. Around 100 hrs per year. - Ka-50 Bort #27 - Does fly actively. Around 50-100 hrs per year. Apparently, these helicopters aren´t only used for testing equipment. The army still believes in the concept of a single-seat attack helicopter. Thus, these helicopters are flown in the manner of a study for potential future applications within tactics and strategy. I´ll also add pictures of the Ka-52 (Bort #92): https://ionovmike.livejournal.com/3492.html At the time of the pictures being made official, there were four Ka-52s on the Torzhok airfield. - Ka-52 Bort #92 - Flown actively. - Ka-52 Bort #93 - Flown actively. - Ka-52 Bort #94 - Flown actively. - Ka-52 Bort #95 - Flown actively. Enjoy!

I dunno if that' been discussed before but will the radar improvement for the F/A-18 and F-16 eventually find their way to other platform (FC3 AC for example) or is the code used is too different for that ?

The whole section on A/A radar… Wonder if such complexities will also be transferred to ground based radars/ SAMS etc in the future. Sounds interesting, love the fact that systems are becoming that in-depth.

Should I do a thread with all the pictures of Mirage F1CT I have and will take? I have access to a Mirage F1CT.

You are welcome guys. Yes, P3 is also added. There are 3 "p" versions now: P3 and P5 with reduced smoke motor, and original P with smoky one.

Look - and it’s severely degraded footage

You know, it's funny. Most of the time, using general (let alone extreme) examples to explain something on these fora and ED in particular, is brushed off as "it's not the exact airplane / year / serial number / conditions". And here you are bringing an SR-71 in a F-16-related conversation... I appreciate the thread has now been labeled "correct as is". Can we at least get an informative explanation as to why it is correct as is (other that the SR-71)? Can we get the same accuracy in being told why something is correct as is, as we are required to provide when reporting a bug? I, for one, would like to know and learn from the devs, why the F-16 engine is running 90% RPM at MIL power at higher altitudes, and that explanation should be referred to the F-16 itself. Seems only fair... EDIT: and just to be extra clear, I am not saying it isn't correct as is. I am pointing out it does behave differently from any other jet engine in game, and I would like an explanation as to why the F-16 in particular sees this effect.

Присоединяюсь к просьбе сделать радиоменю ([\]{F1....F12)) в виде листаемого списка, чтобы можно было отдельно назначить команды именно на него. Либо на три кнопки, либо ещё удобнее было бы использовать энкодер с кнопкой для навигации по нему. В ВР сейчас использование для этого функциональных клавиш - сплошное мучение.

Please read EULA before you get into troubles or contact ED to get other type of license. Seriously, FC3 aircraft on sales are $7, how much cheaper you want it? There are 2 free aircraft. If you "waste" a trial of one module just trial another aicraft - there are over 40 types!

Thanks Guys for assisting Oban. OSA One and OSA Two twins are both in DCS. Making final adjustments.

Gotta be real, this feels like a really trashy way to treat your customers, by the ED leadership. First, we dont even get told about this change at first and had to learn it the hard way. Thats unacceptable from the get go and shows a blatant disregard for customers and community. And secondly, this is ED arbitrarily changing how we can access the game. This is some kind of "pray I dont alter the deal further" moment. We have no choice, we werent asked, not told. Just ED changing such a fundamental thing, a principle of access the game was sold on, and we have to suck it up. This is only made worse becasue we already put up with so much. We pay silly amounts of money for modules, we accept a deeply buggy game, and we crowdfund eternal early access modules with often questionable road maps. If anything, ED should give back more to the community, rather than treat us like this and take away features. I planned to purchase more modules, eg the F-4E instantly at release, but Im gonna put those on hold. Not just because Im treated badly, but because this makes clear that I cannot trust ED to not make changes against my interest. If they did a decision like this as if its nothing, what else will they do in the future?

@myHelljumper any update on progress on this issue? Can you push it internally? It’s a critical system for the Mig-19 modules in my opinion Your message was more than two years ago. thank you, kind regards. Snappy

Interview with Sklang and Chess. Thank you guys!! Work continues YOYO but at a slower pace. However, I think that soon I will be able to show something new again and I hope that I will please you.