Jump to content

Yurgon

ED Closed Beta Testers Team
  • Posts

    10259
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by Yurgon

  1. Ist das nicht im Apache sogar der Default? Ich dachte das funktioniert da, abhängig von der Stellung des Intercom-Switches.
  2. Two of them. a) Transmitting radio commands no longer plays the associated audio files ("Two, break left!", "IN", or whatever). b) Other stations still transmit messages that can be heard by the player, meaning their AI isn't completely switched off (see the above remark about "No further tasking. You may depart" after the last target was destroyed). Did you play the tracks? It's evident in both of them that after a certain point, transmitting radio messages via the F-keys no longer works.
  3. Yeah, when I open a copy of the mission in the ME, I get the same. Instead of selecting an IP, I get a dialog for a trigger zone, although I hid all of them. Normally the ME should update the structure of a mission once it's saved, but saving my copy of this mission didn't help. Also quitting the ME and opening the previously saved mission afterwards didn't help. While I have no idea how something in an old mission might cause radios to break in flight (but only sometimes, and seemingly under random circumstances), it seems that's exactly what happens here. Welcome to the wonderful world of DCS mission editing. Edit: If you have the time (and provided you've got the old A-10C module installed), can you fly the original mission in the old A-10C and check if the problem appears there as well? Edit #2: I've filed a bug report with the Closed Beta Testers and have referenced this thread there.
  4. There's indeed something funky going on, but I'm not sure whether this is intentional or not. Feels like it's not intentional, though. This is one scenario (not involving markpoints, to keep it simple): Select WAYPT page in the CDU Set CDU STEER PT dial to FLT PLN (and observe F1 displayed in line 1): Now the +- rocker does not cycle through waypoints Set CDU STEER PT dial to MARK or MISSION: Now the +- rocker cycles through waypoints just fine It is my understanding that the +- rocker should be able to cycle through waypoints when the STEER PT dial is in the FLT PLAN position. ========== Interestingly enough, setting the CDU PAGE dial to WAYPT and thus selecting the WP INFO page allows to cycle through waypoints with the +- rocker, regardless of the setting of the CDU STEER PT dial (note this is the WP INFO page, not the WAYPT page!). ========== When showing waypoints in the WAYPT and WP INFO pages, what is the intended effect of setting the STEER PT dial (and/or selecting a database via the UFC FUNC + FPLAN/MARK/MSN buttons)? Should the selection of waypoints that can be cycled with the CDU +- rocker be limited to the flight plan, markpoint or mission point databases, just like it's the case for cycling steerpoints with the STEER rocker (on the CDU, on the UFC, or DMS Fwd/Aft Short with HUD as SOI)? ========== Track from 2.9.1.48335 attached. A-10C II and A-10C appear to show identical behavior. A-10C_CDU_WP_Cycle_vs_FLT_PLN.trk
  5. I built myself a new mission with the player flight (2 A-10C II), an AWACS, 2 JTACs, 10 hostile BTRs as primary targets, and on top of that a hostile mortar team that harasses one of the JTACs. In several attempts, I couldn't get my radios to fail. In one flight, the JTAC unit I was working with got destroyed, but my radios were okay and I was able to continue with the other JTAC. I'm wondering if maybe there's something in that old mission you've been using that causes the issue?
  6. Das scheint auch echt Raketenwissenschaft zu sein. Ich hab schon mehrere Windows-PCs und Android-Smartphones gesehen, bei denen NTP eingerichtet war und die es offenkundig monatelang nicht genutzt haben und deshalb um mehrere Minuten falsch gingen. Bei der Qualität moderner Zeitgeber kommen da gerne mal 15 Minuten im Quartal zusammen, während meine analoge Armbanduhr im halben Jahr (zwischen den Zeitumstellungen) vielleicht eine Minute falsch geht.
  7. There's no lasting degradation when the alignment status jumps from RDY to anything else and then back to RDY (at least not that I'm aware of). So the only really important part is to make sure the weapon shows RDY right before coming into range, and remains ready until release. A good aggressive turn shortly before coming into range should do the trick. And if the weapon hates you and drops to "ALN RDY" just as you intend to release it, no big deal. Wiggle the wings until you get the status back to RDY and drop the bomb, it should work just fine that way thanks to the generous DLZ with JDAMs. Also, general note: Don't activate weapon stations by selecting them on the DSMS STAT page (sounds a little like that might be how you do it). It's always better to select a weapon profile by a) going to the DSMS PROF page and activating the profile from there or b) making the HUD SOI and cycling through all available profiles with DMS Right Short/DMS Left Short. Otherwise (when activating weapon stations) you'll get a manual profile, prefixed with "M/", and these manual profiles usually don't contain the changes you may have made during startup, like switching GBU-12 from CCIP to CCRP, autolase-settings, or ripple settings for dumb bombs and rockets and so on. I was just about to leave the forum and get back to work when I saw the new post in the A-10C subforum. Random chance.
  8. Ich meine diese Fehlercodes sind HTTP-Fehlercodes, und HTTP 500 ist "Internal Server Error"; in dem Fall wäre am Backend was gestört. Bei mir funktioniert es gerade, scheint also zumindest keine Großstörung zu sein. Am besten einfach nochmal probieren. Ein Tipp wäre noch, zu prüfen, dass dein PC die korrekte Uhrzeit eingestellt hat.
  9. Without watching the track: The single most common cause is when the weapon's INS goes out of whack. That can happen in as little as a few minutes of relatively straight and level flight. When it happens, you'll see the weapon status go from "RDY" to something like "ALN RDY". To correct the situation, you have to either turn by 90+ degrees or wiggle the wings. In the DCS A-10C, players should always make it a habit to plan for a significant heading change shortly before dropping JDAMs and other IAMs (CBU-103 and CBU-105 come to mind) on preplanned targets.
  10. That's a bit odd. Can you share a mission where that happens? There's an ancient issue in DCS where reloading weapons and then reloading DSMS in the mission will always fail unless you reload exactly what was loaded before. It sounds like your issue is a different one, where the loadout set in the Mission Editor already causes a problem on startup; I've never seen this behavior before. A possible cause might be limited munition stockpiles at the airport you're spawning. Maybe the DSMS gets told "there should be Mavericks" when there are none to be loaded?
  11. Yes, it's possible to refine a search, especially when you know exactly what you're looking for. But seriously, using an exact thread title as search term should put threads with that exact title on top of the search results without any need to tweak or tinker with the results. Even enclosing the search term with " quotes doesn't put the thread in question to the top of the search results. And now imagine users who don't know exactly what they're looking for; maybe they have a general question or even a specific one. They use a combination of search terms and search parameters, but each time they get literally 1000 results, none of which look particularly relevant - and now they're basically required to ask a new question, even though it may have been asked and answered numerous times already. In its current form, the forum search is almost useless.
  12. I haven't tested it lately, but I'm not aware of any changelog entry regarding FM homing. That, together with your test, looks like a pretty strong indicator that this feature is indeed not currently implemented.
  13. Excellent, thanks! In the track I saw exactly what you described. I took control after the radio problem appeared and was no longer able to send commands to my wingman (nor anyone else). The wingman also didn't react to commands like "Break left!", so it's not just a case of missing audio and/or subtitles. Radio commands just don't get sent any more. This is quite curious. I guess I'll have to dig a little deeper to find the common denominator for those cases where the problem occurs. If you happen to see this issue in any other mission, be sure to let us know! BTW, I believe the "Abort" call from the JTAC was indeed given because you were outside of the assigned attack cone while getting close to the target.
  14. Good point! And of course the situation on the ground could change. Maybe friendlies are closer to the target than expected, or civilians show up, or the target moves away from the DMPI, or something as silly as the JTAC messing up the laser code or the laser designator in case of ground-based laser-illumination. Some of these would also probably prompt the DCS JTAC to call an abort, like when the target becomes obstructed during run-in for a ground-based laser-illumination.
  15. I'll take a look at the track later (unless someone beats me to it). Regarding this question: Once an attack has been approved ("Cleared Hot"), the call "Abort, abort, abort!" is used when the attack must not be continued and has to be, well, aborted. I think the DCS JTAC might call "Abort, abort, abort" even before giving the "Cleared Hot" call, which wouldn't be great from a procedures point of view. But the DCS JTAC is very limited anyway. A typical reason for an abort-call by the DCS JTAC would be the wrong final attack heading; when you're given an attack cone like "Make your attack heading 150 to 210" your jet has to point somewhere between 150 and 210 degrees during the run-in, otherwise you're outside of the briefed parameters and the JTAC can call off the attack. (The phraseology "150 to 210" is really bad because of the phonetically ambiguous "to" which sounds just like "two"; there are much better options like "Make your final attack heading 180 +- 30 degrees" or "Make your final attack heading between 150 and 210", and nowadays I believe the standard phraseology is actually "Make your final attack heading between 150 clockwise 210" - but the DCS JTAC isn't up to date. )
  16. Nope, sorry. I know Baltic Dragon queries the state of cockpit switches for various campaign triggers, and he's probably not the only one to do so. But I don't know whether that uses classical ME triggers or scripting, and either way the campaign missions are all protected and you can't see the triggers anyway. I found this thread from 5 years ago which didn't find a solution: And I know I've asked for the option to affect cockpit switches via the SSE 6 years ago, which I believe hasn't happened. So maybe there's no scripting access to cockpit arguments yet (neither read nor affect), or if there is, I'm not aware of it.
  17. By far the best resource in this regard is the Simulator Scripting Engine documentation over on Hoggit World: https://wiki.hoggitworld.com/view/Simulator_Scripting_Engine_Documentation However, at a quick glance I only found a function trigger.misc.getZone() which doesn't have anything to do with detecting units in zone. I'm sure what you're looking for must be there, I just haven't done any scripting in DCS in ages and I can't provide any better pointers than the general hint regarding the SSE documentation. When you find a good solution, it would be cool if you can let us know how you solved it. (Or someone with actual knowledge comes by and can give you much more precise advice, like maybe @Grimes ).
  18. I basically love the current forum. It's fast, good looking, has useful features, and besides insisting on sending users to a 3rd party software on mobile, it's also fairly mobile friendly once that insistence has been actively denied. But am I the only one to find the search function to be really bad? I just searched for an old post of mine: "Tutorial: Introduction to Lua scripting". Using that as a search term doesn't even show me the only thread on the entire forum with this exact title on page 1 of the search results. If there's an obscure or hidden option on the forum backend to make search results more relevant, I would very much appreciate its activation. As it stands now, forum users will have a very hard time finding what they're looking for, even when using the best possible search terms and refining the search. The results are just very irrelevant, and I find using Google to search for the exact same terms, prefixed with "dcs", tends to get me pointed exactly at the one, two or maybe three relevant threads and/or posts in this very forum. The search function on the old forum was much better than what we have now and showed much more relevant results. If we could get a better search function, that might also lead to fewer questions that have been answered many times already, because users who do use the search function will then get more relevant results.
  19. Jesus Christ the search function on this forum is horrendous. Took me 5 minutes to find that thread, and I knew its title precisely. Anyway, I've not updated the tutorial in ages, but I hope it's what you're looking for and it should still be accurate.
  20. This is an odd problem indeed. In your track, I saw exactly what you described. After your check-in with the JTAC, the player stopped transmitting radio messages. I took control of the track and still was unable to transmit messages on either radio. I then ran the track again, took control immediately, and the radios worked just fine. At some point in the track I believe you switched the Frequency Selection Dial on the ARC-186 FM radio to the EMER FM position. On that position, you'd be transmitting and receiving on a dedicated guard frequency and no longer be able to talk to the JTAC. However, that should not stop transmissions from working at all, and should have 0 effect on the other radios. Given the hard to reproduce nature of this issue, if you can somehow isolate the one cause for this issue, that would go a long way to eventually getting it fixed by ED.
  21. Da müsste @Lino_Germany mal schauen.
  22. I've tried the Instant Action -> AH-64D -> Syria -> AH-64D Cold Start mission and for me the Autostart worked okay. Also ran the Autostart in Caucasus -> AH-64D Cold Start and again, no issues (in DCS 2.9.1.48111). I never noticed the "APU ON LIGHT MUST BE ON WITHIN 20 SEC" message that can be seen in your video. On top of that, I tried beginning the Autostart with a full up collective, but that was corrected as part of the sequence. I tried with a fully deflected cyclic, but that, too, didn't cause any issues and didn't prevent the APU from starting up okay. Does the issue occur for you every time you run the Autostart sequence? Can you try in another mission? You can try to repair DCS: Windows Start -> Eagle Dynamics -> Repair DCS World OpenBeta. If that doesn't do anything and the issue persists, you can try to rename your Saved Games\DCS.openbeta folder and try again with a minimum configuration. In any case you can later delete the newly created Saved Games\DCS.openbeta and rename your previous one back to get all your configs, keybinds and so on back. Let us know if any of this helps.
  23. It's very well hidden. C:\Users\{Your Windows User}\AppData\Local\Temp\DCS{Version}\LastMissionTrack.trk
×
×
  • Create New...