firmek

I had exactly the same issue with my old GTX 660Ti which was factory overclocked (to 1100 Mhz). The way to resolve the problem was lowering the core clock by few Mhz. IRC in that specific case 50 Mhz did the job, resulting in 1050 Mhz which was still more than stock 980. Which 1070 card do you have? If it's factory overclocked try to lover the clock. Use the free MSI Afterburner. See if it helps. If yes, create a profile, make it as applied on startup and enjoy your new GPU.

Kind request. It seems that the missions are created in a way that they override the user view settings (SnapView.lua, Server.lua). Would be great to have it fixed. The procedure is not complex: from http://en.wiki.eagle.ru/wiki/Snap_views

Get i5 and save the monay for better GPU.

You must have taken a hit into engine or wherever the governor is located. The problem is not so much the systems damage modeling but the visual indication of the damage which is not exactly reassembling places where the bullets have hit. Not even mentioning that the holes don't follow the bullets patter but rather look like a spatial damage from fragmentation warhead.

Few months ago I've upgraded my GPU from 660Ti, kept the i5-3750k. DCS is installed on HDD. 16GB RAM. I didn't had any major issues running DCS in medium/high settings with that configuration. IMO first increase your RAM then consider a new GPU.

A-10C is a signature module of DCS, can't go wrong with it. Especially that apart of the aircraft itself I think that more important is the content for it, which for A-10C there is plenty of. If you're interested in WW2 why not to go with Spit also. It's in early access and some things are expected to be tuned and added but with Normandy across the corner we can only expect that WW2 will become much more interesting. At the moment unfortunately it’s mostly MP with dogfight and air-quake like servers. Sabre itself is a great module which on the other hand suffers quite a lot from lack of content. On the other hand there is a fantastic Museum Relic campaign for Sabre and MiG-15.

From user stand point, its a bug. Technically, rendering the sight in front of the reflector glass was probably what was possible to achieve an infinite focus perception. Another way could be probably rendering it on the surface of the glass but playing with it's size while the pilot gets the head closer. Then the resolution would be becoming an issue as getting close would make the sight look bulky. It's not a biggie I think, impacts a bit the immersion but wouldn't I guess change the practical use.

Happened when overspending in a dive. But then again, it was from a high altitude and while intentionally testing the limits.

Trying to be realistic, I wouldn't expect a release but rather a news about a pre-purchase and release day. But, the hope (and the hype train) dies last :) Merry Christmass to Everyone :) Edit: got sniped :). Great sales and Viggen is coming :thumbup:

Yes, the website is always updated some time after the newsletter is sent out. Usually I guess more or less 15:00 - 17:00 CET.

I've done it for M2000-C (as also for almost every other module) using the same approach as n26. The JSGME may not be so bad idea with M2000-C as it becomes stable but on the other hand I wouldn't suggest it for a number of reasons: 1. DCS has a really good update system. After running an update it takes just a moment to copy-paste from the latest "__backupXYZ" folder. Can't get easier than that. 2. From time to time it's good to compare the files in order to check if the update didn't bring changes to overwritten file. In such case own customizations should be re-added manually. For that reason knowing what to do becomes handy. With JSGME there may be a false impression that running it after an update makes everything right while in reality the fixes/updates are potentially overwritten with old code.

Yea, I was too fast and did a small mistake with my calculation. To serve the 109 or 190 the base should be set to ~35 not 30 feet. By the way, what is the minimum setting for the base 35 or 30? It's hard to judge by looking on the base disk scale in cokpit. Regardles of that I think the results are more or less the same which is with setting of 300 yards and 35 feets the sight shows the target at ~500 yards. I have an idea how to do some more testing. I'll try to get back with the results during the evening.

Run the process from attached wiki link. It'll create the file in saved games DCS folder.

Thx for sharing Sokol. The gun convergence of Spit in DCS is set ATM to 300 yards. For Bf 109 or Fw 190 according to the book this should be 1/3 of the sight circle diameter. Now, setting the sight distance for 300 yards and base for 30 feet at the moment results in more or less 1/5 or 1/6 of the diameter. Am I missing some understanding or is there some misalignment between the book and how the Spit sight is working in DCS?

Great ides from SUNTSAGA. There is however other way to achieve the same - use the custom snap views: http://en.wiki.eagle.ru/wiki/Snap_views Or edit the Saved Games\DCS.openbeta\Config\View\SnapViews.lua - if you don't have it, create any snap view using method described in wiki link. Next, open the file, find section for Spitfire SnapViews["SpitfireLFMkIX"] and change x_trans and y_trans values at index 13: [13] = {--default view viewAngle = //don't copy this line, it can be used to set FOV (default zoom) hAngle = 0.000000, vAngle = 0.000000, [b] x_trans = 0.075, [/b][b] y_trans = 0.030,[/b] z_trans = 0.000000, rollAngle = 0.000000, }, This way there will be no issues with IC as also no need to restore changes after the update as the original module is untouched. I'm not posting the SnapViews.lua here as this file stores personal preferences and using it would potentially overwrite them.

Normandy, where did you find that? Now the hype train is going to sky rocket.

:doh: Then it's pretty much confirmed. Kind of an "unintentional" leak - on official ED YT channel :smilewink:

Or the "big" news is Normandy or could be also any big news themself :D Cobra has mentioned that they want to give Spit some space. I guess it might be pre-purchase announced.

I might be taking too far going assumption but looking on the diagram (page 81) it seems that the wooble pump (15) is bypassing the main cut-off valve in a way that it is taking the fuel before it and feeding the fuel line after it. EDIT: I think it's actually described this way in manual:

I guess the rear tank is not modeled atm. The manual also mentions that due to severe stability issues the rear tank was only installed on some of the versions (clipped wing?) and filled only when an external fuel tank was attached. Probably it'll come in the future but still we shouldn't expect anything more than a slider. The standard procedure would be to fuel the front tanks first and rear one afterwards. With slider this would be that if rear tanks are installed, everything above certain % of the fuel would go into rear tanks. In either case the bottom tanks were fed from the top ones.

Video is set to private.

There is a similar topic. It looks like it works as it supposed to: https://forums.eagle.ru/showthread.php?t=179467

If I got it correctly from the fuel system diagram, both priming and wobble pumps are connected before the cut-off valve. In other words it looks like it should be possible to prime the engine and run it all the time by manually creating fuel pressure with wobble pump while the main cut off valve is set to off.

Not a big issue. The main functionality works. Great tool by the way. Thank you and wish you a Merry Christmas

I don't know what is the history. Long story short, the files are just a configuration of what DCS is doing, with a difference that for every single module in DCS there is a different setup of shoulder size, eye point (neck length), max/min zoom as also few other things. The benefit of using Server.lua stored in user files is that you're getting the same configuration of mentioned things for every single module. Additionally with proper synchronization of FOV and max zoom values between Server.lua and SnapViews.lua it's possible to get rid of annoying zoom-out effect when entering the cockpit. As for SnapViews.lua I'm editing it to make sure that every single module has the same default field of view (zoom). This file is really optional, actually it may be better to edit your own rather than using attached one - the instruction is in one of the posts somewhere above.