microvax

Ahh, that is what you mean sorry for my reaction then ! :D No, there is no direct way to set the lasercode of a JTAC afaik.

afaik its more or less confirmed, but not a problem connected to buddyspike.

You can change it in the mission editor for each plane. jeeez :D

Did that already, to make sure the "cant join any slot forevar after connect" is not influenced by anything like that. But if ICMP ping packets are already getting lost, DCS cant do much anyways. Prett ymuch consistant if PL is over 20% it disconnects and below 20% it works more or less.

Yup, seems the routes to that network are not properly announced or the link capacities to certain networks are simply completely utilized, which would fit in the good latency but random PL and less PL during non peak time. But pretty much guesswork without knowing the structure of the network.

Each red '?' indicates a lost ping packet. Its all the hops from my machine to your server. Do not mind the reverse DNS resolution. :D So packets pretty much get lost the last few hops to your server, at a moment when its well outside of my ISPs responsability. So I cant even annoy them to death. :D here with latency and pl per hop. So the latency is fine but sometimes stuff gets just dropped which is fairly weird.

Yeee, I love blueflag, but with the routing atm, its pretty much unplayable. :(

Nope, did rune some MTR, before I bother talking to incompetent first level support with my ISP. :lol: Its pretty obvious that the Issue lies beyond the responsibility of my ISP. The PL happens way beyond the internet service has been provided to me. Here is a list by PL/Latency and with the entire names and deviations/max/min. During peak time I get roughly 25% pl now half past midnight saturday its roughly 10-12% and in the morning hours its next to nothing but still above average. From the traceroute/ping combo its pretty obvious where it is happening. x)

Still tons of packet loss. Will open a ticket @my ISP, but since connections to every other server are 100% fine I do not have any hope it will lead to anything.... Never had connection issues in the last 3 rounds.

Well, dunno if it is the greatest, MW1 would be pretty cool tbh. https://www.youtube.com/watch?v=-EQqfxiGgd8 Here a really interesting video from someone who got himself a tornado first gen INS. :D The map projector is really amazing. For 1980 that is such a great feature. Interesting for Razbam as well probably, the guy has reverse engineered some other components of the tornado computer suite.

Same issues here, was fine in the morning hours though. Seems your ISP peer to some other networks is not stronk enough during peak hours. Not much you can do about it though I fear.

Server is randomly dropping connections and is not letting me select a slot for ages on connect. Then it catches up with the server messages and I can choose a slot, but will still drop connection while taxing. Other servers I tested are perfectly fine.

There is no damage implementation yet, but there is one supposed to be there, in the future. :)

omg can we plox have zis ? That would change so much. :D Having an gazelle sitting 15km away from an airport just spotting over a ridgeline would actually become usefull. :D

Yeah, dunno if it was cptsmiley or zeus, but one of them said VNE isnt implemented yet but it will be. Jojo said 750kcas as well, mirage was tested up to 800kcas without problems. I have been runninf from a 27 and 15 with magics only, wasnt able to reach more then 790. Didnt know though that 15 and 27 do not implement it. I mean even Warthunder has its go at it. xD

I would say CMD damaged or out of stores should be the same blinking frequency as the one the RWR uses when damaged. So that is an consistent "system powered but not functional" signal. For other error codes I would go for steady and every few seconds a number of differently timed blinks. Thats how its done with most of the devices I worked with, since counting a number of blinks is way easier in general then tell apart 4hz and 5hz or the time something is lit up. So I would go for same blinking frequency as for the DA if stores are depleted or system is damaged. Off => off Then divide DRM switch state and stores state. DRM blinks are long, store state blinks are short. DRM A => 2 long blinks DRM SA => 1 long blink DRM AU => no blink No chaff => 2 short blinks No flare => 1 short blink Short blink should be really just a flash while the DRM state blinks should be a lot longer. Between the blinking sequences its steady. So in case my explanation wasnt clear some examples: DRP between 1 and 10, DRM SA, full stores => 2 seconds solid, 1 long blink, 2 seconds solid, 1 long blink.... DRP between 1 and 10, DRM SA, no chaff => 2 seconds solid, 1 long blink, 2 short flashes... DRP between 1 and 10, DRM AU, full stores => solid, there is really nothing to be worried :D DRP between 1 and 10, DRM A, no chaff => 2 seconds solid, 2 long blink, 2 short flashes... Think should be clear now, and is, IMHO, way easier to tell apart then a frequency and also tells you both states at a time. :) And I agree that release in programs should be parallel.

negative g during release ? I think that stops release.

AIM54c was designed up to the spec to intercept sea skimming mach 2-3 sea skimming nuclear ASMs. I think it should do fine against a often subsonic fighter sized target. ;D

Takes some getting used to, as does the gun snake, but once you got your brain around it it works pretty well. AP usage is also well possible.

:D in my squadron I am already known for talking about the Viggen all the time literally. :D Funny part ist, that we have a real swede also as a member but I am known for talking more about it then him. ;DD We are already doing training in low level high speed a2g for our future Viggen wing. :)) Anything higher then 60ft is to high. No excuses ! :D Powerlines are to be underflown on final approach to target. :D Kinda curious how much harder it will be to do that without the FBW. Although in general, I expect to be able to achieve more with the Viggen due to its nature of beeing intended for A2G, then with the Mirage. Also the Viggen can carry roughly 20% more fuel while consuming pretty much the same on 100%RPM and the same on stage 2 AB, only on stage 3AB it really eats more fuel then the Mirage, but also has roughly 20kn more thrust, so I guess thats usefuell. :D Cant wait to pwne people with the RB05 btw. :D

Yeah L2P, if you cant use the GBU12, which makes it useless to you by definition, you have an L2P issue. Its even usable in unguided mode and i have employed it multiple times in guided fashion. Yes I agree, that needs a fix, but not breaking something which is right, sts no inflight lasercode change. The fix would be reworked JTAC. should start listening and stop discussing. I mean okay, you are obviously trolling, unfortunately my counter trolling would get me banned for doing political jokes here. ;D So be happy you got spared of them ! :D

yup. Thats why I find LNS policy very enjoyable. It keeps the discussion calm and rational most of the time. Because the people who cant wait arent in there anyway because NO FANCY SCREENSHOT. Meanwhile devs talk in the appropriate threads more then screenshots could. :)

If it makes it useless for you you have a L2P issue. *scnr* Yes you can, if its not part of your contract. Well if you consider it a problem, then write a bug report and not a lousy thread in the general section. :P Oh damn, I forgot, reporting realistic behaviour as a bug is kinda pointless in a simulator. It seems you are out of luck ! I do not even get as a german what you meant with that. But if you come from eastern germany this all makes a little bit more sense. ;D ;P /jk

This... !

Hmm, I mean the AJ37 as one of its main purposes had the "sink an possible invasion fleet" task. If you combine the Radar the aj37 has onboard with a directional RWR which may even be optimised for detection of radar signatures used by russian ship borne radars, you have a pretty damn good detection system. Against ships, which are the main threat here. Iirc prototypes had also hydraulic canard flap actuators which would have made an inflight usage possible. But in the end they are linked mechanically to the gear deployment procedure somehow. Since it was not required in a more fancy way for its task. Main concerns were keep it simple, so its possible to maintenance things in the field and dont overengineer it, leading to big cost. Iirc they expected to loose the enfire F1 fleet within a few weeks. So a potentially more complex, spare part dependant on third countries RWR which didnt improve the survivability against ships much would not have made much sense I guess. Also swedish fighters had datalink pretty early on which kinda is better then a RWR. I mean I dunno if any of that was an argument for or against it, but swedish aircraft Industry at that time really doesnt look like they were taking bad decisions. :D Only thing I really do not get, why they opted for the subsonic AGM65 and not the RB05T.