Jump to content

eifionglyn

Members
  • Posts

    26
  • Joined

  • Last visited

Everything posted by eifionglyn

  1. Worked out what my mistake was. I'd used the KC135 MPRS as my tanker, - stupidly assuming from its model that it has basket and boom available. It does not, in game it appears to be basket only. The boom is purely aesthetic. I've now added a regular KC135 and it does talk to me. The KC130 (basket only) does not, presumably because I'm not equipped to refuel from it. Bit confusing, I'm also not equipped to land on the carrier, but if I tune to their frequency and declare inbound they at least tell me to bugger off!
  2. This is just a SP mission I've thrown together myself. Nothing fancy, just has some Bears circling at 10,000 and some trucks on the ground to shoot at, a tanker and a carrier. I use it mainly to learn an new module or when I need a refresh. Edit: The carrier will talk to me. It's just the tanker. I'll check its settings again.
  3. Yep, I'm using MIC Switch FWD and MIC Switch AFT depending on if I want to use the primary or aux radio. Oddly enough I've noticed that Anderson ATC will talk to me on 250.1 once I start rolling down the runway. Still can't raise them on 126.2, and the tanker still ignores me.
  4. Single player mission, nobody will talk to me in the F15E other than the ground crew. Tried with easy comms on and off, makes no difference. I use multiple other modules in the same mission, no comms issues with them. Anderson AFB on 126.2, Tanker on 251. Have read the manual and pretty sure I have the radios on, volume up, mic on etc, correct frequency tuned. Is there a secret mute all radios button I've inadvertently pressed, or is this a bug?
  5. I've also tried it deliberately setting a wildly wrong QFE, it makes no difference. Obviously it moves the waypoint / target circle, but as I thought, that's just there as a guide to the pilot to visually acquire the target, it doesn't factor into the jets weapons employment parameters for rockets when using AGR.
  6. 211 turns on the fixed sight. 220/221 is target motion measurement on/off, which I believe is off by default. I have tried it with both and it doesn't seem to make much difference. Right here's a track file, air start 10km so away from the disused airfield at Kobuleti. There is a single truck in the middle of the runways. viggenRocket.trk
  7. I have dialled in the correct QFE calculated from the F10 map, and verified this is correct by comparing the pressure and radar altimeter readings when flying straight and level over the target area (trucks on an airfield so it's flat). It's my understanding that QFE setting is irrelevant for rocket delivery in ANF master mode as we're using radar ranging. I'm placing the pipper on the target, unsafing the trigger, keeping the pipper stable on the target, waiting while the range bar shrinks down and flashes and only pressing weapon release when the 0.5 sec 'wings' cue appear either side of the pipper. I'm not sure how to edit a track (or record my screen for that matter) but I'll look into it as this is pretty reproducible.
  8. As the title says really. I'm a new-ish Viggen driver trying to get to grips with rocket delivery. I've been following Chuck's guide and some of the better YT tutorials like Deephack and Iain Christie. And no matter what I do, my rockets always go long. Not massively long, but long enough for the unarmoured truck I'm aiming for to take no damage. I get they are not precision weapons and more of an 'area saturation' thing, so I would expect a spread of impacts around my targeted point. But I'm finding they consistently, repeatably go long. Anyone else experienced this? What might I be doing wrong? Thanks in advance!
  9. Happened to me too, latest OB, single player MT Marianas map. Cover would not open by clicking or when bound to a button. Refuelling switch does move when bound to a button, and allows AAR when in the forward position as expected.
  10. Will Virpil's software talk to my VKB stick?
  11. This may or may not be a stupid question so I figure it goes here. I have the VKB T-rudder pedals - no toe brakes. I figure I can use the twist grip on my stick for differential braking. However, DCS picks up the twist as a single axis. If I assign it to the left brake and then assign it to the right brake it takes the assignment away from the left brake. Is there a way for me to tell DCS to use the Z axis of the stick from centre to fully left as the input for the left brake and from centre to full right as the input for the right brake? Or alternatively, can I set a modifier somehow that when I hold a button down it makes DCS treat my rudder pedals as toe brake input? Currently, I just use a hat on my throttle as toe brakes. It works, kinda, but it's not great.
  12. Thank you! I was going mad clicking on everything, and then when I did it wasn’t sure how.
  13. As the title says really. I've designated a number of TOO's with the TPOD, cued them up as targets for GBU38 and successfully dropped them. Great. Now I'd like to navigate my way back home, using waypoints. But I can't select my waypoints anymore. All the EHSI will cycle through is T0, T1 and T2. I've tried hitting DESG, hitting NWS to put the TPOD back to Snowplow or VVSLV, I've put the HUD back in NAV mode, put master arm off. I've no more weapons on the jet but it won't go back to navigating on waypoints. Right - I've somehow done it. Long press of waypoint increment, I turned the TPOD back on, and pressed NWS so it said NO DES and now wayponts are available to select again. But which of these actions, if any, is the right one to do I don't know. The AV8 is great, in those times when you're not wondering what the hell the jet is doing *that* for.
  14. Just tried with the latest patch - v 2.8.4.38947 Display going black on turning on the pod is fixed as far as I can tell. Still shakes when ground stabilized / area track, but steady if WP slaved or point tracked. Noticed in patch notes it's now listed as a known issue so I'm sure will be fixed in due course. Thanks Deka - still loving the JF-17
  15. Interesting - I get different behaviour in MT and ST. Shame you've just got the module and this is your early experience of it. Hopefully they will fix it soon, she's a great little jet.
  16. I never have the mirrors turned on. In ST I'm not able to comment on the behaviour of the pod as when the pod is on and uncaged my entire screen goes black when looking ahead. If I look to the right I can just about get to the avionics power switches to turn the pod off which restores the view ahead. Powering up the pod again and uncaging it makes the screen go black.
  17. Just noticed some odd behaviour in the JF-17's targeting pod since updating to 2.8.3.37556 Open Beta, in MT and in non-MT - though the bug is different in each. In MT, the view of the targetting pod display shakes around making it impossible to identify or designate targets. Effect is more pronounced at higher zoom levels. Wasn't like this till the previous patch. Previously in slaved mode it would drift slowly if pointing at terrain beyond 20 NM, but would fix to terrain under 20NM. Now it shakes about. I thought this might be a MT bug, so tried the same situation in non-MT. There's a bug, but a different one. Now when you enable the targeting pod the screen - as in the entire screen, not just the MFD - goes black when looking straight ahead, look ~60 degrees off straight ahead and the display returns. Turn the power off to the pod, and the bug goes away. Turn the power back on, and as soon as it's started up and you uncage it, the screen goes black again.
  18. Just bound my Steam account to my DCS shop account and guess what - I'd bought FC3 years ago and completely forgot. Now I've got all them to play with too
  19. Oh good. It's not just me being a complete idiot then! I think that's what I like about helos is you can just sit there and take your time to scout, see what's what and what matches up with the briefings. Fixed wing you have to be going somewhere all the time, and fast. Didn't know you could get modules on a trial. Will look into that. I have the Steam version so not sure it will work for me. My plan is to get the F-18, then some rudder pedals, then the Huey and then a decent hotas, probably in that order.
  20. Hi, Hoping I can get some pointers on what to work on so I can take on the Su25t single player campaign. Currently attempts at even the first mission result in my losing situational awareness, being unable to find targets, yes they're at waypoint 6, yes they're marked with red smoke but I often can't spot what I'm actually meant to engage. Even cheating with labels on I have trouble spotting them. And even if I do spot some tanks on the road, everything happens way too quickly, and by the time I've got a target locked and ready to release weapons I'm within seconds of overflying the targets and inevitably eat a SAM. The thing is, I'm an OK pilot with the Su25, I actually enjoy flying it, I can taxi, take off and land with no problem. I understand and can use the navigation and autopilot systems. I'm happy with weapons employment in training missions I've created. I can put guided missiles and unguided bombs pretty much where I want them. But try and put it all together in the campaign missions and it all goes to pot. So there's two things I need to improve. Visually acquiring targets, and secondly, getting the jet ready to employ weapon on that target before I've overflown it, while at the same time avoiding enemy fire. I don't have any such issues with the Ka50, perhaps the more slow, methodical employment of an attack helicopter suits me more than a jet. I think I should make some training missions that include stuff that is actually going to shoot back at me rather that statics to practice dropping bombs on. Any suggestions for what would be hard enough so that it's a challenge and I'm learning but not so hard that I get instantly blown up. I'd like to get the F/A18 one day, but need to get competent at using a ground attack jet before I spend the moneys.
  21. That's brilliant! Thank you so much.
  22. Just upgraded from the Logitech extreme 3D to the X52 Pro. A couple of observations / questions. The slider jitters. Fine, I was expecting that. I use the Logitech profiler software to set the slider as 3 bands rather than an axis, and assign the zoom in / zoom out view keys to the top and bottom band, and nothing for the middle. Works great. But, now that I have a profile running in the profiler software, DCS doesn't see the pinkie button as button 6 anymore. The profiler seems to take over and now it can only work as a 'shift' modifier button. It's a shame, as I fly gliders in RL, many of which have a stick trim, so grabbing the pinkie switch, moving the stick then releasing is already in my muscle memory. Secondly, if I plug in the joystick, fire up DCS and try to take off I find the joystick axes are crazily sensitive and the poor Ka50 gets slammed into the ground till it's a smoking heap of metal. But wipe the controls (i.e. move them fully stop to stop in each direction) it's like DCS (or windows? - no way of telling) now has a mapping of the entire range of motion, and I can fly properly. Didn't notice the need to do this with the Extreme 3D. I'm still in the return window for the X52, and am debating whether it is enough of an upgrade to justify the cost, or return and put the money towards something better.
  23. AFAIK the ABRIS doesn't talk to the autopilot. To use the route mode hit the WPT button then one of the numbered buttons on the PVI 8000 to select a waypoint, trim some forward cyclic to get some speed, then engage route mode. The ABRIS is there more as a map / reference / info source for the pilot, rather than interfacing directly with other aircraft systems.
  24. Just got mine registered succesfully :-) off to try it now.
×
×
  • Create New...