Jump to content

Fishbreath

Members
  • Posts

    705
  • Joined

  • Last visited

Everything posted by Fishbreath

  1. If we're dreaming, I'd take DCS Su-25SM over DCS Su-25T, but in the meantime, adding some convenience would make me happy. :P
  2. The keybinds for 'Zoom in slow' and 'Zoom out slow' change the FoV (and, by extension, zoom the view) smoothly. I have them bound to half of a hat on my HOTAS.
  3. Wrong bug. The other one says ripple and salvo don't function. This one says that the switch to go to instant salvo mode (i.e. the separate 'salvo mode' keybind) doesn't move. I've never really used it, though, since setting the salvo knob to 'all' and the ripple knob to 'salvo' has the same effect.
  4. Okay, cool. I'll give that a try later—so set an attack-some-unit task on the waypoint with an AI wingman? With a little luck, I'll be able to do some trigger-fu to get that feature without actually having to bring an AI wingman.
  5. The best thing about the Ka-50 is how easy the INU is to use. I've heard it said that it uses GLONASS fixes to keep the INU aligned in-flight, and the whole Shkval-at-fix-point bit is just so easy.
  6. Although I don't expect it to get a lot of work, there are two things that would improve the experience in the -25T immensely. 1. Keybind for 'toggle HUD display of current waypoint' or Bring back the FC2-era mission editor option to mark a waypoint as a target. This is within the capabilities of the aircraft as modeled: you can right click to get a crosshair and left-click to mark a target, or you can play the Instant Action mission (which has the target markers). Having a way to either set it up in flight for an arbitrary waypoint (as the first option would allow) or make it pre-planned in the DCS World mission editor would be very nice, and make re-attacking much simpler. 2. Keybind for 'disable waypoint auto-cycle'. This one could be done for all the Flaming Cliffs-fidelity aircraft, and would be handy if #1 isn't feasible. It would let us Su-25T drivers use the HSI to cue us onto waypoints without having to cycle through all our waypoints for every run.
  7. I wasn't able to get it to work--crosshair yes, but in the vicinity of a bunch of ground vehicles, no diamond. Does it have to be right overtop of something? That's hard to do from a distance/with headtracking, but if it's a route toward working out how to include them in missions, I'll have to give it a try later.
  8. It's odd that the actual navigation stuff—the next waypoint indicator and the like—point correctly even when the compass reads wrong.
  9. Two yellow levers on the left side of the cockpit in the back, aft of the Shkval control panel. Pageup once, I dunno; pageup twice is auto, pageup three times is either manual or maximum? Someone else will know. The alarm is a warning for rotor RPM, I think--you'll also sometimes hear it if you're carrying a heavy load and demand too much from the engines. Radar altimeter measures altitude above ground level, barometric altimeter measures height above sea level. You definitely want to do whatever you have to to use the main throttle handle.
  10. Strange—I was hosting a mission with a friend, and 2/3 times he was able to launch on an H50 radar without missiles blowing up. A server restart fixed it when it didn't work.
  11. It might be possible to tease out some data after doing that in a Prepare Mission setting. I was probably also looking in the wrong place in the mission file—if that's how you do it in the cockpit, it's probably not in the route list in the mission file. I'll play around with it again tonight.
  12. Can't you make an immediate follow-up shot with launch authorization override, too? I don't think I've ever tried it, but I seem to recall someone saying that worked.
  13. In addition to an option to show hidden units in the editor and a way to make a unit invisible from the cockpit but not invisible from the F10 map or the ABRIS, I would very much like a way to mark a waypoint as a target for the Su-25T. (See research into the mission feature in this thread). According to posters there, it was possible to mark a waypoint as a target for the Su-25T in the Flaming Cliffs 2 editor, which would cause it to show up on the HUD as a diamond in air-to-ground mode. Having this feature available would be a huge quality of life improvement for the Frogfoot, and the code is likely already knocking around somewhere, given that it's a former feature we're now missing
  14. Quick update: copying the waypoint in yields a mission that doesn't load at all, which is an obvious step backward. I've posted in the mission editor feature request thread, so sound off there if you want the target diamond feature back.
  15. Same issue for me--I can't get the Su-25T to release even pairs of bombs from the outside hardpoints. Ripple set to 4 or все, salvo set to anything, FAB-250s on the outer four, dropped in visually-targeted CCRP and CCIP modes (tested both), came off the hardpoints one at a time no matter how long I held down the pickle button. IIRC, KMGU/MER mode worked a few days ago to fire off two hardpoints with MERs mounted, and gun pods still fire in twos or fours per the panel, so not everything on the salvo panel is broken. Just most of it.
  16. Last night I (finally) had a look at this, but it wasn't immediately obvious what the difference was in the mission file. I'll try just copying the waypoint later; if that doesn't work, we're going to need actual support from ED, and (for all the good it will do) I'll post in the mission editor feature request thread.
  17. That's the only case that worked, Hog, as I said--starting the mission with the Ka-50 (and ABRIS) booted and deactivating or destroying the threat after that works, but that's only a solution for singleplayer. I'd like to be able to do something for multiplayer missions where I might take off late in the mission in a Ka-50 after flying something else beforehand, and that's the part that seems impossible without some way to make a unit present, but invisible to players in the world.
  18. Yup, that's correct. Placing a threat that dies after ten seconds with the helo started shows it on the map; starting the helo at mission start yields no threat on the ABRIS. There's a waypoint setting for JTAC for 'invisible', isn't there? I imagine that only affects the AI, though, and doesn't actually make it invisible in the sim. If there was a way to do that, I could probably get away with disabling the unit's AI and just leaving it there. Or maybe I could stick it under an invulnerable building or something--can the mission editor overlap units? Edit: seems like it's basically impossible to make a threat icon without an actual, specific threat active and visible on the map. Besides modding invisible, generic, nonfiring threat units, I'm not sure it's plausible.
  19. Right—you have to have some product installed that either is or can be traced back to LOMAC. I'm not bothering, personally—if I want a fast-mover before DCS F/A-18C, I'll just wait for the Eagle/Flanker standalone. :P
  20. Don't forget that the non-clickable 3D cockpit/advanced flight model F-15 and Flanker are in the pipeline, so you could snag one of those for the $15 price point when they're released, rather than spending for LOMAC and FC3.
  21. At least the Ka-50 would get some love for once. :P
  22. So, as far as I can tell, threat circles on the ABRIS come from threats in the mission editor that are: 1) Active 2) Non-hidden. What if I want to place a threat circle as a feint (i.e. bad intel)? Is it possible? I tried ticking Late Activation and Visible At Start, but although the threat showed up on the mission editor map, it didn't show up on the ABRIS.
  23. I only see pylons in both of those.
  24. So, honest, semi-relevant question from a mostly offline Ka-50-er—how good are the fighter radars at picking out a helicopter down in the trees?
  25. You can buy the upgrade, but you'll have to have BS1 installed any time you want to install BS2. I own BS2 only, but a lot of BS1 owners seem to think the upgrade version isn't worth the extra hassle.
×
×
  • Create New...