BlowTorch

Alright, thanks, at least it was worth a try...

(This subforum looks like the most appropiate to post this...) First of all, I know this might look like a stupid idea, but looks like it may be able to work. My current situation: flying on a laptop, the requirements for 2.5 are too high and is effectively unplayable (not complaining, I know that my laptop is not at all made for gaming, much less for something like DCS), so for the time being I'll be stuck at the last 1.5 version. Today I thought that maybe that had changed, so I tried installing the 2.5 beta, only to find out that it is still as impossible to use on this PC as before. So, now I find myself with the 1.5 version installed, the one I fly in, and a 2.5 version with the latest updates but "useless" for me. An idea came out from this: As the Harrier has been upgraded several times since the merge, updates that I've been missing, and now I have all the files from the current version of the plane, would it be in any way possible to just substitute/copy the correct files from the 2.5 install to the 1.5 install so I can use the newer systems/avionics in the older version? I don't have any real experience or knowledge on the file structure or internal workings of DCS, but after some looking around it appears that luckily it would be somewhat possible... Also, would it work also for flight model changes or is the FM handled differently? I hope I worded it correctly to be understood, and that it is a not too stupid question, but desperate times call for desperate measures...

I think you are mixing it They should be these two lights IIRC:

En esta parte del foro se habla ingles, mas abajo hay una seccion en español, aunque considerablemente menos activa: https://forums.eagle.ru/forumdisplay.php?f=100 Ahora, para tu problema: para poder disparar tienes que asegurarte de 1º, que el avion esté cargado (que por defecto lo estará), tener asignados los botones de cañon y ametralladoras, el de la cubierta del gatillo (que esta en el stick, hace de seguro) y que esté activado el interruptor de control de armamento (no recuerdo el nombre, está en la parte superior del panel, junto a los contadores de munición). Creo que no me dejo nada. En mi T16000m tengo asignado ametralladoras al gatillo, cañón al de la izquierda y seguro al central.

I also have experienced this problem since the update, in various situations and missions, without an apparent correlation to the aircraft I'm in or AI's own plane, or his skill level. Here is a track that maybe shows part of the problem: Quick fight, me in a Harrier, AI in a Su27, 6xR73. His tasking is to engage me, set with the advanced waypoint, engage unit. Skill at excellent. The fight starts head-on at about 18km each other, 2000m alt. The first missile he fires is a good launch, within parameters, I avoid it. Then just as we pass each other, he fires another that, while having a good lock, was obvious it was going to miss. His third shot about the same, with a lock but poor shot. Then the next 2 or 3 missiles are just blind shots, into the sky, without even a lock. After some more flying and avoiding him, I put his plane in a risky situation, low and slow (VIFFing can be useful sometimes...), and he decides to just dive into the water, not even really trying to recover. Hope the track works as intended... AI in 1.5.8.trk

Looks like part of an aerobatic sequence in aresti notation: https://www.google.es/search?q=aresti+catalog&client=firefox-b-ab&dcr=0&source=lnms&tbm=isch&sa=X&ved=0ahUKEwj36vDN2PfXAhVHMBoKHVsbDOUQ_AUICigB&biw=1366&bih=656

Well, good news that you already found the cause, that's a fast working team. I'd say only the Harrier, haven't flown much other planes, but the A-10c felt normal

This first part is just an introduction, but important to see why I think this is happening. In my current situation, I'm not able to get a real computer, and I'm limited to a laptop. 16Gb of ram, but Intel HD Graphics 4000 integrated graphics card, which is probably what causes this "incompatibility". Since I started flying in DCS, I experienced a graphic bug anytime an infrared optic was used, be it the A-10C, the Su25T with the LLTV pod,... I was already used to it and just avoided using these systems, as I know it's my fault for running DCS in such a low end PC, in fact I feel lucky the rest of it works alright. The bug itself meant that whenever I turned on any infrared system that provides video feedback (FLIR modes in the litening, FLIR mode in the gazelle, -D or -G mavericks,...), the whole texture of the terrain would just "light up", as if it was unaffected by time of day, weather, shadows,... and remaining like that until DCS was closed. Don't know if I'm explaining it correctly, so see for yourself: -This is how a normal night looks: https://imgur.com/f3aGJGu -The same in the A-10C before using FLIR: https://imgur.com/JttRVjG Notice that I am using the TGP but the CCD mode, you can only see because of the runway lights. https://imgur.com/zJoGU6E -The same image, just after turning the black hot mode on (the same happens in white hot): https://imgur.com/f1TIuet So this is what happens in my case, not complaining, just so you know where this deduction comes from. Now what happens in the harrier: -The same exact mission, at the same time, and just after takeoff, no button clicking at all: https://imgur.com/Bi1Ak0u https://imgur.com/1u4EICG -When turning on the NavFLIR: https://imgur.com/aVqKmvb In this case turning on the FLIR didn't do anything as the effects of this particular bug were already in place since the beginning. The same happens with a cold start, or in any situation, really. What you have seen is what lead me to think this: Is it possible that the NavFLIR is being rendered in the background constantly, even if the system itself is turned off? That would explain why my "bug" with infrared looks this way in the Harrier, as something permanent instead of only after turning FLIR on. Also it gave me the idea this could be related with the lower framerate compared to other modules (also experienced by me), and that seemed to be related with the aircraft location and orientation. So, maybe everything inside the pilot's FOV (including what should be outside of the sensor FOV) is being passed through the "IR filter simulation" (or however it works in DCS), even if the NavFLIR itself is switched off. This part would explain why the framerate is lower than other modules, which shouldn't be even with the NavFLIR on. Also why it looks so dependant on position and heading, being really dependant on how cluttered/how many objects are in line of sight/inside your FOV. This whole post shouldn't be read like a complaint, since I accept that the bug that allowed me to see this is my fault and there is nothing any dev could do about it (other than giving me a free better PC?). Instead it is intended to provide a possible cause of a problem others have experienced, the low FPS. Any thoughts? (BTW, what is wrong with the screenshots that can't be uploaded in a normal way? Here are all the screenshots: https://imgur.com/a/3wnZc)

Thanks, didn't know what was the problem, don't recall reading any comment about this. First impression is that it's an impressive work, you must feel really proud of it...

(As I understand it): In the left panel, to the left of the gear lever there is the antiskid switch. Also the NWS/target undesignate button on the stick. To turn, you have three options: 1- switch to antiskid and hold NWS button==normal steering 2- switch to NWS and NWS button not pressed==normal steering, no antiskid 3- switch to NWS and hold NWS button==high gain steering, for tight corners

I don't know if I'm missing something... Can't slew the ARBS in TV mode with the analog stick in my TWCS. The default keys work alright, but can't make it work with the stick. No problems when setting up controls, but it doesn't do anything when trying to slew, also it works properly for other aircraft. Any idea?

In the video, he says the nozzles are at 45 degrees when firing. I'm not an expert, but having the nozzles at any setting other than 0 sound like a big "no", it would make the hud compute wind in a wrong way. Anyone with real knowledge knows about the correct procedures?

From the email notification (not mine):

Now that we are asking for "fictional" liveries, I think this one looks nice. I never really liked the tigermeet liveries, but for me this one is an exception (though I might be a little biased). Bonus: dirty hornet (a livery like this one would be nice too)

Welcome to the club, at least I know I'm not alone. Most likely is related with Intel integrated graphics and some incompatibility. Here you have the response given by SkateZilla when I asked about this some time ago: (https://forums.eagle.ru/showthread.php?t=173643) I get our laptops are not at all designed for high performance, but it would be nice to know what exactly is causing an incompatibility like this only on IR systems, as the rest works as intended.