RafaPolit

With what? The Thrustmaster Cougar MFDs? No, not only is one "not included", there is no "specifically made for them" display, so that's the reason of this thread, to show different implementations of different options available.

I wanted to extend my huge thanks to this post! Really changed my experience. It even works for night missions, I created a couple of profiles with different values for white point and gamma and I shift through them quickly depending on the scenario. This is a game changer if you have external MFDs. Big thanks again! Rafa.

This looks incredible!!! I understand winter is "different" and more difficult, but this is exactly the type of response to "critique" or "suggestions" that puts a smile on people's faces and makes us be more "happy" with our purchases. This, for me, changes this map from a: "very niche scenario", to a "wow, you can do anything but winter", and for that Caucasus is perfectly fine. I really love the seasons and the effort put into this. Thanks!!!

I wanted to share a big thanks to this thread, the community and especially to @Gierasimov! The suggestion to go with the VSDISPLAY 7" 7 inch 800×600 4:3 CLAA070MA0ACW LCD was ABSOLUTELY FANTASTIC! I'm going to share a little bit of my process: I was planning on building metal frames to hold the screens and then the MFDs on top, all to house larger screens that actually made little sense and I was not happy about wasting a lot of screen size. Your suggestions really put my mind at ease that the CLAA070MA0ACW could do the job... I couldn't be happier! Not only are they almost a perfect fit, I was able to install them without any alterations to the MFDs, no alterations to the LCDs, and I was able to still use the MFD stands, so the amount of work you saved me is really undescribable. In case my approach is useful to others, here's what I did and what was required: - 4 x 3cm M3 screws (the length will depend on the fixtures you find, M3 is a good thread but just pick something that fits on the original holes) - 4 small washers and nuts for those screws - Some thin metal plates, ideally with a hole that can allow the M3 screw a little wiggle room so you don't need to measure everything down to a thousand of a milimiter - Larger washers to secure the bottom part of the LCD - 5mm nuts to serve as "spacers" between the metal plate and the MFD - 1mm double sided tape (this can be any thickness, but you need to account for the 4mm of the bezel for the LCD plus the thickness of the tape when choosing the separator nut) How I did it is: - Start by securing the bottom part of the LCD with the bolt a larger washer and then the washer and nut like in the picture. This is ideal, because the LCD bezel is at its PERFECT height when resting on a bolt going through the bottom-most holes, which is a god-send! No need for crazy perfect measurements, it just aligns. - With this two bolts securing a little bit the LCD, center it horizontally so that you have symmetric "air" on the sides of the MFD to the SCREEN AREA (crucial here, don't center it to the outer size, but the inner screen area) - Once it's roughly centered (the beauty of this method is that you don't need to be milimetrically precise with anything!), secure the metal plate to the bezel with double-sided tape, using the bolt as reference (here's where it's handy if the hole in the plate is slightly larger) You are DONE! Now simply: - Put the 5mm spacer in the bolt, secure the back element from the Cougar MFDs, and place a nut and bolt (please note that, in this picture, the plastic frame is upside down, that is not the way to mount it, mount it normally with the opening to the top part as in the next image) I used the MDFs frame to further secure the PCBs that come with the LCD: And with that, I have my functioning MFDs with screens, for less than the WinWing screens. Not a LOT less, these are: - $90 for the MFDs + $160 for the LCDs (with HDMI breakout PCB and remote control!) + $10 of nuts and bolts = $260 - WinWing solution will offset you $349.6 and you don't have to do a thing, so it's note like a night and day difference Still, I love the result, couldn't be happier!!! And I couldn't be more grateful to @Gierasimov for sharing his "discovery" of these marvelous screens! The fact that I can use the Thrustmaster stands is a huge advantage for versatility and upcoming options. Thanks so much! Rafa.

I have to agree with the general hype about this map. The new images look great, and the new airports will certainly make for a much wider possibilities. I don't think anyone would go to the Big Ben to check the time of day, but that attention to detail certainly shows in many places and that is encouraging. I have been open about my frustration about the lack of seasons in this map, but its size and the addition of larger cities could very well make up for it. Looks really great. Thanks for sharing.

I've had this happen to me as well. I have not been able to pinpoint a specific culprit, though I have a couple of things that I blame for: - The iron may get a little colder when exchanging heat with a large component or one that can sink a lot of heat - I may try to "fuse" the solder when the component's leg is not warm enough - The iron's tip get's coated by the flux or rosin and it gets charcoaled and I no longer have the tip correctly covered in solder I blame a combination of (or all) those three things. When that happens, I wipe the iron clean with a cloth or wipe, I re-tip the tip with solder, wait for it to heat up back nicely, and then resume soldering. I would describe them as "mini spikes" or "uneven surface" rather than whiskers, but I know exactly what you mean.

Hello. I really appreciate this effort, I had a similar issue and was surprised how little documentation there is to use Witchcraft with modern OSs and NodeJS versions. However, your solution seems to have taken the "long way home". If I may suggest, the changes required are much fewer! You simply need to: - Remove the included NodeJS version with the newest one (at the time of posting its 18.13LTS) - Implement Socketio correctly with just this two lines: var server = app.listen(port, "0.0.0.0") var io = require('socket.io')(server); instead of var io = require('socket.io').listen(app.listen(port, "0.0.0.0")); That's really it. No other modification required, and this doesn't force a global installation of npm packages and other unnecessary stuff. If you try it and double check it to see it works, I'd be happy to support your Fork of the original asset. If not, I'll probably create my own with this much simpler instructions. Best regards, Rafa. ps. My solution does not address the automatic opening of a browser pointing to localhost:3000 , but that's really the only thing missing.

Good afternoon friends. I was wondering if there is a flow that would allow me to run everything I need in my main DCS machine and access some kind of profile / monitor / export / view from a remote browser preserving touch functionality. This is the scenario: I would configure DCS with Helios? Iris? To export all the views I need... then I access the DCS machine via IP with a web browser that can see AND INTERACT (this is crucial) with, for example, the F-16 ICP screen. So, I want to export the view of the ICP (and perhaps DED) and access it via a remote web browser. Why haven't I found a solution to my needs? Mainly because my remote PC is running Ubuntu on a RPi3. I have found solutions for Android Tablets, it would also work for remote windows machines that could run Helios on them, but my machine needs to access a somewhat different flow. Any ideas where to start looking? Thanks a lot! Best regards, Rafa.

Thanks! This is very helpful! For me, Winwing looked great, but logistics to send to my country are a nightmare, and Amazon US is better with an importing service, so I have the Thurstmaster MFDs incoming. Also, call me a snob, but I fly the F-16 more than the Hornet and I wanted the MFDs to be more like the F-16! Thanks for the info.

Oh, that is really helpful! I was thinking of purchasing this 8" ones: https://www.amazon.com/dp/B07V7GGWMM/?coliid=IKDYNWPSFHLQS&colid=39QRGRVFCK9MF&psc=1&ref_=lv_ov_lig_dp_it Unsure if the 7" will fit. The 7" are more expensive by a few bucks, but maybe the tighter fit makes them easier to work with. Have you experience with the larger ones? Thanks for the time to help. Best regards, Rafa.

This looks exactly what I would want. Quick question, there is a slight "missalignment" of the buttons to the screen. Is there no way to make them more precise due to the nature of the screen? Also, how is the visibility of things like TGP? Is the resolution enough? Thanks in advance! Looking really nice.

I am reviewing the training lessons, and I have Lesson 19 and Lesson 21. Lesson 20 does not appear. This could be wrong naming, or something else gone wrong.

What does any of the conversations here have to do with the original thread that was posted almost a year ago? I have yet to purchase the Flaklands map, and I would really like a bundle of the two. It would make me a faster buyer. I'm buying the F-15 no matter what, but a bundle with the map would be something I really considered. If not, I'm probably not going for the map.

I'll add my vote to this. +1 I see no reason after selecting Ctrl+F6 if you are following a bomb till hit that you wouldn't want to remain there as opposed to returning to the cockpit. For that you use F1 with no timing constraints. On the other hand, timing the F11 is really tricky as some bombs may start a very high process (like the GBU-105) and you have to hit the F11 perfectly or you are back at the plane missing the in-situ action.

Development is a complex process. Some times you make advancements that you can showcase weekly, others you are coding how a building could collapse or something similar that could take weeks and you have nothing to show for. That's why some folks like Heatblur will show nothing until release, while others like Razbam show continuous updates and everyone gets anxious as to when it's coming. I'm sure that when they have something to show, they will do so with as much flare as possible. Rafa.

I believe this is a bug with CTLD, I have submitted the following bug report: https://github.com/ciribob/DCS-CTLD/issues/84 Changing line 5470 to `_defaultEnemyUnit` does the trick, in case anyone is facing this issue.

As an extra info, if I disable the smoke (third argument to "false" on the JTACAutoLase function), everything works perfectly, but, obviously, I don't see smoke.

Good afternoon! I have been enjoying flying with JTAC laser designation in the Through the Inferno servers. I tried to create a simple JTAC scenario using CTLD and the JTACAutoLase feature. I am getting an error attempting to index local "_enemyUnit" con the 'createSmokeMarker' function. What do you believe could be missing from the very (VERY) basic implementation I did? I can share the .miz file, but maybe the log is enough, so I'm attaching the log, if someone thinks that adding the mission file is useful, I'd be happy to attach it: 2023-01-09 01:04:11.013 WARNING SCRIPTING (Main): MIST|init|1206: Init time: 0 2023-01-09 01:04:11.013 INFO SCRIPTING (Main): Mist version 4.4.90 loaded. 2023-01-09 01:04:11.014 INFO VISUALIZER (Main): Preload() camera=-281894.172614, 944.316886, 645324.389769 radius=60000.000000 2023-01-09 01:04:11.014 INFO EDTERRAINGRAPHICS41 (Main): ITerrainGraphicsImpl4::forceLoading(): pos=(-281894, 944.317, 645324), radius=60000 2023-01-09 01:04:11.513 INFO EDTERRAINGRAPHICS41 (Main): surface5 clean up LOD 0: left 2 released 20 2023-01-09 01:04:11.514 INFO EDTERRAINGRAPHICS41 (Main): surface5 clean up LOD 1: left 6 released 45 2023-01-09 01:04:11.514 INFO EDTERRAINGRAPHICS41 (Main): surface5 clean up 2.338500 ms 2023-01-09 01:04:17.079 INFO VISUALIZER (Main): Preload() finished 2023-01-09 01:04:17.146 INFO APP (Main): Screen: mission_offline 2023-01-09 01:04:17.161 INFO Dispatcher (Main): precache units resources in slots 2023-01-09 01:04:17.163 INFO LUA (Main): Lua CPU usage: metric: average mission loading: 17.5165 % 2023-01-09 01:04:17.163 INFO Dispatcher (Main): loadMission Done: Сontrol passed to the player 2023-01-09 01:04:19.684 INFO APP (Main): MissionSpawn:spawnLocalPlayer 3,F-16C_50 2023-01-09 01:04:19.689 WARNING EDCORE (Main): Source mods/aircraft/f-16c/cockpit/shape is already mounted to the same mount /models/. 2023-01-09 01:04:19.701 INFO VISUALIZER (Main): cockpit ILV loaded 2023-01-09 01:04:19.722 INFO COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver/transmitter "UHF_RADIO" with id - 0 2023-01-09 01:04:19.722 INFO COCKPITBASE (Main): WebRTC VOIP init: enabled VOIP capability for radio UHF_RADIO 2023-01-09 01:04:19.722 INFO COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver "ARC-164 Guard Receiver" with id - 1 2023-01-09 01:04:19.722 INFO COCKPITBASE (Main): WebRTC VOIP init: added guard receiver - ARC-164 Guard Receiver 2023-01-09 01:04:19.723 INFO COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver/transmitter "VHF_RADIO" with id - 2 2023-01-09 01:04:19.723 INFO COCKPITBASE (Main): WebRTC VOIP init: enabled VOIP capability for radio VHF_RADIO 2023-01-09 01:04:19.724 INFO COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver "Base ILS localizer receiver" with id - 3 2023-01-09 01:04:21.038 INFO COCKPITBASE (Main): lua state still active DED, 26 (status undefined) 2023-01-09 01:04:21.038 INFO COCKPITBASE (Main): lua state still active EHSI, 28 (status undefined) 2023-01-09 01:04:21.038 INFO COCKPITBASE (Main): lua state still active UHF_RADIO, 36 2023-01-09 01:04:21.038 INFO COCKPITBASE (Main): lua state still active VHF_RADIO, 38 2023-01-09 01:04:21.038 INFO COCKPITBASE (Main): lua state still active INTERCOM, 39 (status undefined) 2023-01-09 01:04:21.039 INFO COCKPITBASE (Main): WebRTC VOIP init: registered radio receiver "Base TACAN receiver" with id - 4 2023-01-09 01:04:21.039 INFO COCKPITBASE (Main): lua state still active MACROS, 52 (status undefined) 2023-01-09 01:04:21.039 INFO COCKPITBASE (Main): lua state still active TGP_INTERFACE, 58 (status undefined) 2023-01-09 01:04:21.040 INFO COCKPITBASE (Main): lua state still active DTE, 65 (status undefined) 2023-01-09 01:04:21.043 INFO WORLDGENERAL (Main): loaded from mission Scripts/World/birds.lua 2023-01-09 01:04:21.053 INFO LUA (Main): Lua CPU usage: metric: average mission execution: 91.4732 % 2023-01-09 01:04:26.708 INFO SCRIPTING (Main): I - CTLD - Loading version 20211113.01 in 2 seconds 2023-01-09 01:04:28.691 INFO SCRIPTING (Main): I - CTLD - Initializing version 20211113.01 2023-01-09 01:04:28.691 INFO SCRIPTING (Main): T - CTLD - ctld.alreadyInitialized=[false] 2023-01-09 01:04:28.691 INFO SCRIPTING (Main): T - CTLD - force=[nil] 2023-01-09 01:04:28.691 INFO SCRIPTING (Main): Generating Laser Codes 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generated Laser Codes 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generating UHF Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generated UHF Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generating VHF Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generated VHF Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generating FM Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Generated FM Frequencies 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): Searching for Crates 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): END search for crates 2023-01-09 01:04:28.692 INFO SCRIPTING (Main): CTLD READY 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): D - CTLD - ctld.JTACAutoLase(_jtacGroupName=JTAC1, _laserCode=1688 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): T - CTLD - _laserB=6 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): T - CTLD - _laserCD=88 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): T - CTLD - _frequency=40.4 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): D - CTLD - ctld.notifyCoalition(_message=JTAC1, lasing new target, BTR-80. CODE: 1688. POSITION: @ 42 14.461'N 42 02.832'E - MGRS 38T KM 56371 80758) 2023-01-09 01:04:32.995 INFO SCRIPTING (Main): T - CTLD - _radio= .freq=40.4 .name=JTAC1 .mod=fm 2023-01-09 01:04:32.995 ERROR SCRIPTING (Main): Mission script error: [string "C:\Users\xxxx\AppData\Local\Temp\DCS.openbeta\/~mis00000EBC.lua"]:5618: attempt to index local '_enemyUnit' (a nil value) stack traceback: [C]: ? [string "C:\Users\xxxx\AppData\Local\Temp\DCS.openbeta\/~mis00000EBC.lua"]:5618: in function 'createSmokeMarker' [string "C:\Users\xxxx\AppData\Local\Temp\DCS.openbeta\/~mis00000EBC.lua"]:5470: in function 'JTACAutoLase' [string "ctld.JTACAutoLase('JTAC1', 1688, true, "all", 1)"]:1: in main chunk 2023-01-09 01:04:34.697 INFO SCRIPTING (Main): T - CTLD - jtacTargetsList for JTAC1 is : .1= .dist=985.09104359134 .unit= .id_=16777472 2023-01-09 01:04:59.635 INFO LUA (Main): Lua CPU usage: metric: average mission execution: 4.9010 % 2023-01-09 01:05:02.052 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] Thanks in advanced, best regards, Rafa.

After applying certain textures, I had to reload content in a couple of places to have the shaders take effect: - Tools > reload shaders - Tools > reload models (this usually did the trick) - Tools > reload textures When that failed, I usually first loaded all textures and THEN went into File > Load Model I know this are stabs in the dark. It's just some of the tips that helped me until someone with more knowledge arrives.

In Model Viewer, you load manually the order of the textures and which trumps which. In game, it happens based on certain logic / folder naming / lua definitions. So maybe it's loading them in the unexpected order?

Looking forward to trying this!! Looks great.

I may be missing something... I don't have any mission on either Marianas or Syria (I do own Syria and have both maps and installed): n

If you take the first 24 characters, it's perfectly safe. You won't have the blinking cursors, which are very useful in many scenarios though.

Thanks for the recommendations! I own both Zone 5 and the Fear the Bones campaigns, but I have not yet started them, as I'm doing the Warbirds campaigns first. Thanks @draconus for recommending the "included" campaign and missions. I just finished Watching de Devildog and I agree it's another masterpiece. I like it how this missions force you to refuel in order to achieve them, I wouldn't have become more proficient on air-to-air refueling without them. Also, I had to refresh concepts like Computer Pilot delivery mode, created my own mini-mission to "train" how to take down an Mi-8 which is the perfect IR evasion machine, and also nice to do some more carrier landings. So, I concur, it's another masterpiece that plays as nicely (or even more so?) than the Training Day. So, thanks Heatblur, if this is what we can expect from the F-4, you have my money! Thanks again! Rafa. Edit: @IronMike, yeah, I fully agree with your assessment, that is why I came to compliment on the masterpiece and not complain on the minor issue I locked under the spoiler block. It is a masterpiece and I really appreciate it!

I'm going to expand a bit further: I have been even insulted in the 4YA forums for even suggesting the addition of MW50 on the Bf-109 because it is not "historically accurate". I have been "harassed" (to put it mildly) by ED and others in this community for asking for a unitary broach JSOW for the F-16 because the USAF block 50 circa 2007 didn't carry it and it would be "historically inaccurate". So if I'm going to take <profanity> from everyone because this games pursues historically accuracy above anything else, let's have historically accurate buildings. Right? If not, let's just relax on everything else as well and allow me to use MW50 in Dday missions and to bloody well be able to take down a tank with a JSON on the most versatile modern fighter we have. But to demand PERFECT accuracy from everything and then say: "hey, it's OK as long as it looks the part"... common!