bn880

You can ignore it sometimes but not when they're locking you for a long time, coming head on within visual range, and you can't confirm that they're friend. It's a concern. The main discussion really for me is: A) Why not un-mix aircraft, and/or what is the timeline when this will happen? B) Why not press ED for IFF that can fail or be turned off, and to make at least balanced aircraft to allow A above. (because I assume A/C mixing per side is because of the limited aircraft that don't overlap Red/Blue) The thing with firing on numpties that insist on locking very clear friendlies is a side point to the two points above, and just a discussion on the rules.

No I do try, but I 100% disagree with you on letting a fighter keep locking in a friendly TA, and having to wait till they fly past your head without firing.. And firing only when they fire at you. So there are new people who do the wrong thing, sometimes they will pay the price. That's just what should happen. I've really only had 1 friendly kill like this, but I would still do the same thing after checking for a buddyspike. (which would come up empty in that case no doubt) If you want to be strict on it, I suggest putting down a basic list of requirements before firing on any aircraft on the briefings. Not generalized, but specific and clear. But it's up to you. Does everyone want to be on TS even?

So you think it's OK for someone to keep locking an A10 and approach it head on, in an air superiority fighter that gives them a clear indication that it's a friendly aircraft? The reason I know I am right is because I see the majority disagree here. (remember majority picked Tump and Brexit.) I am only talking about an extreme case where you can reasonably assume someone is an enemy. At some point what happens is considered an engagement. Continually locking a friendly in an aircraft that gives you IFF info is a clear violation of procedures IRL and should be on your server too. I certainly dont like the mixed A/C on your server, that has been set up for years (just like asbestos was used for years), but it has other qualities which are appealing. Sometimes it does make me (and friends) go to another server if I want to be able to ID a threat though when I see it's shape. You guys are actually clearly ignoring the sensible thing and the voice of more than 1 person, and as a result are not putting any pressure on ED to develop an acceptable set of aircraft either. Perhaps you can explain in the first place why you are mixing aircraft on both sides? And how this outweighs the benefits of no mixing? Carry on then.

Another absurd post. A) no that's not what happens all the time on even 104th. Most target areas don't get CAP. Idealistic. B) I am not talking about contested areas in terms of air Usually. Ground yes. C) So what about the totally absurd mixing of aircraft per side? I gues we are going to ignore this, and focus on A-G aircraft being basically defenseless. D) My main point was actually about retards who lock up same side ground pounders in target areas of their own side for a long time, in jets with IFF interrogators, and then get surprised when they get a missile up their canopy. I am telling you, whenever this happens to me I am going to fire especially if someone is heading straight into me for a long time. No excuse to be doing that in an air superiority fighter to some slow/low fighter bomber. Some people just don't know what they're doing and are about to shoot me down.

More idealistic nonsense here, sorry. It's not RL. Lots of things are missing, planes mixed per side, people are not confirming before firing with any authority. Most missions don't have awacs or anything anyway. Really it all would make sense if it was somehow properly designed and enforced, but it isnt.

Yes but this isn't real life and those F15's and Su/migs fire right away. You can say what you want, but you're telling ground pounders they essentially cant fire back , just die. If we're going to go by RL and confirmations, then everyone including the superiority fighters should wait to ID visually or to get approval from a fictional authority. :p Not everyone is going to follow some idealistic IFF guidelines. This is why I say the missions (not just on 104th) should be balanced, right after ED produces aircraft to level out the playing field. Like something to match Su25t anti radiation, ka50 gunship etc. ;) just a voice of reason. This isn't anything very complex, any reasonable person should be concerned with the mix of aircraft per side and non functioning IFF etc.

So your response to some aircraft having IFF and others not, and mixing aircraft per side, and people locking friendly A-G aircraft in figthers that have IFF needlessly long, is for the aircraft without IFF capability to spend potentially 1 minute not firing? That's your ONLY solution right? Very Idealistic ;) Not gonna happen. (so the suggestion is also for an A10 to get within 2km of an F15 to spot some camoflage markings, which are not even disclosed in the briefing? Meanwhile the F15 can engage the A10 BVR :p quite funny, certain death) The point is, there are all kinds of aircraft out there, and all types of players, if you want to live you have to currently take a few blind shots. The Game designers and the mission designers along with the overall situation force this. Remember this is NOT real life, as is evident from IFF not working, and vehicles of the same type being used on both sides constantly. Intel is rare too. And nobody actually dies of course.

I agree, its when you get constant locks, and the threat keeps coming at you long enough then it's kinda hard in a ground pounder not to do what has to be done. (this happened to me over a Blue TA in an A10, I felt bad, but I did shoot down the fighter as it was an extremely obvious situation to them, or should have been) The point on breaking up aircraft per side is great, it would help tremendously for aircraft without electronic IFF means, just visual. I do still see major limitaitons in aircaft selection though which probably still blocks this.

I have a complaint against a user named "Rhino" who has fired at my friendly A10 twice, once disabling it so I had to land. Second time killed me while I sat on a FRIENDLY taxi way. (he was in Su27 apparently) Meanwhile, the server seemed stable all morning, I think due to fewer players. It looks like with 52 players it's just a matter of time before things time out etc.

Hmm, I will try that thank you. The scary thing is when people drop from the server (that I saw), everyone seems to drop.

I have noticed that the server is disconnecting people every hour or so recently; is this something that is a DCS issue, or server issue or ? I mean, is someone trying to fix the problem at all? I remember a year or more ago the disconnects/crashes were actually less frequent, which is odd. :huh:

Yes that helps, but the new cards still down throttle in DCS when it goes under 30% GPU utilization, it's pretty sad. Wish there was an app out there to dynamically load GPU an extra few % only when needed to prevent going under 30% :) (if not proper vbios etc.)

Right, they don't provide instructions on PCB replacement.

PCB replacement is quite easy and quick. Philips head screw driver, and flat head or small pliers should do. The hardest part is detaching the hot glue without damaging anything (but not THAT hard) It may be wise to glue the red grounding cable back in place with hot glue before reassembly, or some electrical tape. No instructions.

I have a performance loss of about 6-10% in 1.2.15 vs 1.2.14. I just did a controlled test by downgrading DCS then upgrading back up on a test track of a Ka50 taking off. I log sample FPS at different time intervals (by hand) and compare. losing 3-6FPS everywhere.

I can confirm the same problem since the latest beta 1.2.15.37241. It was fine with 1.2.14.36041.618 I believe. 970m... brought to it's knees every time, otherwise running min 30FPS.

Is the server offline today or something? Not in the list for me. (and that is VERY unusual) Edit: server was down, but now back up.

Ok Mr teaser, then can you just say if it runs faster or slower for you than DCS 1.2 on relatively the same settings? :D

Kind of in the same boat. I guess the key will be to avoid upgrading until the Alpha is out to see what's what. (I guess unless something drastic happens the alpha will be within 10% of the final performance)

DCS World 2.0 System specs? Just wondering if ED or anyone can provide any hints as to the system requirements of the upcoming DCS 2.0? For example: GPU: Higher/Lower CPU: Higher/Lower Memory: Higher/Lower Thanks for any replies, though I know it's a long shot before it's out :) Edit: I see my thread was moved, and now I see others wondering the same thing :)

May I ask what DCS version is the server on?

Some good points there, I'd be interested in these changes as well. I suppose some of them are blocked by bugs, but probably not all.

Comparing this to any automotive or industrial equipment (which isn't junk / recalled) is IMO wrong. Automotive ECM's usually last 10 to 30 years in VERY VERY harsh conditions. This controller is simply a poor implementation by use of these problematic Cyprus PSOC's and improper voltage/programming handling. And this under some of the most ideal conditions for electronics on earth (PC USB device). There is no real excuse, but yes compared to most other controllers it still probably is best barring this fault. So to cap off what I am saying: ok the Warthog stick/throttle combo may be a little better than the other controllers on the market in lower price range, but at the price of the warthog today, it could have been made about 30% better = proper micro controller and voltage handling in throttle, metal throttle levers, swappable (screwed in not board soldered) throttle switches, higher quality ministick, metal joint interface knob and pins for stick, etc)

I looked into why the flash may be corrupting on these devices a little, and it must have to do with the Vdd ramp up and stability vs how Thrustmaster set up the Cyprus micro controllers. And my recommendation to everyone to avoid these issues especially once your warranty is gone (which Thrustmaster alluded to when I got my new board as well) is to plug in your throttle/stick once your PC is in windows or powered up properly, and unplug it before shutdown. (don't fiddle with the connector, just get it in there fast and snug) Don't power cycle your PC with the controllers plugged in and especially never do a HARD reset/power down with them plugged in. (best to have a UPS for power interruptions/spikes and to allow for safe shutdown)

Yeah absolutely, I had that exact error when my PCB failed as well. At least you know what you're in for. They'll probably take you through some troubleshooting tips if they treat it like it's on warranty, follow the directions carefully to limit the time it takes to get the process complete. If all else fails just tell them you want to order the PCB and be done with it.