Hunden Ynk

If you post a track, I'll have a look...

I just tap the regular break button to disengage the parking brake, does that work?

Or keep the target centered manually, fiddly, but works quite OK.

Yeah, I'm also seeing this, or maybe something similar, since it has happened on other missions as well. Reloading the mission may work, but this one in particular seems very crash prone, I've only managed to load it once. Manually loading the mission, that is outside of the campaign always work, so it's something to do with the campaign. Crash log: # -------------- 20140227-112953 -------------- # C0000005 ACCESS_VIOLATION at E89791DE 00:00000000 00000000 00000000 0000:00000000 E89791DE 001BE9C0 0000:00000000 ?uninitObject@woCar@@QEAAXXZ()+1E E896C815 001BEA10 0000:00000000 ??1woCar@@UEAA@XZ()+C5 E896D586 001BEA40 0000:00000000 ??1woCar@@UEAA@XZ()+E36 F0947E12 001BEA90 0000:00000000 3FD233CA 001BEBA0 0000:00000000 3FD24BD9 001BEEA0 0000:00000000 3FD1FA09 001BF160 0000:00000000 E91CDDAA 001BF190 0000:00000000 ?sendOutputSymbol_@FSM@Common@@AEAAXI@Z()+2A E91CCF78 001BF1D0 0000:00000000 ?enterToState_@FSM@Common@@AEAAXI@Z()+C8 E91CD846 001BF200 0000:00000000 ?onSymbol_@FSM@Common@@AEAAXI@Z()+1B6 3FD22EAF 001BF260 0000:00000000 3FD399F4 001BF290 0000:00000000 3FD39C1B 001BF2C0 0000:00000000 3FDCCDFB 001BF330 0000:00000000 3FDCD656 001BF950 0000:00000000 3FDD0658 001BF990 0000:00000000 7730652D 001BF9C0 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D 7753C541 001BFA10 0001:0002B541 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

I dislike FXAA, since it has a tendency to blur way more than the aliased edges, leading to lost texture detail and blurry UI elements. SMAA is pretty darn good for a post-process AA solution. But to me, MSAA is always preferable, if it's supported by the game and I have the performance to spare. In DCS on my rig, I get about the same FPS hit with MSAA as with SMAA. So a post-process solution is not always superior in that regard either.

My money is on Intel, Dell used to be (and still is?) 100% Intel. Trust your own measurements SkateZilla!

MSFFB2 with CH Fighterstick Handle. I'm very happy with that combo!

I found this interesting, it's mostly about multi-threading, but the quoted part is relevant to this discussion. Source: http://www.codeproject.com/Articles/35679/Parallel-computing-and-processor-affinity-Never-un My experience within DCS (running on an i7 2600k@4.4ghz) - it makes no measurable difference either way (same with HT on/off). Do note that I'm pretty satisfied with the performance of the game, save for the usual suspects of cluster munitions etc. I'm just an habitual tinkerer.

Vodka or Apple pie, why don't we have both?! ;)

Brightness/Contrast/Gamma/Saturation-sliders in the options. I'd love to see that!

You can work on line nr 327, this one: return float4(composite * OV * 0.95, 1.0);Increase the 0.95 part if you want more contrast. Edit: Sorry, that's not contrast, it's exposure, which I would have remembered if I read what I wrote later. Sigh. Edit2: Tinkered a teensy bit with the snippet, I can now use negative Offset values without DCS turning all DISCO. That combined with increased Exp, will give contrast proper. This is what I use, for brightness and gamma controls as well: return float4(pow(saturate(composite * OV * 0.95 + 0.00), 1.0/1.00), 1.0); // ---- ---- ---- // Values to adjust: ^ Exp ^ Offset ^ GammaOf course it's silly to add 0.0 like that, if you're happy with your brightness levels, just remove it, same with the gamma part - which brings you back to the original line.

http://forums.eagle.ru/showpost.php?p=1857363&postcount=982 ps. RButton is Right mouse button

Glad I'm not the only one. ;) I can understand this picture: Having mesh resolution being adaptive to camera distance should improve performance in general no, not just GPU-memory consumption? Edit: Thanks EtherealN and SkateZilla

No trash here! Probably because the FF setting does not effect the rudder, meaning, it's always behaving like your stick does when FF is set to off.

Hi archorn! Are you sure that's a Force Feedback stick? Is it this one: http://www.cyborggaming.com/prod/v5stick.htm? That page doesn't mention it having that feature, and hiding it wouldn't be too business-savvy. ;) If your stick is not FF, then disabling that option will probably fix your problem. Central position trimmer mode should not be used for FF gear, I just don't think it has any effect then. It means; instead of a set time period for the new center position to activate after you release the trim, it will activate once your control is centered. But again, if your stick is FF, you don't have to bother about re-centering, hence that setting not applying.

What's the meaning of this: Google just handed me a bunch of research papers - making me feel super stupid - is it some kind of LOD-thingy, but for the terrain?

It's normal, the Windows thread scheduler will allocate resources on the cores as it sees fit. Not keeping one application to one core, and bouncing things around like that is no problem. So, a large bunch of short running tasks in sequence, might make a (largely) single threaded application, like DCS, look like it's doing things in parallel, when it's not. The total load percentage is a giveaway; say you have four cores and the task manager displaying a total load of 25 % with one running application (disregarding any background tasks), that's a sign of a single threaded program running to the max.

Yeah, there's one without FF, named Precision 2. Perhaps you could still use it for spare parts if needed, buttons, pots, etc. Considering how similar to the FF stick it looks, it's likely to be similar on the inside as well.

The voice language follows the country of your flight. But if you want an Russian flight with English voices, you could probably overwrite the Russian files with the English in "DCS World\Sounds\Speech\Sound". Though I haven't personally tried it, since I like that feature.

I haven't seen any difference. Different parts of the map looks more or less good. Plus, the terrain is utilizing normal-mapping, if I'm not mistaken that is. Allowing the "interior" parts of the mesh to appear more detailed than they really are, a trick that fails when exposed as silhouettes.

Thanks for the Ka-52 picture Fri13 (love that chopper). Interesting, I thought it had the radar in its nose, perhaps that mast thingy is some other sensor? And no it doesn't look that ugly. ;) I like the roof-mounted optics, there's also a version with that sensor mounted under the fuselage, which in pictures often is facing backwards - 360 vision (or just the caged position)?

So you're not :joystick: enough :). Great find! Cover those pesky LED's...

The added height of an co-axial rotor design is already on its minus list compared to a traditional one rotor layout. It increases drag. That's one reason we got the retractable landing gear. Seems hard to mount sensor gear on top of that, if anything - it would look silly. ;) I'd love that! The 1x could even be useful when landing, rapidly reducing speed, etc, since the front view is quite frankly, crap. Wonder why it wasn't done, two lenses might be all that could possibly fit, and 7x/23x was chosen as the best compromise.

Thanks a lot Devrim! And thanks for the Ricardo connection! For those curious, since I didn't want to make the first post look scary - like this one will ;): The lines added to the livery description.lua that looks like this: {"panel ka 50 left", 0, "Ka-50 Panel L_blue", true}, Translates to something like this: {“surface name”, surface type (0 = diffuse), "texture name", search outside current dir}, So it basically tells what texture file to map to each surface and where to look for it - just what we need. However, the tricky thing was, how do you know the name of the surface? You can get plenty of help by looking in the DCS World\Mods\aircrafts\Ka-50\Liveries\Cockpit_Ka-50\english\description.lua file. Which in the same way as we override black cockpit textures with blue, overrides Russian with English in the vanilla game. But you don't get all from that file. To do so, load up the cockpit model file in a hex-editor and search for the texture name. In the screen-shot below I searched for the “ka-50 panel l” texture, and you may find the name of the surface highlighted in green. This can of course be repeated for any texture.

Shameless! :P http://forums.eagle.ru/showthread.php?t=114953 BTW. Devrim, have you heard from Richardo yet?