DragonSoulkin

Back on topic, I asked this a month ago and got no response. It's mentioned that the aircraft is being based on a manual available on Amazon, which manual? There's a few of them.

What manual in particular? There's multiple ones available on Amazon.

Who said I was angry? Wasn't me, your interpretation of what counts as anger needs some adjusting bud. Here I'm just pointing out that when a release is planned around a certain time frame that with ED expect it to be much much later than that and you'll never be disappointed. I just don't like being led on and learned to set my expectations of timing really low. Hence why I'm not angry as you seem to think I am. What does make me angry is when people try to disseminate something as superfluous as my emotional state off of incomplete information.

Like I said, can't get upset if you stick with the mindset of "I'll believe it when I see it". I hear switching to summer release, I start thinking maybe next year, then ya can't get disappointed.

Me sitting here when I initially heard Q2 being planned release "I'll believe it when I see it." Can't get disappointed if you already have the bar so low that you don't believe a single thing that's ever said from any representative of ED about a release date. It does feel like a bit of a slap in the face though when another plane (yes, I get it, it's not an ED product) gets released before this one, without a pre-order, and here we get to see all those people play with their new toy and we're stuck here just watching or flying it just to have something new while we wait. Of course I don't want a botched, bug filled near or completely unplayable aircraft, but I also don't think ED should be getting people's hopes up by putting out a release time-frame if they're not going to hold themselves to it. Just release it when it's ready and stop giving people false hopes on a projected time-frame, and then we reach that time-frame and nothing and then get told some time later, then later later, then later later later, then later later later later.

I'm a livery artist and usually participate in the livery contests so that's probably where most of it went. Freaking dumb how they can't come up with a better way to post your submissions sometimes, the last two they wanted full PSD templates of your works. Any idea how large a Hind Livery is in the templates? That file can get over 50gb easy. And I bet PMs take that space too doesn't it? Wouldn't surprise me that the crap uploaded into userfiles contributes too.

Dunno how I'm supposed to upload a track file when even a couple minute track file exceeds the limit of 37.14kb, what the hell kind of file these days anymore is that small in the first damned place? Freaking dumb, alternative method I uploaded it to my google drive and you can download it from there. https://drive.google.com/file/d/1SSSW2-nd8hY2WLD9sXIsAUSK2MHOK3yG/view?usp=sharing

This is literally the ONLY game out of well over a hundred that I've played on PC that this has EVER happened.

Problem is for me EVERYTHING relating to the radio and ARK are locked and I cannot for the life of me figure out how to unlock any of it outside of random chance that when I spawn in I can use it.

I was just thinking this.

I'm currently trying to resolve this as well, so far adding the exceptions isn't working. Edit: Eventually got it working. Had to run a repair after adding the exceptions to re-install the missing files.

I'm running into a weird intermittent issue with the MiG-15bis. Some days I can click the radio and ARK-5 controls just fine and others neither will respond to any mouse or keybound inputs. The mouse changes when hovering over the knobs, dials, and switches but clicking right or left mouse or scrolling does nothing and I cannot for the life of me figure out what's going on. Is there something somewhere in the aircraft I'm missing half the time or is this a bug?

Heh...no. Steam is fed up with scummy developers and wants to hold them accountable.

Something I'm curious about with the FF MiG-29 seeming to be around the corner finally, how is ED setting up the RSBN beacons? Are they doing the same thing with R_NAV_data.lua files? Or is it going to be something that'll be built-in to the maps and an additional option to put a beacon like we can with the TACAN beacons in the mission editor? And if that's the case will the MiG-21 be able to utilize them? This would just compound the BS that the MiG-21 is just an abandoned module when the MiG-29 can utilize RSBN on all the maps and the MiG-21 can't because it's an abandoned module and won't be getting updated to fill those gaps.

Not just yours, but yes they're in there as well.

Hoping someone has an idea as to what's going on here. I use OMM (Open Mod Manager) and as of a couple updates ago my cockpit mods stopped working. They're just reskins with English labeling instead of Russian/Chinese and they were working up to about a month or so ago. I re-packaged the mods in OMM and they worked and figured I was good but the next time I logged into DCS they stopped working. Any ideas as to why this is happening? The files are all still there in my SavedGames/Liveries folder but DCS is not using them.

Manually clicking "Save State as..." and saving from there also crashes the server.

On our dedicated servers I haven't been able to get this to work. I've got the option selected to automatically save the .sav file upon mission restart or end but it's not saving.

The root problem still remains. STILL, we do not have RSBN/ARK on Kola and Sinai, or Afghanistan, Iraq, and now Germany, WITHOUT BREAKING INTEGRITY CHECK BECAUSE WE HAD TO MAKE THE DAMNED THINGS OURSELVES! So is the MiG-21 just an abandoned module at this point is that what it is? Seems like all that gets done anymore is half baked products that never get finished, not just in DCS but in just about any other game these days.

Well that's kinda what happens when you ask for PSDs and not dds files. I imagine the PSDs are going to have all the layers merged to protect artist intellectual property, and save space. Unless we're going to go back on that requirement like the last livery contest and allow users to submit functioning liveries, instead of PSDs. Where's the discussion thread then to ask questions?

Okay, so my thread gets merged into here, a thread with a marked solution. My issue of CASE II being reported in CASE I conditions has not been solved.

Also having this issue, I made a separate thread for this in particular but it's possible that these issues are stemming from the same root cause.

I'm having issues with the carrier ATC incorrectly reporting the approach conditions. In this instance I have set up what is a clear, no clouds, no wind, fog mode off, basically a perfectly clear sunny windless day. The carrier ATC though is reporting a CASE II approach when it very clearly is a CASE I. I am also having issues of the carrier ATC reporting a CASE III approach when in what would be a standard CASE II, and perhaps it's the same thing causing the issue of getting a CASE II approach in CASE I conditions, but for the moment I'm just trying to get the carrier to report a CASE I approach. Attached is a screenshot of the weather settings for the mission and a .trk file. vTF-77 Dynamic Training V1.2.92-20250110-015244.trk What it looks like from the carrier.

At this point I'm less interested in having a livery paint-kit for the Phantom, and would much rather have dynamic board numbers for the Tomcat and Phantom. It's a pain in the arse for those of us that make liveries for squadron/s and takes up a ridiculous amount of storage space having to manually paint the numbers on for every individual modex, on each separate template that has the location/s of where the numbers would be placed (nose l/r, wing l/r, and tail l/r). Quadrupling the size of the livery files they would be if we just had dynamic board numbers and just had to worry about painting the names on the canopy rail.

I'm having the same issue with the wheel chocks. Edit: If you use the keybind "Pilot Salute" the wheel chocks go away and you'll get directed by deck-crew to a catapult.