Jump to content

Martyn

Members
  • Posts

    70
  • Joined

  • Last visited

About Martyn

  • Birthday June 12

Personal Information

  • Flight Simulators
    DCS: A-10C, UH-1H, Mi-8, Ka-50, F/A-18C, FC3
    MSFS
    Rise of Flight
    Elite: Dangerous
  • Location
    Midlands, UK

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. This may be too late to be useful for you, but perhaps is interesting for others who are considering Winwing products. I recently ordered their Orion HOTAS after years of clinging on to my Sidewinder FFB2 stick. I was charged about £90 by FedEx today for import duties (£78 import tax + £12 min. handling fee). This was on a purchase that was $500 + $69 shipping. I don't have an exact conversion rate as it was paid for using US dollars already in my PayPal account. Interestingly, FedEx have delivered 3 of 4 of the boxes this morning but kept one back pending the payment, so I have the throttle base, joystick base and grip, but no throttle handles yet! Overall, the final cost is likely close to £500 which is reasonable given the issues and concerns I've read about with the TM Warthog which is a little over £400 and has fewer switches and a gimbal that can wear out etc.
  2. I was going to start Deployment tonight, after owning the Ka-50 for years but never putting it to much use. But after several VR-related crashes during the first few minutes I gave up as I need to sleep soon and it's a 45-min flight. Anyway, the original version of the mission gives you a hot start and the initial voiceover tells you there are three minutes before take off. The briefing text mentions the 30-min windows but I presume that's just flavour text. The updated version must have switched to a cold start without changing the timings. Doesn't really help you but it does explain why it's like it is. Glad I read your post though, as I just found the updated campaign version and guess that's going to offer a better experience than the original, if the original is broken in 2.5.6.
  3. Hello All, I finished this campaign today and wanted to post to say how much I enjoyed it - everyone has done a fantastic job, thank you so much I particularly liked the way the campaign was closed out at the end too. I didn't run into any major problems other than a couple of minor/random trigger issues as posted in other threads, and voiceovers cutting each other off in a few places due to (unlucky) timing. In the cases where my wingman was shot down, I often found myself opening up the mission file and extracting the audio files to see what chit-chat I might have missed. The banter between the player and wingman were always interesting, informative and fun The delivery of factual information about the conflict through the conversations and mission briefings was fascinating (and saddening) too. I've been flying DCS on and off for years but the only other campaigns I have finished so far are the less combat-orientated helicopter campaigns. Despite being technically proficient in the A-10C and Ka-50 in terms of flight and the operation of weapons systems, I consider myself poor and somewhat inexperienced in an actual combat environment. So I usually find any campaign a baptism of fire where I struggle to get past the first mission (especially as I don't like to play with labels or F10 map icons). In this respect, it was nice to jump into the F-15C and fly some missions more akin to the simulators of the 90's, which were less in depth than DCS but still engrossing. I don't consider myself a great air combat pilot either, but I knew most of the BVR theory and read the F-15C manual, so the obstacles were not too great to overcome. I do enjoy focussing on one aircraft at a time and learning it well. Thanks again to all involved
  4. Also ran into overlapping voiceover issues as mentioned in my other thread here, and in the post above that one I also mentioned the same issue with nonsensical messages about the Backfire: Furthermore, I had a similar issue in Mission 15 on first attempt (orders issued to both F-15 flights simultaneously); it was very confusing. Second & third attempt was OK, as I was perhaps faster to get off the ground and reach the AO in those flight. Still got killed all three times though
  5. Hi @baltic_dragon, thanks for the question. I had taken a screenshot of the results page and you're right: Score = 50 Result = 85 I misremembered it, and believed the '50' was the minimum pass mark for a campaign mission, based on something I read a long time ago. My mistake, it's good that you queried it! I'm just about to fly the next one...
  6. I flew the mission again this morning, as it's a UK holiday today. This time it ran better - almost as intended I think. I didn't do anything differently, but perhaps I was in a different position and the triggers fired differently. Attacked the 2x MiG-29s, shot down one, got into a furball with the other. Eventually it bugged out and we headed back to our anchor point. Shortly after, the call came in for the Tu-22 which we pursued to the east for a while, until it turned back (so far already better than the above runthrough) Then we had a long flight west to chase down the 3x Su-24s headed to Kutaisi. As we got with 10-20 miles, and very close to Kutaisi, the three-ship turned for home, and at that moment a voiceover came in from my wingman to say "all bandits destroyed", to which Rogue 4 replied with "good job, return to anchor point". Then I got the speech about the bandits wanting to stay out of our WEZ, and Rogue 4 asking us to continue to push these targets while over the TCT. So the voiceovers were confusing because the mission seemed to think the 3x Su-24s were both destroyed AND going home But either way, the trigger fired to signal the end of that task and the start of the next one... After the above, the call came in about the 4x Su24s approaching Rogue 4 and we headed east again, destined not to get there in time. As we closed in on this group, some of the voiceovers 'overlapped' (cut-off by a subsequent voiceover before the previous one had finished), or came in a somewhat jumbled sequence. Maybe I was unlucky with the timing and separate triggers firing near simultaneously. Didn't help that the in-game Overlord calls were coming in thick and fast, so I was mostly reading the subtitles. I didn't hear the audio with the "mother******s... they're doomed" for example - just saw it in the subtitles. The rest of the mission seemed to play out OK (instruction from Wizard to RTB, Dodge 7 scrambled) Mission complete, but only a result of '50' so not sure what counts as a full pass on that one (not that I'm concerned about score or kills; I just want a good experience). I've uploaded the track & Tacview files to the same folder linked above in case you want to analyse them Flying in VR is taking some getting used to, and I spend a lot of time fumbling around for keyboard keys I need to look at setting up VoiceAttack at last, as the overall experience is amazing.
  7. A few months on from my last attempt, I flew this mission again tonight. I can be like that with DCS when I hit a hurdle in a campaign - it takes me a while to feel like repeating the mission again. But I've just been away from DCS a while. Still on 2.5.6 - I didn't try the OB despite the enticing clouds! This time the mission ran a little better - up to a point... The Georgian Su-25s did their attack run as soon as I neared WP2, then a pair of MiG-29s came in from the north which I downed. Then we had some jumbled up voiceovers about letting a bandit go and "too late, missiles in the air", even though we hadn't fired anything. I think this related to a nearby Tu-22, looking at the Tacview. Hopefully the DCS track will have caught that. Next up, we were directed westwards towards some Su-24s which I caught up to nearing Zugdidi. Rogue 4 said to engage as long as they were over TCT (Tbilisi Controlled Territory), but as they were running away and nearing the Abkhazian border, I elected to save my missiles since the brief implied it would be a long flight. Unsure if I needed to shoot these down to progerss the mission, I followed them for a while, then eventually instructed by wingman to attack and he hit one, but it got away (I told him to rejoin). After that, I flew back towards the Bullseye but nothing else happened. I got standard AWACS calls about aircraft in the area but no official instructions about what to do next. After a while I flew back to Kutaisi to land. Just as I was about to come over the threshold, my wingman gave a "bandit down" call (mission voiceover) then Rogue 4 asked us to return to our hold point. (Looking in Tacview, the timing coincides with the Su-24s landing at Nalchik). So I aborted the landing, and headed back to WP2 at 28,000ft. Again, nothing else happened! I flew several orbits with time acceleration as I was a little bored by this point. Using F2 view I could see three Su-24s which appeared to be near the edge of the map. It was very dark and I was in VR (with short-range terrain rendering) but I could just make out some snow-capped mountains and lots of empty/flat terrain. Using the default AWACS calls I headed over - they were in the far east of the map. Shot them down, then 4 more bombers appeared, headed directly at Rogue 4. I was very close (probably because I was not where I was meant to be - voiceovers said we'd never get there in time) so attacked those but only had one missile left. Soon after, some Flankers appeared and chased me down. (I'd taken damage from an Su24 as I was careless after running out of missiles, then the Flankers finished me off.) So not a very successful run once again. I got a result of 90 so could have continued, but as I don't consider it a completed mission I ended without continuing and will try it again at some point. I'd appreciate it if you can do a bit more bug-hunting on this one, thanks. The Tacview and DCS tracks are both here: https://drive.google.com/drive/folders/1fG4RVaPsCS66Cn9MFzvFjcvpGWU4PvLx?usp=sharing
  8. OK, thanks for the response and looking into it. I'll be sure to save the .TRK file next time, if it happens again. It's hard to stay focussed on one campaign/aircraft when ED keep doing these free-to-play events!
  9. Of course, here's a link to the ACMI file https://drive.google.com/file/d/1vlWaqlTV3pZtPnyszWbpQuxeT9Jqin_c/view?usp=sharing Perhaps I strayed too far from the trigger point and in orbiting the area I didn't pass into it for a while. After a short time I starting doing a rough racetrack orbit and then kept overflying WP2 (Gori) each time. If you can find something amiss, that's great; if not I'll try it again at some point in the coming days and report back. Thanks!
  10. I just flew mission 13 for the first time. I didn't expect any instant drama due to the comments about reserving fuel, but... Seems a trigger didn't fire somewhere? Maybe I was too high or low at times, my altitude tended to drift between 26,000 and 28,000ft, as the F-15 doesn't seem to like attitude or altitude hold in a continuous gentle turn! But hasn't been an issue until now. Eventually, I flew back and landed about an hour after I took off. Still got a score of 50 but I chose not to continue as I think I missed some interesting events (even though I always enjoy non-combat missions as I don't get usually die halfway through!) I am on 2.5.6.59625. Will try again soon. I've recently starting flying some DCS missions in VR and enjoyed my first sunset and seeing the nighttime cockpit come to life, so it wasn't all bad. Thanks.
  11. Hello. After being stuck on mission 9 a while back (no fault of the campaign, just my own ineptitude and/or bad luck), I finally picked up this campaign again to push past it. This time events went as follows: After this point, no more instructions were received and it wasn't clear what I should have done next to complete the mission? I didn't fancy backtracking to my last waypoint just to see if I needed to hit a trigger there. I landed (though I realised later that I hadn't extend all the way out to the last waypoint, south-west of the airfield) and thankfully passed the mission with a result of 60, so can go on to the next mission, but I didn't get the 'success' notification as normally happens. Unless that only triggers at a score of 100? Great campaign so far in any case, thanks!
  12. Four-and-a-bit months on, any news on a fix for this mission, Sabre? I run stable, and while I saw the below update for this campaign in a recent Open Beta patch, I didn't see anything on this one yet. Despite my renewed enthusiasm to more deeply learn the A-10C earlier this year, I lost my momentum with this campaign issue and have long since moved on to other things. Now I'm waiting for Asobo to fix problems in MSFS instead :D It's not life or death, so you'll get no ranting or demands from me, but it is a product I paid for and it's broken, so I really hope to get a fix during this year... I would say that's being patient enough :) I bought the A-10C II so look forward to future content on that, though I won't get to fly it until it hits stable; can't be doing with the hassles of OB, nor the space require to run two installs.
  13. I hope that was an intentional pun on 'stable'. With your username to match, it gave me a good chuckle :D Looks like a fix is on the way as confirmed here, at least: https://forums.eagle.ru/showthread.php?t=275727 Funny that the above new thread was tagged 'Reported' but this older thread was marked 'Already reported'. I know, I know, I'm nit-picking now when I should just be thankful that big bugs from OB are being tended to after release to Stable... :noexpression:
  14. This is shockingly bad. After a 51GB download last night to 2.5.6 stable, I cannot continue the campaign I was flying as I can't get off the ground in one piece. My wingman always taxied behind me with his nose just inches from my tail, constantly stepping on his brakes to avoid a collision, in many previous missions in 2.5.5, but today he just crashed straight into the back of me when I held short to ask for take-off clearance. Repeated outside the campaign in the ME just to be sure it was the game at fault not something specific in the campaign. Utterly rubbish. I've been very eager for 2.5.6 to come to stable so I could see again in the cockpit at night and take a look at the Ka-50 cockpit update, but I'm not sure it was worth the wait. I'll go back to 2.5.5 until this is fixed. I guess the release of the the high-profile Supercarrier module in 2.5.6 only has led to that version being pushed out of the door before it was really ready. I'd gladly wait 6 months between stable updates if they could indeed be 'stable'. Very disappointing. I can accept minor bugs being left in for imminent fixes, but this one is pretty big for any single player folk out there.
  15. Thanks all for the confirmation. Glad to know I'm not going mad, or misunderstanding how it was supposed to work. But now that I think about it again, should the aircraft clock update with the adjustment or only the CDU time? Perhaps that's the bug, rather than the CDU offsetting the time by the adjustment value. Many aircraft have a clock that always shows UTC time, so it just crossed my mind that it could be the reason. The A-10C manual doesn't really say much about the clock itself... (though searching for "clock" finds quite a lot of results!!!) Regardless, it's on the list so that's all that matters.
×
×
  • Create New...