Jump to content


  • Posts

  • Joined

  • Last visited

Personal Information

  • Location

Recent Profile Visitors

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

  1. Yes, I'd hope this would have been obvious, that this is only experimental and for modding DCS, not doing anything else with ED's intellectual property against their permission. I've not done anything with this in over a year, because I got myself a job which had me away from home all week. Now I've moved closer to the job I'm planning to get back into DCS soon so hopefully I can find some time to poke this/see if any of the problems can be resolved. No promises though.
  2. Is there a way to prevent this sort of thing, or does it literally come down to micromanaging the wingman? Edit: Youtube link if the video embed isn't working:
  3. Tested on new OpenBeta Still misses. However - discovered that when deliberately releasing weapons *without* contour lock, the bomb appears to hit the target properly. Steps of test: Left target size minimum Waited until LA, released first weapon Increased target size until contour lock achieved Released second weapon The contour lock is still properly over the exact same point of the target, but the second bomb misses, and the first hits. So for some reason the calculations with contour lock are different, even though the target hit point is the same. This means that it's actually playable, as long as you ignore the contour lock capability. As a small aside, additionally I was playing with weapon release modes/release timing (to make dropping several automatic), and these settings don't appear to work for the KAB500-Kr. The manual seems to name the controls for "Free-fall" ordinance in one place, and just "Air to ground weapons" in another, so this might be deliberate and just not well documented.
  4. I recently reinstalled on a new computer and the way the game deals with held-down buttons seems to have changed - I'm wondering if there is a way to restore the old behaviour or, if it's an artifact of my installation somehow. Before (~1month) a button held down on the joystick - like the mode or aux switches on my X45 - was ignored after the initial press. This let me use them for e.g. switching airbrakes, or external views, or even landing gear up/down. This was especially convenient as having the switch in e.g. the "Landing gear up" position would be ignored if you loaded a new mission, until you changed it. Likewise, I could use the three-state switches for flaps - "up", "up/down" and "down" would work consistently. Now, it seems like every few seconds it "re-reads" the button as being hit - so if I start a mission with the switch in "gear up" state after a few seconds it'll start raising the landing gear until I jump to reset it. Similarly, it's hard to assign controls in the menu because every few seconds it thinks the button is re-pressed and jumps back to the entry I bound it to. Any suggestions? Edit to note: This is actually the *opposite* problem from the toggle switches sticky - https://forums.eagle.ru/showthread.php?t=89226 - that starts by claiming the problem that a button held down doesn't re-trigger, whereas I'm finding that it now does.
  5. It's not the wind. Attached is a custom mission that starts you heading south towards Kutaisi (the smaller). The command post is placed in the middle of the main runway, and comes within bomb range within about a minute. There is no wind. I've also attached a track - and include a link to a video of the live run below. I've done it this way so there is absolutely no time warping involved (considering in the command post strike mission it's about 20 minutes in, extra frustrating.) I release one bomb as soon as getting LA (1:40 on video), and the other about halfway down the "safe" area (1:56). The first bomb misses in the way that we've seen (and in the several times I have run the mission). The second actually does something different and goes way off-target - It could have been too late release, but still said it was in the LA safe zone. Neither hit. Also note that I get contour lock at some distance in this configuration - at 1:05. I've repeated this mission several times and have not got a single hit. Strike.miz Strike_Misses.trk
  6. Are you sure about that? Because the missile is mostly on track until that final turn right before hitting. Turning the opposite direction would probably lead to a hit...
  7. I've attached a screenshot of settings from the Command Post mission I've been using to consistently miss (assuming opening in the mission editor is accurate and it doesn't change over the mission). - the wind settings seem about half of you "hit" settings.
  8. Incidentally I just tested this with the latest update and it's still broken.
  9. After the latest update I've been getting a strange crash. The main menu opens, but anywhere from immediately to a couple of minutes later the audio dies, followed by a crash 10-20 seconds later. I've tried reinstalling from scratch, and removing the DCS.OpenBeta saved game folder. I've also run windows 'sfc /scannow' to verify my windows installation, and had no problems come up. Windows 10 build 1607, Intel i7-4870, Nvidia Geforce GTX1070. DCS The .crash file: # -------------- 20170205-061455 -------------- C:\Windows\SYSTEM32\AUDIOSES.DLL # C0000005 ACCESS_VIOLATION at 88B20739 00:00000000 00000000 00000000 0000:00000000 88B20739 1550FA60 0000:00000000 C:\Windows\SYSTEM32\AUDIOSES.DLL DllGetClassObject()+E569 88B33D5A 1550FAD0 0000:00000000 C:\Windows\SYSTEM32\AUDIOSES.DLL DllUnregisterServer()+F41A 88B33DCE 1550FB00 0000:00000000 C:\Windows\SYSTEM32\AUDIOSES.DLL DllUnregisterServer()+F48E A7998364 1550FB30 0000:00000000 C:\Windows\System32\KERNEL32.DLL BaseThreadInitThunk()+14 A7AA70D1 1550FB80 0000:00000000 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21 And the .log file is attached. dcs.log.txt
  10. The way I read it, they are requesting to be able to do this again - the ability having been removed at some point. If it used to be possible, it might still be possible by editing the mission files manually.
  11. That's okay, it's not trolling if it's not deliberate! New theory: The bomb inaccuracy is completely deliberate to simulate WW2-style bombing tech :)
  12. IIRC 2.0 tends to lag several months behind 1.5 in terms of engine updates, so it would make sense that it doesn't have the same issues. Edit: The altimeter bug is much more long-standing, but if you are flying with an altimeter set to sea-level then it won't affect you. This is compounded by the fact that some missions start with it set to local airfield pressure (as it should do) rather than always set to sea level
  13. Here's some more actual data for this: Tacview's graph of altitude and roll for the missile clearly showing the effect. Unfortunately because the timeframe is so small tacview doesn't have so much data for a smoother curve. You can also see the immediate projected path noticeably changing - I've marked where the missile actually hits on the image.
  14. Unfortunately this is also useless (in this mission) because of the altimeter bug - putting it into level flight mode causes an immediate dive down 400m or so, which is not helpful when trying to aim weapons.
  15. Really interesting - I hadn't noticed that final turn. What are the aerodynamics of the missiles like - is that last-second turn enough to make the difference between hitting and missing? Because that sounds suspiciously like a negative-value bug. Edit: Yes, it does signficantly change the path of the bomb - I plotted using tacview and you can see the estimated target position change:
  • Create New...