-
Posts
7026 -
Joined
-
Last visited
-
Days Won
4
Content Type
Profiles
Forums
Events
Everything posted by baltic_dragon
-
feedback Raven One Campaign Review / Feedback
baltic_dragon replied to jmarso's topic in F/A-18C Raven One Campaign
@IceyJones you and me both. If something is not working in the campaign because I messed it up - I'll be the first to admit it and fix this. But if campaign stops working because of behind-the-scenes changes in how the Supercarrier taxi system works, that really makes me mad - because it usually means a few hours of trial & error testing for me with different aircraft configuration on deck until they finally stop crashing one into another. And it makes me want to uninstall whole DCS as well.. Please disregard these issues and continue to support us (the 3rd party devs). I don't think these issues will ever disappear because DCS is a constantly evolving projects, and that means bugs will be appearing quite often. -
Thanks, that's the kind of feedback I love to hear
-
The Enemy Within. Mission 15. Any hint?
baltic_dragon replied to Odessa's topic in A-10C The Enemy Within Campaign 3.0
Yeah, this is just one of the DCS AI issues I have zero control over... -
@Excal301 make sure you are not on FM band when switching the freq, this is a common problem / user error with the new radio. I am 99% sure this is the issue.
-
investigating Mission 2 + 3 Experiences
baltic_dragon replied to Ready's topic in A-10C Iron Flag Part I Campaign
Thanks for the feedback. A lot of issues are linked with changes in core DCS between the release of the campaign and now (TACAN - I assume you used it in A/A mode, and now it works only in A/G even with airborne tankers; Biff probably stopped communicating because of the new DCS radio system that completely messed up a lot of missions and campaigns - but it may also be user error, check if you are not on FM band when changing the freq). There should be further ATC comms, perhaps you were in a wrong position.. or perhaps something else got borked, it 100% worked OK before, but DCS updates have tendency to break things. Bif I am only one person and it is very difficult to keep up with updating already released stuff - and I have to rely on reports like yours, but even then it usually takes time to get to bottom of all the issues and have them properly fixed (also because when I fix some things, others get broken with DCS updates). It is a vicious circle which unfortunately probably will never change, so I'd like to ask you (and others) for more patience and to keep supporting our (3rd party campaign devs) work, as it is not super easy I'll try to put things in order for next patch, although it may be tough as I am away from my gaming rig till almost half of January. Anyway, thanks for the report! -
HMD Labels
baltic_dragon replied to Jack Summers's topic in F/A-18C Raven One: Dominant Fury campaign
Possibly that is because the whole campaign has not yet been updated to the new datalink. I already did it for Raven One, but it takes time (together with all the other changes introduced to DCS that require a lot of work on old campaigns, like new radio system or upcoming taxi directors). This will be done, but most likely only for February patch (I am away from my gaming rig for a month)... -
Mission 15 - is there a missed comms push?
baltic_dragon replied to Sandman1330's topic in Bugs & Problems
Thanks! I'll get to M15 soon and update it, for the 20 Dec patch M14 got a massive overhaul. It takes time to fix everything that gets broken with almost every update -
Well, I’ll be happy to refund you for this product since you clearly have no idea how DCS works. Just PM me and I’ll send you back the money because you completely don’t understand how many months of work goes into making a campaign that is worth one pizza - and if you cannot wait one more day for a fix, I’ll happily reimburse you and never hear back from you.
-
investigating Mission 8 - warrior goes radio silence
baltic_dragon replied to arneh's topic in Bugs and Problems
@Pyrocumulous is it possible that this is the new radio system implementation? If you are blocked from the transmitter (for instance by the mountain when you get too low) you may loose radio comms, which is realistic but not optimal for a campaign where you don't have an option to ask someone to repeat last transmission.. As for JTAC - IIRC this is the stock DCS JTAC over which I have zero control, so there is nothing I can do to fix this. -
@spaceBunny well, thank you for your sarcasm. My priority is to fix bugs and right now I am spending around 70% of my time fixing stuff that used to work but get bugged with every patch of the game, which forces me to revisit old missions and repair them, but with the next update something else gets broken... it is marked as fixed, but you will get the fixed version only when the new patch lands (should be tomorrow). Still, just tune in your radio to 251 (the middle one) and all will be fine even in current version. Hope this helps.
-
Yes, not far from the end! Turns out the problem was with the AI helo that now for some reason refuses to land.. I tried everything and finally just changed the parameters of the trigger to make the mission think it landed even if it is in perfect hover just 1m above the ground...
-
fixed internally Mission 10 - trigger issue on second SAM attack
baltic_dragon replied to lowki's topic in Bugs & Problems
Should be fixed for next update. -
M14 should be fixed now. Will fly it once more, but it should be good to go for next OB patch!
-
M14 Olive does not take off.
baltic_dragon replied to sideshow's topic in F/A-18C Raven One: Dominant Fury campaign
So, Olive not taking off is fixed, however later in the mission she just randomly flies into Cyprus and no matter what I do with triggers etc it always happens. I will have to probably spawn a new AI in her place to take over tasking which means a major re-work of the mission. I still hope to be able to fix this for next OB patch, but chances now are slimmer... -
@Agim this issue is now fixed. The helo not landing properly is indeed a DCS bug, but I managed to find a way to get around it. Fixed for next OB patch.