69iAFMike

Looks like they already sent the truck to remove this structure.

Harissa Cathedral, if seen from behind- floats in the air. The terrain is just too flat. Not that it matters to jets, but the chopper pilots will be disappointed :) Here is a Google Street View link for a similar angle: https://www.google.com/maps/@33.980229,35.6529234,3a,75y,301.9h,84.79t/data=!3m7!1e1!3m5!1sAF1QipM5BJACttMcZZoTBlEYxq4MuWtBN2B709fvtjZf!2e10!3e11!7i5120!8i2560

Sounds great :thumbup:

There are also some missing landmarks (and potential targets?) in Israel such as large power stations (where are the two giant cooling towers in Haifa?). The map's detailed area stops just north of Israel's central cities. But the identifiable area is very large. From the southern tip of Crimea, almost reaching Riyadh. It also spans from the eastern end of Iraq all the way to Greece. The resolution is very low but major features, shorelines, cities and rivers are identifiable. I really hope the area to the south, from Egypt to Iraq, can be improved, at least concerning major historical events, maybe with community mods. Attached is Baghdad, for example. Just let us add some Osirak buildings please :(

After seeing Normandy hammer my 1070 at 99% with the 8700K staying relatively calm, I can see a Titan V in my future :)

11 years of progress. How many more till we get DCS: GTA?

Line 35, just multiplied it by 5.

I love my f/0.1 lens!:) Now the DCS world looks really tiny. Look at that cute little Mustang and the cute little cars going about their day. Adorable. This is the DOF.fx getBlurFactor function, multiplied by 5. I wonder if movie makers would like it for some shots.

You guys have no idea what a good lens flare is all about.

No doubt DCS Leica will cost 100$ at least, per camera. But yeah, the shape is easy to change. It's just the alpha channel of lensGhost.dds

I don't think these settings do anything. Apart from Adaptive, which allows to antialias alpha (which destroys the framerate on my card), the various modes and filters don't do anything at all. The ingame AA setting works it's own magic regardless of overriding or enhancing it in CCC.

I think you are fine

Well, yeah, if the new settings "force" the rendering of at least a single pixel at low resolution, then it will appear much larger when upscaled. What if the low resolution one or two pixel sized planes get their brightness scaled (depending on resolution) to appear somewhat equivalent to larger resolution renderings? Could that be an acceptable solution?

Well, something is wrong! My 280X Dual-X runs the thing at 1920X1080 almost all settings maxed/ultra, without dropping under 50FPS. No lens effects, X2 MSAA. I did have to disable the Adaptive Multisampling option in CCC, it killed the framerate, and jaggy trees never bothered me anyway, can't see no trees from an F-15 :) Try running with all settings at the lowest possible setting. At 1080 you should easily hit 120FPS. Then change them one by one and check with a quick flight, you'll see where the problem is. If you can't get 120 with everything on minimum then I guess it's not a DCS issue.

Careful man, this screenshot just gave me a small heart attack!

Thanks! It's really confusing now. Aren't there like three ways now to handle locations for models and textures?

I feel stupid, but I can't even find the texture for what we have now, or even the model to view through the modelviewer.exe. Did anyone locate these?

I Love ED/Wags/SiTh

Accela Mk4, this is the main reason for using the point tracker with Opentrack :) The default settings are way too laggy. Try rotation/translation values at about 40, order 2 is 1.5, order 3 is 2, deadband zero and exponent 1.8. You can change the values to fit your needs (changing a value by even 0.5 will a noticeable effect), either more responsive and "noisy" or slightly lower response time and much smoother. Here's a more accurate explanation: https://github.com/opentrack/opentrack/wiki/Accela-filter I must say, version 2.2a2 is weird for me. I can't get it to track smoothly with as fast a response time as I get with the older version 2.0b3. I used to be able to move the virtual head in a nice circle, rather quickly, but now it tries to stick to moving in straight lines. Back to 2.0b3 for me.

Do the "raw translation/rotation" values under the video show anything? Did you define the point model dimensions in the Point Tracker settings? Make sure you select the "clip" tab and not any other one- it actually sets the point model selection.

Nice work :) Instead of facetracknoir, consider using Opentrack. It has better (newer) filters. After setting some stuff up, you get a much more responsive and accurate tracker. https://github.com/opentrack/opentrack/blob/master/README.md

If you want to go really deep, look at that: https://code.google.com/p/adapt-ffb-joy/ As I understand it, it presents itself to the PC as a FFB stick, but instead of driving motors, it translates to MIDI and lets the original Force Feedback Pro stick do the work like normal. So controlling our own motors would require modifications.

Thanks, I'm using it now :) I did hit 96% at the detent before (no idea why), but then it only got to 93% every flight. So the new curve helps.

Just a cable? WTH is he talking about? Get your money back and buy a proper warthog at the real price of 450~500$, yeah shipping could be pricey but I highly doubt it would get near 700$. Amazon has one for 460$ and free shipping. "Kids these days" apparently run computer sales businesses.

They'll probably offer you a replacement part. Heck they sent people whole PCBs even.