All Activity

In the air. A-10 pilots would sometimes use other A-10's, per an article on the internet.... somewhere. While ground boresighting kinda works in DCS, IRL Mavericks drift during takeoff and when pulling G's. IRL, I'm sure pilots are briefed on suitable places to boresight (a town, for example). In DCS, this gets tricky since Mavericks may not "grab onto" a static map object, so that would effectively break the mission. In the ME, it would be best to build a little area near a town to boresight on the way to the AO. -Ryan

Thanks! Yeah, based on real story.. and as for the first technical, this is now internally fixed. Indeed - not intended, things changed with new splash damage for the Mk-80s

Razbam is Veao 2.0, the only difference is that they are administering it to us a little at a time, to make the pill less bitter. Razbam modules are lost, they are no longer for sale, they will never be updated. Razbam has no intention of returning to DCS, just as it never had any intention of returning to MSFS. Certainly, this whole story does not make me want to purchase new modules, I myself am not buying any; however no software lasts forever, we have to come to terms with it. This time it's Razbam's turn. Sooner or later we will have to go back to enjoying DCS for what it is, and let go of the past. Chi ha avuto ha avuto ha avuto, chi ha dato ha dato ha dato.

Which means they are dead. New customers are also ED customers, so if they cannot buy them it means these modules are not part of DCS World anymore. They are just on life support

I think he means if HB were handed the MudHen and told to get it working again it'd delay the implementation of the player-drivern Intruder.

Thanks for the feedback. And here I was proud this was the best structured briefing in any of my camapaigns, with clear references to each briefing slide, with the most important things available on hand in the kneeboard... I'll keep it in mind though for future projects, this is a good idea that won't take long to implement but will help.

Why would the imminent release of the AI A6E Intruder by heatblur be effected by any Razbam shenanigans?

'Making new versions' is a very tall hurdle to cover. Who is going to do it? The ED teams working on ED Projects? The Third Party teams working on their projects? Frankly, if RB going belly up were to delay my A-6 Intruder, I'd be ready to throw hands. The ideal solutions are either store credits or getting RB back in, in some form. Beyond that is dicey.

I am not experiencing any issue with F16C JDAM accuracy in 2.9.18.12722. For best accuracy, use targeting pod to refine actual target position and use laser ranging, adjust the impact angle to near vertical, release near the center of the launch window.

Look like 2 quotes were merged, but just one response, apologies, not directed at your comments, but Alejandros

Please attach a short DCS track.

I mean... there is an option... one that's been brought up several times, and now has a whole thread in the wishlist section: Make new versions, and if someone hasn't gotten a refund, they get the new toy for free or significantly reduced cost

I cannot reproduce the issue for now, even with fog. Can you please post a track demonstrating the issue?

ED running into this thread "Lemme scootch past ya der."

No, it is not. Factually the Luftwaffe Depot maintenance facilities overhauled and recycled damaged aircraft all the time. That is exactly where White 1 came from as it started out an FW-190F8 as delivered from the factory and was converted to an FW-190A8 by the receiving yard/Depot Maintenance in Norway. When magic happens and a BMW801S motor appears upon an FW-190A8 it now to called an FW-190A9 and NOT an FW-190A8/R4.

ok, will wait for the fixed version, maybe there will be also the updated Mission 10...

I tested the same scenario with the old TGP. I got the same thing, once I boresighted the Mav's in the air, the TGP would not focus on the actual next steerpoint, which is my target SPI. It seems to be locked on the boresight target at the last steerpoint. I don't know if I'm doing something wrong. I reset the CZ (never been an issue before). I will add a TRK file in the bugs section once I have time. THIS IS NOT AN AQ-33 BUG - POSSIBLY A GENERAL TGP BUG.

Request for a 509 FS G9-L / 44-33813 Balls Out (Capt. Milt Thompson) Skin

This is, to me, absolutely on target. We can establish either party is the dastardly villain, stroking their comical handle bar mustache, and stealing into the night all we want. It's been very well established that RB did breach contract. To try and weasel around this fact is to not understand business and what has to be done to protect a brand. However, where does that get us, the consumers? We know who to blame, but that hardly gives us a measure of confidence. What's worse is the lack of actual solution that benefits the paying customer. We clearly need more than just "Well it'll work until an undetermined date in the future." It's nice to know that they'll work, but what about the point at which they don't? What about the point in which they're removed from the software all together? Do we just get an apology? The BP episode of South Park comes to mind in that case: Soohhhrrreeehh. We're going to need something, not much, really. I wonder how many would be satisfied if ED says they intend to do something to compensate us in the event of total module failure.

The key command is currently acting as the throttle detent's micro-switch. The broken wire graphic suggests this is a temporary implementation. I don't think "some guys" are getting extra knots - either everyone is, or no one is. Would be nice if M3 weighed in and explained what we're all seeing.

What the actual frack? An aditional €172,95 EUR to get the Pimax to track properly? Now I understand why neither tech support or software/firmware updates could not get me flying straight. The wobly wibble is default.

GM-1 and Erhohte Notleistung could be used together. GM-1 and C3-Einsptrizung could not.

Sharing the coordinates is a start, but you still end up with a talk on. You can put the grid in as a waypoint, then use the waypoint as prepoint, but unless you get a perfect pepoint (rarely happened) and have a relatively empty area you still ended up talking the other crew on. The grid is a good start, but the talk on refines it.

Did you ask George to turn on the systems ?

So you're claiming that two months after the start of serial production at two different factories, Fw people (!), BMW people and AGO people meet up at a third place to identify the need for those exact access panels already there. http://www.wwiiaircraftperformance.org/fw190/Fw_190_A-8_Besprechungs-Niederschrift_4-4-44.pdf Got any comments on the required changes to the oxy-tank arrangement (like in the Ta 152) as well? Btw this part: Is completely made up by you. Really? Where? It says that the D and TU motors are interchangeable and that with the start of production of the TS/TH motors (TH never happened) that aircraft will be called A-9. There's not a single word on exchanging or swapping the motors (TS) in the field, which you're implying. The A-9 was a thing since early '44. At first projected with the F motor and later with TH delays, earmarked for the TS. In August. No R4 designation. Except that it never mentions motor-swaps. "Anlauf" means "start of serial production".