Some testing done by one of the guys in our squad suggests it's any unit that uses purely visual acquisition seem to be affected by no-render.
Things like Ural AAA, but also aircraft set to "No radar use" were affected.
I ran into a similar issue tonight.
I saw that it was trying to connect to some (but not all!) servers via IPv6 rather than IPv4 and hanging at the loading screen indefinitely.
I had to disable the IPv6 protocol on my Network card and reboot before it would connect to those servers.
Their certificate has expired:
updates.digitalcombatsimulator.com uses an invalid security certificate. The certificate expired on Saturday, 16 December 2017, 10:59 AM. The current time is Saturday, 16 December 2017, 11:16 AM.
I had a similar issue recently. Turned out to be a CPU thermal issues from an incorrectly seated heat-sink and fan.
I could play every other game in my catalogue all day long. It was only DCS 1.5 and 2 and only in certain aircraft and at certain times of the day that would cause the system to power off/restart without warning.
It's easy enough to rule out. Download and run a CPU and GPU temp application and you can monitor for thermal issues.
Hi.
I've found a reproducible game crash when embarking troops with the Uh-1h.
Steps to reproduce:
1. Load troops
2. Tell troops to pop smoke
3. Unload troops
4. Request troops to pop smoke again.
Seems the second time you request them to identify their position with smoke causes the game to crash.
Logs, dumps and sample mission attached. uh1h.miz DCS.openbeta-20151011-041113.crash.txt dcs.log.txt DCS.openbeta-Crash-20151011-041113.zip
Use TMS down short with the maverick seeker as SOI for an instantanious ground stabilization.
It will only work until the next aircraft input, so it's best if you have the aircraft on autopilot when you do it. It makes slewing the maverick seeker much easier/accurate.