bn880
-
Posts
253 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by bn880
-
-
This is a great suggestion IMO, and would avoid the god mode for some fighters. Making it much more interesting and detailed. Also it's interesting to quote AI, as it seems for the most part it can be simulated to act like a human in this regard. (you can add mission options for their IFF knowledge in general, some theaters they'd just know, some they would need to confirm, add appropriate delays, done.)
-
Guys, you can`t stop someone to lock other aircraft. Why discussion about that? Of course it annoys but... ignore.
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.
-
1
-
-
;3072777']
My problem with what BN is saying is his apparent refusal to even bother trying to IFF and instead just saying these suggestions are 'idealistic'.
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?
-
;3072516']There is nothing "totally absurd" about mixing aircraft on both sides' date=' our server has been set up like this for [b']years [/b]and most people who fly on the server do not have a problem with it, if you don't like the set up go and fly somewhere else, we don't force you to fly in our server.
If I can IFF in a HELICOPTER you can do it in an A-10, trying to justify teamkilling people just because aircraft are on both sides is stupid. There is more to Situational Awareness than just reading your RWR and firing on the first aircraft you see because it 'might' be a bandit. I have never once teamkilled anyone in a Gazelle and I have over 50 air to air kills in it!
There is also nothing "idealistic" about holding fire until you have IFF this is what you should be doing in all cases, you only fire on another aircraft if you are 100% sure its an enemy, not doing so will get you banned. A-10C or not, teamkillers get removed from our server, you have been warned!
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.
-
1
-
-
I don't understand what you mean by non functioning iff. Planes like tha A-10 etc. don't have interogators they only have transponders which react to friendly fighters and SAMs that interogate them. An A-10, Ka50 can't iff and rely on intel, good SA and mk1 eyeball.
If you're entering a contested zone then you should be going with fighter cover on comms, otherwise you're asking for trouble. If this is what you want then you need to learn to notch and defend to force a merge because if your only tactic is blind firing on anything you see then you need to get back to the safety net and stop trying to play with fire, aswell as potentially ruining others enjoyment.
When i'm unable to iff, firing on something i'm not sure of is ridiculous, I will always try and visually id, gather communication or pick up the situation on how he is behaving. This serves me and most everyone else well so why try and be ahead of the curve just for your own gain. It is all part of the learning curve, don't be that guy that doesn't care for anyone else because he only wants to hit the instawin button.
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.
-
"to spend potentially 1 minute not firing?", yes if needed hold fire until you are bingo, if you are not sure. Its not idealistic, its simply a base for having a nice time together online. Everyone of us has so and so much time he can and want to dedicate to DCS and its completely up to him how he spends that.
I think its simply unacceptable though to shoot a potentially hostile, potentially friendly target, effectively risking ruining the fun someone else has and effectively reducing the time he has fun, just to potentially save one owns, despite one has choosen the obviously high stakes operation to get into situation having to decide on this at all.
So its simply not idealistic, only to shoot if one is sure of ones target, its a basic requirement for complying with "Fair Play is MANDATORY AT ALL TIMES".
Especially in the scenario you are depicting, hostile f15 vs a10. If the F15 isnt quite below average on skill, the a10 will be dead before anything happens. If the F15 is somehow missing the a10, its up to the a10 to use that only advantage he has, not beeing detected, to make something of it.
And I totally get that its satisfying to down a high end a2a platform with some kind of plane, less capable in that arena. But that doesnt justify trigger happy behaviour.
So hell yes, if the a10 isnt sure of the potential hostiles hostility, better die not knowing, taking responsibility for your own decision to go there, then downing someone else, who is indeed allied.
Thats the only logical solution I see to this "problem".
No, simply stay safe if you "want to live".
Nobody forces you to shoot undeclared targets. If you do, you are basically violating "Fair Play is MANDATORY AT ALL TIMES". At best ones own bad decision making, greed and disrespect for other players forces one to take blind shots.
I do not exactly get how IFF not working as it does non simulated, for that timeframe of planes we have, is an argument against visual ID. If IFF would be as reliable as IRL we would basically not rely on IFF for BVR. Its a good indication, but visual ID beeing base for ROE even in desert storm might indicate how sure of an indication. :)
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.
-
This actually mirrors real-life ROE throughout history much more closely.
There's been remarkably little BVR combat in the last 50 years as compared to WVR.
--gos
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.
-
Do not shoot before AWACS or visual ID by cammo or type identifies a contact as hostile if you do not have IFF at hand.
If one shoots by factors like long STT or other rather speculative things, one is simply trading potentially killing a friendly for potentially solving a dangerous situation for ones own flight, for which only one self is responsible in the first place.
And that is, to put it mildly, not nice. :P
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 understand getting locked up time to time from friendlies. My only complaint is the continuous lock. I can't complain too much as if I just got on TS, I could then hit up the person that might be locking me. I flying time is fairly short so I forgo TS a lot :( so in the end, guess I can't complain.
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.
-
It is highly recommended for users to have an autoexec.cfg placed in their Config folder in Saved Games to avoid such disconnects, this file contains parameters that raise the up/downstream of the clients connection thus highly reducing the chance of a disconnect or timeout.
You can grab the file here
http://www.mediafire.com/file/37bejnkzp2sll1g/autoexec.cfg
just simply place this file into your C:\Users\<name>\Saved Games\DCS\Config folder and you will see the difference.
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:
-
I would certainly switch energy management mode from adaptive to max performance - You don't want Your card to down- and up-throttle in the middle of a mission. The rest is subjective fps-vs-eyecandy matter, probably not very different from ATI card settings.
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.
-
In this regard, and for those who already went through this procedure, I would like to ask some questions if I may :
- Is the replacement procedure of the PCB difficult ?
- Are you provided with a replacement procedure or DIY one ?
Thanks
Laurius
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.
-
Me thinks you will change your mind when you get to play around with it yourself. :thumbup: :D
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
-
Has ED considered a "view only" tech demo tool for World 2 engine? Suffice to say the long release as lead to great expectations. My concern is that many of us are headed towards disappointment in terms of how well the engine will run on our hardware. There are many threads about people preparing new PCs specifically for DCS, but we are really all left throwing darts in the dark.
Similar to how Microsoft releases hardware experience tools prior to a new major OS releases, could a demo be released which would allow no control, and simply run a short 30 second "flight" with an FPS indicator to give us an idea of performance?
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?
-
How does it look on the CA front? Any chances of trying that again in 104th missions? Would really like to see the possibility for frustrated CAS to drive SAM's toward their A2G area and protect themselves. :D
Also could we get the different FARP's where possible on the Briefing screenshot? And a little description or grid on the briefing, was earlier in the Shark, shot out ABRIS and the FARP wouldn't answer on radio... Was a nightmare! :D
edit: also what about maybe a jtac that spawns if >80-90% of units got destroyed? Sometimes we search for 3 1/2 hours... :(
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)
104th Phoenix Dedicated Server Info
in Multiplayer
Posted
Riiight, ok, that's not exactly what I said even in the quote, but even if it was you're wrong. Also do you always target just one liners from people's posts? :music_whistling: