BlowTorch

Fishbed 31-28 Tiger 26-28

I knew it isn't good or prepared for games, theoretically, but it has already shown me it has enough performance to run a lot of games, recent ones too, just by setting up correctly the graphics settings. Most problems it has given me are more related to compatibility issues more than low performance, so I just was hoping there were a fix. Well, then I guess I'll have to stop trying to use IR, as the rest of the sim works flawless

Yes, without effect It is a laptop, however it performs relatively well, better than I expected at first

Hardware: RAM: 8GB CPU: I3-3110M @ 2.40GHz GPU: Integrated Intel HD Graphics 4000 Software: Windows 8.1 DCS World (no steam) 1.5.4.55952 No mods ever used, only skins Settings: Textures: high Terrain textures: low Civilian traffic: low Water: low Visible range: low Heat blur: off Shadows: low Resolution: 2646x768 (1280x1024 + 1366x768) Aspect ratio:3.4453125 Monitors: custom, two mfd at left monitor Resolution of cockpit displays: 512 MSAA: off HDR: off Depth of field: off Lens effect: none Clutter/grass: 30 Trees visibility: 1500 Preload radius: 96008 Anisotropic filtering: off Flat terrain shadows: off Anything more needed? The logs folder has more than 300 files, is that normal? Also, already tested with normal 1 screen setup, but the same happens Logs.zip

Most of the aggressor skins we have seem a little bit dated... We need something more actual to train against threats before they arrive. Any volunteer wants to try this F-5 dressed as T-50-5? This is the only info/photo I could find:

I've been having this issue for a long time now (can´t remember if this happened in 1.2). When using the daylight optical targeting systems, everything looks good. But whenever I try to use infrared in any aircraft, be it the Su-25T with mercury pod, the A-10C with the FLIR modes or the Gazelle's IR, the ground changes. At night it is like if the map was illuminated by direct sunlight. It also affects cloud shadows, even at day. I haven't seen anyone talk about any bug similar to this, so I'll assume there is something wrong with my setup. Any help on what could be causing this behavior? Screenshots: 1-Gazelle with normal camera 2-Gazelle with normal camera, nvg looking good 3-Gazelle with IR camera, all map illuminated 4-Gazelle with IR camera, all map illuminated, nvg unusable, like daylight 5-A-10C with litening's CCD 6-A-10C with litening's black hot, all map illuminated, look outside cockpit 7-A-10C with litening's white hot, the same 8-Su-25T with Mercury LLTV pod, all map looks illuminated, but vehicles, buildings or aircraft remain dark. Looking at the last picture is clear it only affects the ground lighting but not objects in map, making anything look black and stick out, ruining all interest of night missions. Also, the map remains like that in any mission unless I quit and restart DCS. Any ideas that could help? Thanks

After reverting back and updating drivers, no effect. Also tried changing the graphics settings, results were the same. No mods installed, did the "DCS_Updater.exe repair" thing and it keeps happening. I think I'll have to stay out of night attacks until this gets a solution...

It may look like that, but it isn't the case as I'm not carrying any illumination rockets nor releasing flares. Also there isn't a small area illuminated, it is the whole map. I'm sure it is some kind of bug, just don't know what is causing it.

So I wanted to set up a night training mission for the A10, everything starts up normal, but when I get ready to kill things is when the problems appear: The TGP starts up with the CCD/normal camera, and obviously nothing can be seen. Then, as I select any of both IR channels (whot or bhot), the ground texture just gets all illuminated as it were daytime. Going back to CCD doesn't solve this, the ground remains illuminated. #1 shows normal night conditions and the CCD #2 just after I switch to IR, look outside the cockpit #3 it remains after going back to CCD It only affects the ground; vehicles, buildings and weapons remain dark. IIRC, the same happened with the SU25T long time ago with the LLTV pod, so it might be related to my own graphic settings. As this kills all fun related with night ops, any help will be appreciated.

For me it only crashes in one server, tested in others and worked fine

Thanks, that one worked quite well

But I would need to map an axis as if it were a simple button, can it be done? I would prefer to have two camera axis for joysticks, but I don't know why this plane doesn't have it the same way as others

Nothing?

Currently, until I can get better hardware, I'm using a xbox 360 controller, with the right stick for camera rotation the same way as the mouse. Every other aircraft I have flown can be set this way, but in the c-101 I haven't found any option to get cockpit camera movement with the right stick. At the moment I fly looking forwse the mouse. Anyone knows a way to "solve" my problem?Anyone knows a way to "solve" my problem?