Jump to content

609_Relentov

Members
  • Posts

    526
  • Joined

  • Last visited

Everything posted by 609_Relentov

  1. +1 We’re not talking about an FM, so I agree, if they can just borrow the same guidance from a PW2 it would be great.
  2. OK, now it makes sense, I was doing the same thing (learning the LANTIRN in single player), and was wondering why the GBU-24 was not tracking the laser but the GBU-16 and GBU-12 were. Any word on if/when this might be fixed (by ED I presume)?
  3. +1 A mission I have/ran using the “hold” advanced waypoint “perform action” command no longer works as of 2.5.6. A column group with the hold immediately starts moving at the start of the mission - the stop condition flag has not yet been set to true yet. Just wanted to back up Paco in that I’ve been able to reproduce this bug.
  4. Thanks Paco, at least it confirms what I have observed. Not sure if anyone has added it to the bug list. Edit - I saw your post Paco in the DCSW 2.5 bugs and problems page and posted there to back you up; thanks for posting it. Oh, and thanks Grimes for the added info you shared in the original post.
  5. Were there changes to any advanced waypoint actions in 2.5.6? I ran a mission that had an armored group with an advanced waypoint do a Perform Task: Hold, and now it moves ahead right away (Enable Task is checked), whereas before this update, the column stayed put (type: custom). The Condition is: Probability: 100%, and the Stop Condition is: Is User Flag: 3 is checked. Is there anything different we need to do to hold/prevent movement now?
  6. Unless it has been changed, try this. Once in CCRP, and you see the target box/CCRP line pegged to one side of the HUD (I.e. slaved to a WP), click the OVRD OSB twice on the TGP MFD. This should center the target box/CCRP line to the center of your HUD. Then you should be able to TMS up to ground stabilize/lock the target box (TMS down will recenter on the HUD again), then you should be able to slew the crosshairs on the TGP. This is from memory, so I may have missed something, but it should get you close enough.
  7. If you hit the A/A button on the UFC, the right MFD should show the current missile selected on one of the OSB’s. Assuming you have both Aim-9’s and Aim-120’s, click on that OSB (can’t recall which one at the moment) and it should switch to the other missile type (I have a HOTAS button set to that OSB for this purpose).
  8. Yep, I noticed it was set to 1500 (default), but yeah, I'm getting good dispersal when dropped at 15-20k ft plus, again in CCRP using the TGP for the sight line auto release. I tried the CBU-97's tonight in CCIP for the first time, and got mixed results depending on the dive angle/altitude of the drop (i.e. sometimes they dispersed and hit targets, sometimes I saw no effect, so probably hit the ground), so I'll have to practice some more.
  9. I’ve dropped CBU-97s in CCRP mode from 20k ft+ using the TPOD, works great. I’ve found that I get more accurate results when I use area tracking and move the TPOD cursor a little short of the target. No problems with the submunitions releasing/bursting.
  10. For triggers - we currently have the ability to use AND and OR keywords between trigger condition rows. Can parenthesis be added so we can group multiple lines of OR conditions? This way, you can then check against a number of OR conditions being true, and then still group that with other AND conditions. It would allow for more complicated trigger logic without having to use a bunch of flags.
  11. Thanks bell_rj, but I’m not getting it to work. When I click down once on the ICP it highlights the “NB” at the lower right of the data panel. If I press “1” on the UFC for preset one, it changes from NB to WB, so I’m not following. Edit: Actually, I got it to work with more experimenting. So I hit COM1 and simply clicked on the preset number on the UFC (1 in this case, for UHF 240.00 for AWACs ), then hit ENTR in the UFC. As you mentioned, once I went back to COM1 it shows “1” at the top instead of the preset frequency, but it’s working at least.
  12. I’ve been able to change the preset, but then how do you select it so it changes the actual frequency you are on? I.e. the frequency showing at the top left? Thanks..
  13. This. I noticed my HMCS went away as well and had apparently accidentally hit DMS up. After hitting DMS down it came back up for me as well.
  14. Actually, if I don't have a waypoint near a target, once in CCRP and the TGP is the SOI, I just use the OVRD OSB button on the TGP screen, clicking it twice. This brings the TGP camera target box near the flight path marker on the center of the HUD, including the flight path line, so you can then just point your aircraft towards the target. Then you can hit TMS up to make the TGP camera/cursor stick (hit TMS down to reset it near the flight path marker again, if needed). After the cursor sticks/ground stabilizes, you can slew the TGP cursor to the target area, and now hitting TMS up will switch between point and area track. If you hit the TMS down it will reset the TGP camera again to the center of the HUD and you'll have to point your aircraft to the target again to hit TMS up to re: stick/ground stabilize the cursor/target box.
  15. +1 I was just noticing this as well, as I was finally trying to use the Lantirn pod in the RIO's seat in single player, and kept having to do exactly what's described above each time I went to the adjust-controls page. One time I miss/un-mapped a Pilot control setting as I forgot it defaulted to the pilot and had to quickly undo it lol.
  16. I’ve been having the same difficulties with AI JTAC lately. They are accurate with stationary targets, once they lase I have no issues hitting the targets. However, moving targets it’s another story. I can tell the AI JTAC (using a TOW equipped HMMWV usually, on weapons hold ROE) is lasing, as I can see the GBU-12 adjusting its flight path.. but in all cases with moving targets the bomb hits behind the moving units (unless it’s a long column on a straight road, then you might get lucky and hit one). It’s almost like at some point the AI JTACs were changed to area track and don’t continue tracking the moving vehicles. I recall it used to work for moving targets.
  17. Sounds similar to a post I had pertaining to the cockpit shake on the F-14, but only after hooking up with the catapult sled/shuttle via the “u” key: https://forums.eagle.ru/showpost.php?p=3866098&postcount=26
  18. Currently in the DCS mission editor, if you create a trigger you can use the OR condition with two or more expressions. Of course, if you put two expressions without an OR in between it’s assumed that the two conditions are AND’ed. What’s missing is a way to group multiple lines so that you can properly use the OR (and assumed/default AND) properly with multiple rows of conditions. For example, it would be very helpful to have something like this, so we didn’t have to use multiple flags or convert to a Lua script: ( Expression A Expression B ) OR Expression C Thanks! Relent Edit: Moderators, please change “model” to “mission” in the subject shown in the topic list view... thanks.
  19. Having the same issue with the F-14, posted my observations/thoughts in this F-14 thread: https://forums.eagle.ru/showpost.php?p=3866098&postcount=26
  20. Having the same problem, after enough times I see what "appears" to be the pattern. Basically, as you creep forward to line up with the shuttle, if the nose gear/bar goes past the shuttle, even if when you hit "u" and it pushes you back slightly and raises the blast shield, hitting the salute key combo (LShift-u) does not initiate the catapult launch. Also, I notice that when you've gone past the shuttle and hit "u", the plane (from the cockpit POV) is shaking quite a bit. Whenever I see the shaking, it's pretty much guaranteed not to launch after the salute. So basically the solution I've seen, is to release the shuttle ("u"), enable nose wheel steering and move (i.e. in a circle) to re-align with the shuttle again. But this time, I'm very careful about not passing the shuttle... almost like you have to be just short of it when you latch to the shuttle ("u"), and not observe any (major) shaking - then the salute launches OK for me.
  21. I was able to replicate the error just now in the mission editor: - Added F-5E-3, SKILL=Client - Changed the COMM value (MHz AM) just under the PILOT text box in the upper right of the properties pane to "124", where the numbers turned red - Clicked Save and I got the error dialog as you did: "Invalid frequency 124 MHz" - After changing that value from 124 to something valid (for the F-5E-3 UHF radio AN/ARC-164) between 225 and 399.999, I was able to save the mission. So it seems that when you add an F-5E-3, it's somehow defaulting the COMM value to 124, which does not allow you to save the mission. Can you check what value you have, and if it's 124 change it to a valid value.
  22. Whatever key you use to bring up Jester (e.g. "A" key, or in my case a button on the throttle), once the wheel comes up and you move your head (assuming Track IR, for example) to point the line that comes out of the center of the wheel to one of the wheel slices, just hit that same key (e.g. "A") to select that slice/command. Also (assuming using Track IR), if you don't point to one of the slices (e.g. leave your Track IR/head centered) and hit the Jester (i.e. "A") key, you can "drill down" to the next level of Jester commands. Keep hitting the Jester key (while your Track IR/head centered) and eventually it'll close the wheel. Not sure if that helps given your way of invoking the Jester wheel, that's just how I invoke it.
  23. That's correct. So it may not be for everyone. However, it's an old stick that isn't really supported, so I don't expect the FF to work much anyway, but without the return to center the stick is useless. So I'm good with just being able to use it for all my sims without having to worry about the tension. As mentioned, you can always try it and see if you can at least fly the F-14, then if you want to get the FF back just check Allow instead of Deny and you're golden.
  24. I just disable the FF effects via the registry, which gets me back the return to center force on my MS FFB 2. Otherwise I get the limp joystick effect sometimes with BoX, CoD, and DCS. All I really want is that return to center force, so for me it's worked great. Here's the steps (works on Win 7 and 10 for me) if you want to try (if you don't like it, you can always change the permissions back to Allow and you're back the way you were: - Open the registry editor (click the "Start" Windows icon at the left of the start bar at the bottom of the desktop and type "regedit" in the text box marked "Search programs and files"). - Navigate to the following "hive" via expanding the folders under "Computer" on the left pane: HKEY_CURRENT_USER/System/CurrentControlSet/Control/MediaProperties/PrivateProperties/Joystick/OEM/VID_045E&PID_001B/OEMForceFeedback - Once you see the "OEMForceFeedback" folder, right-click on it and click "Permissions.." - You should see "Everyone" under the "Group or user names" - left click on it to highlight it, then under "Permissions for Everyone" click the check box under "Deny" and to the right of "Full Control" - Click OK - Close the registry editor
  25. Thanks, I was scratching my head on that one as well.
×
×
  • Create New...