kobeshow

Wow Winchester, your way of arguing sure as hell will get you nowhere, enough with the extremes already. Maybe you have this type of elitism on Bluefor, but if someone is on the proper coms channels, be it TS or SR, I have never seen them being ignored or just cast away, the problem with Blueflag right now is that it became the dynamic 104th, markers further incentivise people to ignore each other since they can just "look at the map". I agree with BadHabit that they are very useful and I don't care if they are on or off, but you need to admit that if people are given a crutch they will use it, and if someone is not on coms the markers sure as hell won't make them talk to their teammates. In conclusion, the markers themselves are not the problem, but they are not the solution either.

The following is not meant as an argument for or against markers, keep them or take them away I don't care. I am not really convinced by this argument, Squad works because it has in-game communications that are easy to understand and setup, and people use them to actually communicate. I have had bad expiriences with Squad aswell, so it depends on the other players alot, just like it does here. When I first joined this event in round 5 it was a bunch of randoms on Red meeting in teamspeak and actually trying to coordinate, we actually split up in different channels back then when SimpleRadio wasn't available. That discipline quickly deteriorated though, and when SimpleRadio became available my biggest fear was that it would further split up the few people that are on coms, and look where we are now: no one on teamspeak, no one on SimpleRadio. I see that Blue handled implementation of SimpleRadio a bit better, probably thanks to RvE aggressively recruiting a lot of players from Blueflag, which I think is great, it helps promote teamwork and communication. Coms are key, and people need to be willing to communicate, that means they need to be able to talk, but more importantly they need to be able to listen. "But what about new players that want to have fun?" I agree, they should not be excluded, but unless you are willing to read the SOP and be on coms with your team you should not be allowed on the server, it doesn't even take 20 minutes to do that. We have a lot of "just join and do your thing"-servers already. For some reason Blueflag has become a place where anyone can join at any time, without proir knowledge of anything, and waste a few airframes to get their airquake in.

I don't have expirience with the markers yet, specifically how they are used on the server, but the fact that this is even an argument shows the state of blueflag right now.

Don't worry, the people don't get you either.

Nice "testing" Micro, under those circumstances even fighters will disappear.

To avoid confusion: you watch your track in DCS (cross fingers that it is not broken, although it probably is), then Tacview will record everything from the track and you'll have a good .acmi

TacView

Kneeboard Builder is great, just not for multiplayer, it creates its own .lua which does not pass the integrity check.

Sounds fantastic, great work !

I'd say remove stable, so people don't get confused by the word.

small detail, but if you don't activate the battery before spooling up the engines, the radios won't work on groundpower alone.

All in all the least stable round I have been a part of so far, sadly, but BS team are working on it so I have hopes for the future, especially with a new sponsor in the mix (; I have a question about the numbers above, does unassigned players mean they entered the server without picking a side, hence not able to spawn in a plane, or does it mean they entered the server without registering in the forum? The player numbers further indicate a rather casual approach to BlueFlag for most people, and that was very evident in coms most of the time. Great Job and a big THANK YOU to all of the Buddyspike team :thumbup:

I have done basically the same test with a buddy of mine and we just chalked it up to "DCS things". In our tests we noticed similar missile behaviour, there was desynch in terms of missile flight path, but wether it is a hit or a miss is pretty much consistent. I have attached the .acmi tracks if anyone is interested. Missile Tests.zip

Nah it still is the same as 1.5 apparently. You get everything the way you should, except that you probably still can't enter decimals for the distance of the BAD. IP does not update correctly and you don't fly level and on the right course, so your steering cue --0-- is pretty much pointing where I would expect it too, and you can release bombs, so that part is working. What we still have a problem with is the precision, it should never be laser precisioin, but right now it is impossible to get bombs even remotely close. Well I hoped those fixes meant something, are you sure you are on the latest update 2.0.3.57442 Update 3?

It was the latest 2.0 update on Oct. 7th. https://forums.eagle.ru/showpost.php?p=2920337&postcount=18

So again, for people to have an overview, this is the latest changelog for 2.0 M-2000C added separate mode for M-2000c ground ranging TAS (radar ranging) upgrade. AG gunsight upgrade. HSI VAD enabled. WP display on VTB bug fix. OBL not displaying bug fix. TAS for OBL/IP bug fix. RWR Threat library updated RWR Sounds updated RWR Launch detection mode enabled Radar NCTR library included Radar NCTR enabled Decoy release program enabled. Built-in Jammer upgraded. New keyboard bindings. INS N.DEG light bug fixed Bullseye coordinates fixed INS "Always Aligned" not working bug fixed Radar CCM bug fixed DRM button added to Module Manager if you are on 1.5: radar/TAS/sights/IP position updates, are all faulty. I can not say anything about the effect of the 2.0 patch, I don't have it installed.

For people complaining about mirages on red being french and such, this is due to things that are going on in the mission editor. Currently only the french mirages can select all skins (as in they need to belong to the country france), so the red "iranian" mirages only have one selectable skin...which is a french one ): and switching coalition manually for a country after you have creatted a mission is a bitch, so unless someone is expirienced with the editor, just hold your horses, it is sadly very limited in some respects.

BAD is simply an offset value that belongs to a waypoint, any waypiont can have one offset. If you have set up the BAD waypoint you have two options: You want your HSI needle pointing to the BAD instead of the IP, to get direct navigation, in that case just DEST "waypoint number" and then press BAD on the PCN. Use the BAD as your INS bombing target, in that case you need to DEST "waypoint number" (maybe PREP aswell not sure), this is not the offset, just your regular waypoint. Now prepare your bombs, as soon as you have them selected and master arm is on you should see your PCA mode row showing PI (point initial). This will tell the system that you want to use your currently selected waypoint as the reference point for a bombing run onto the corresponding BAD (offset), if you now fly over your waypoint it will automatically switch your navigation indications to the BAD point, and will assume that this is where you want to drop the bombs, so it will give you a bomb realease indicator when you approach it.

Ah I see ! Sorry I confused you with the OP (;

Just so there is no misunderstanding, the VTB screen is suosed to be black, if you have a TAS indication in the top right corner everything is fine (like in your screenshot, TAS is showing). If the TAS indication is blinking your radar is not emitting, but you already get ranging info so I suppose it is working.

Once you have picked a side on the server by typting red/blue in "all chat", only the admins can change your coalition, and you would need to request that either here or in the existing thread on buddyspike.net

I thought they had fixed that in the last 2.0 patch, apparently not, it is the same as 1.5 and is known to be an error, so we need to continue waiting for a fix.

Yes you may have missed that they fixed the need to display the messages, and the messages were removed at one point in round 9, but came back for some reason.

I don't think kill messages for air kills would be better, remove them all! Remove everything from the chat window that gives any form of intel, I can't be the only one that feels that way.

It has been a while, I'll check and see if it works with engine running, but as I recall it did not. EDIT:Well, I tested it with ground crew and enignes running give enough power to the radio.