Jump to content

Weidlich

Members
  • Posts

    51
  • Joined

  • Last visited

About Weidlich

  • Birthday 02/22/1985
  1. When you load a mission where the default loadout contains a JDAM and you select the weapon to "on" on the ground you will not see any timer A09,... As soon as you are airborne the weapon is RDY and you get precise hits. Any subsequent rearming works as intended. You'll see the timer on the ground and it takes the normal time to align. It's just still bugged that you need to keep the SMS page open with the jdam selected to continue aligning. Only tested in singleplayer as I am not aware of any MP server with a default JDAM loadout when you select a slot. jdam timer1.trk F16 JDAM bunker Mariana.miz dcs.log
  2. there you go. As short as possible. Airborne the second time there is just no option to CZ (TGP removed during rearming) or any hotas command for it. dcs.log F16 ccrp error.trk
  3. It's a problem due to missing system integration I think. Happens on every map, single and multiplayer. It's easy to reproduce: Start a mission with a stored waypoint and a TGP attached and any weapon which can be dropped in CCRP mode. Go to AG mode, make TGP SOI on a selected waypoint and slew the cursor around (apply an offset like you always do when you search for targets). Now don't reset the cursor (CZ), simply switch to NAV mode and land. The waypoint is indicated correct with the large diamond (and without any offset). Land and rearm but remove the TGP. Then depart and switch to AG mode again. The target box still has the offset you previously applied without any way to reset the cursor. result: AG mode for CCRP attacks unusable. You need to land and load a TGP, then you can reset it.
  4. It's a problem due to missing system integration I think. It's easy to reproduce: Start a mission with a stored waypoint and a TGP attached. Go to AG mode, make TGP SOI on a selected waypoint and slew the cursor around (apply an offset like you always do when you search for targets). Now don't reset the cursor, simply switch to AA oder NAV mode and land. The waypoint is indicated correct with the large diamond (and without any offset). Land and rearm but remove the TGP. Then depart and go to AG mode again. The target box still has the offset you previously applied without any way to reset the cursor. result: AG mode for CCRP attacks unusable. You need to land and load a TGP, then you can reset it.
  5. Trackfile or log not required, easy to reproduce. You start a mission with jdams. first problem : when you power them on they only align when the sms page with the jdam menu is visible. When you select a different weapon the alignment timer stops where you left it. You need to cycle back to the jdam weapon to continue alignment. second bug: when you drop the jdams, then land and rearm with the same jdams again the pylons stay aligned. They should be unaligned. (hornet had the same bug for a very long time last year). Hope you can reproduce.
  6. Amazing tool! F16: Do you have plans to add the elevation to the waypoints? (As well it would be handy to have a button to kind of delete all waypoints be setting them to 0000000.) <- just tested this, it doesnt work, it really creates a wpt. Kind regards
  7. Just got a 4k screen so I put the Scale GUI to value 2. This makes it look like it was before on my 1080p screen. However whereever you put the mouse on the F10 map the coordinates are wrong. You can crosscheck it by putting a unit on the map, select the unit so you see the coords and then put the mouse over it. The mouse coords are just completely off. When you select the range/distance function you only need to move the mouse around half or a quarter of what you need. Pretty easy to spot the error if you try it. (there is a second 1080p screen connected to the PC as a secondary screen but not used for DCS at all) dcs.log
  8. dcs.log It happens quite often (around 1 out of 20times using the switch). I fly on the Buddyspike PG Modern server. Using the dogflight switch on my hotas the game just freezes (I don't even get the DCS error message). Anything you can see in the log? Crash happened at the very end of the log, after time 05:03.
  9. Hi! First time I ever used the Viggen. While doing the cold start procedure training mission right after I entered the 9099 code and pressed enter for the data cardrige DCS crashed. Anything you can see in the log file? It did not happen the second time. Kind regards Andre dcs.log-20201121-022711.zip dcs.log
  10. no overclock (as written in first post)
  11. No mods, pure dcs without anything added.
  12. Buddyspike Persian gulf modern server, we departed the carrier with 2 hornets, I was number 2 (departed within 20sec from each other). Just being airborne my game crashed. Log attached. Track file 11MB: https://1drv.ms/u/s!Aqt9J1OkiSdKgv8yFiR_AStHqAMyTw?e=caayaM Anything you can see? (And please do not ask about overclocking) My game ran without a crash for weeks so far. dcs.log-20200718-023502.zip
  13. Your reason for the crash is the same as I had this morning. It's the nvwgf2umx.dll. My rig is completely different and I reported the same this morning. My post #5 contains the crash log with the same error: https://forums.eagle.ru/showthread.php?p=4358862#post4358862 It's an nvidia module. We both have the new 446.14 installed which was released 2 days ago, I have a 1080TI. So either the new driver causes the crash or the new DCS update causes a conflict. Do you have the GeForce experience installed and/or running? I guess you flew the P51? I was in the F18.
  14. again access violation (a different one). This time I was doing basically nothing. Sitting in the F18 in the climb and waiting to arrive at target. The log attached is with the full debug you were asking for. Searching Google for the nvwgf2umx.dll, it only relates crashes to the GeForce Experience. If it matters, yes it was running (running it for years without issues so far). This guy has the same crash as me today (same nvwgf2umx.dll error): https://forums.eagle.ru/showthread.php?t=275700 We both have the new 446.14 installed which was released 2 days ago, he has a 1080, I have a 1080TI. So either the new driver causes the crash or the new DCS update causes a conflict. dcs.log-20200530-014231.zip
×
×
  • Create New...