Insanatrix

Was gonna report it early but forgot what part it did it in so would have been useless. Yes it was funny as I was going off the voice during the whole thing.

I got it and enjoy flying over all of the terrains. I play multiplayer but definitely fly alone learning the systems and practicing. It's always more fun if I have new and interesting areas to fly in. I think the problem with NTTR is the that it's mostly relegated to a training area and not a combat oriented area. I hope the Persian map is utilized more since it is definitely a believable and viable area for low and medium intensity conflicts.

Problem with parallel processing is that everything needs to be written from the ground up to do it. In most cases that would mean an entirely new engine written from scratch. Almost every developer uses an iteration of an already pre-existing engine to run their games on. Try splitting off individual tasks and all of a sudden you have all kinds of crazy things happening because other systems within the engine weren't written with those tasks being run in parallel in mind. Like that old joke, run your compiler and get 1 error, go and fix that error and recompile and you have 10,000 errors now. The resources needed to write a new engine, the time needed to do it etc... Think of how long it's taken DCS to get where it is now and try rewriting everything all over again. Doesn't sound fun, cheap or efficient.

You'll probably never see issue's like that fixed. I'm no expert on it but the only way I've known that a developer has gotten around that was using asynchronous rendering meaning the rendering doesn't run parallel to the simulation but rather as a separate entity. I think that's what they did in DayZ for instance which is why there was a large performance increase in one of the experimental builds but don't quote me on it as I haven't loaded or installed that game in 2 years. Using it as an example though because as a whole ArmA and the RV engine suffers from the same issue's, a massive workload for the CPU and not a whole lot for the GPU. It has it's issues, I'm no programmer by any means, but you could have switches that don't switch because the simulation is behind the rendering, Units that appear to be looking one way when the simulation say's they're looking somewhere else because they are behind the renderer etc... Loads of weird issue's that wouldn't make asynchronous rendering feasible for a game or simulation as heavy as DCS. Which is why usually simulation is tied to rendering in complex games. I use Simulation as a generalization of the workload for the CPU as generally it's the biggest task. Could be scripts, could be AI, could be ballistics. Better multithreading and parallel processing would help but I'm sure I read where ED felt that Pursuing better multithreading wouldn't be feasible or worth the time. Not to say they might not change their minds in the future.

Quick search say's it's DX10, not DX11. I think DXDiag will show the version of DirectX installed, not what the card supports but could be mistaken.

Happened to me as well.

I have crossfired 290's. Any settings I've tried I get massive stuttering or worse performance than just 1 card.

I haven't been able to get crossfire working in windows 10 with 2x r9 290's. Tried most of the stuff suggested in the thread and nothing has gotten the second card to be used. I'm sure there will eventually be a profile since dual gpu is a big point of interest for DCS:W 2.0 .

You should just have to reactivate. Adding or activating the GPU on your CPU constitutes a hardware change and the DRM requires you to reactivate. Maybe the Mig-21 uses an older version of Starforce or whatever the DRM is they use now? Really you should just have to reactivate it and you'll be fine. If you've run out of activations on your key then contact support and they should be able to give you more AFAIK.

His specs are in his sig.

limiting frame rate isn't the same as V-Sync otherwise they would just do it that way in the first place. It does help with screen tearing but you still don't run in sync with your monitors refresh rate so there is still some tearing. Triple Buffering is a must for using V-Sync. I hope they have freesync/gsync support in DCSW2.

I've had my Seiki 4K for awhile now and even at 33hz due to the HDMI limits, 4K is amazing if you can drive it.

Plugged my X-55 into a powered USB 2.0 hub and all the hats worked perfectly no problems with them registering. I really think a powered USB hub is almost mandatory for this thing as I didn't even get ghosting issue's, simply those 2 throttle hats just would not work and all of a sudden work fine with a powered hub. Overall I like the stick for the price, I think it's just got it's quirks.

Last night after I re-installed the drivers it was still having a problem, now the top hat on the side is working completely fine, only the bottom hat won't register in the up direction now... I should also say the button movement feels fine, doesn't feel like there's any kind of slop or looseness, I can also feel it "clicking" in the up direction just get no response in the HUD software. I think I might try some USB 2.0 ports since I've got it plugged into my USB 3.0 ports right now.

I'm thinking about it. They may not have installed right. *edit* Tried re-installing and still the same issue.

They don't even register in the HUD software as me pressing them. Like if I set them to actual bindings instead of as hats, when I press them up they don't light up or anything.

I recently got an X-55 and been trying to use the two hats on the throttle as simple 4 way hats and they all register except for the up direction or button, so effectively they're 3 way hats. I've tried googling and haven't seen anyone else with this issue.

Same, I just got one as well and it works fine here. I think throttle should be Axis X and Y for split throttle not Z. Z is the top rotary and is usually what it defaults to.

You're not, I feel the same way for the same reasons mostly.

I don't think he's sensitive though I can understand his sentiment as IRQ conflicts are pretty much nonexistent these days and seeing suggestions in that respect makes me cringe a little as well. He's right about the power requirements as most USB ports are limited to 500ma, depending on the chip, after enumeration and limited to 100ma before enumeration. From what I understand a buddy of mine has an X-55 and managed to get rid of most all the problems by plugging it into a powered USB hub and or modding the USB drivers to allow more power to the devices. He just found the powered hub option to be easier. It's possible that when you re-installed your OS you got different USB drivers that don't limit the power output to 100ma before enumeration or solved some negotiation issue. Hence why re-installing the OS "fixed" your problem. Also most onboard USB "hubs" use the same power source so if you have all USB ports in use, it's probable that it's not going to be able to support the load of all the devices. Also from what I understand USB 3.0 ports are able to support more power through each individual port so if you have them you could try using those instead and see if it fixes the issues for anyone else.

Noticed a boost in Assetto Corsa and Rfactor 2. Have yet to try any ED sims, still waiting for EDGE to come out before I get back in to it.

Then what's the point of the program since pretty much every product is launched through a beta with a discount?

As title reads, not sure if this is because it's already discounted but can't seem to use my bonus amount earned on purchasing the K4. It says you can take off 30% of the retail price so I can understand if they only let us use like 10% of the retail price in bonus cash. It's kind of making the loyalty bonus moot if we can't use it on preorders simply because they are already discounted unless you want to wait and pay at a higher price point.

Visual spotting of objects This is something I have noticed more with the WWII planes and having no sensors etc... but it's really damned hard to spot objects, even if it's moving against a contrasting background. I've seen this said a lot but as an example I can look up in the sky and see a plane probably cruising at 30,000 feet and I can easily make out it's shape and tell what it is, maybe not the exact type of plane per se but that it's a plane and I can track it and see it. Like I've said, this is something I've noticed much more since flying the WWII birds but scaling feels very off based on distance in DCS. A plane at 1 mile feels like it's 3-4 miles out and so forth in terms of scale. How does anyone else feel about this? Do you feel that object scaling at distance feels correct?

Just preordered as well. Don't know why but I always loved the German WWII planes, 109-F4 though was my favorite.