Title says it all, no idea why this is happening. Recent development, past week perhaps.

Does the bug-reporter pop up when this happens? What platform / hardware?

No bug reporter does not come up, just 'vendetta.rlb has crashed' or something like that.

Win 7 enterprise
amd fx-8370
16gb ram
GeForce GTX 970

I also found when I was quick enough to jump in sombody's trident, it did not crash. Even in turret.

I was then able to warp in without problem with another character on another account, without problems.

But the problem is still happening on your main account or character?

We may need to know exactly what character, to check the inventory. You can submit it via a support ticket if you don't want to reveal an alt publicly.

Actually, if you could open a support ticket and submit your character name, the time of the crash, and all of your client-side "log" files (errors.log, directx11.log, etc) from immediately after the crash (before re-running the game), that might also help.

There's probably some combination of inventory or something that's causing the issue.

Was on this character, on this account. It didn't happen last night at all. First time was in a Greyhound, with adv rails, and UC battery, no cargo. I forget what I had the second time. The third time I was in an Orion hornet with charge cannon, again no cargo. The secondary character I brought in was look ...busguns.

Unfortunatly I did not think to save the errors.log or dx11 log and I guess those are now useless as I have logged in since then. If the problem re occurs I will make sure to save them for you.

This happened to me at least twice a few days ago when there were other players in the sector. Didn't see anything interesting in the log files though

If you guys get to a "reproducible" point, please do save the logs, and then also try it without any plugins loaded? If it still crashes without plugins, go ahead and send us the logs.

It keeps really randomly happening here too, and it is not just Latos o12 but does seem to happen more when players are in a sector. Fresh install of VO, fresh OS too, I'd send the logs but they do not really say anything. Happened right now as I warped into Sedina B8.

I mean the last lines of directx11.log are

Device description: 'Radeon(TM) RX 460 Graphics'.
DedicatedVideoMemory = 2090360832
DedicatedSystemMemory = 0
SharedSystemMemory = 2204540928
Feature Level Supported = b000
Initializing Device Objects...m_pSwapChain->ResizeBuffers(1, 1920, 1080, 87, 0x00000002)
backBufferDesc = 1920x1080 87
Error: Failed to load vs[8] shader.
Error: Failed to load vs[9] shader.
Error: Failed to load vs[12] shader.
Error: Failed to load vs[13] shader.
success.
Restoring Device Objects...
success.
Reloading Textures...done.
m_pSwapChain->ResizeBuffers(1, 1920, 1080, 87, 0x00000002)
backBufferDesc = 1920x1080 87

and the last line of my errors.log is
[11/16/17 19:50:47] You are entering Sedina B-8

(nothing else in it but chat)

Fresh character too, no inventory to speak of, I could list it here on about 3 lines, so that is not it. There really is nothing in any of the logs to indicate why it crashed.

Windows 10 [Version 10.0.15063]
AMD Radeon RX460

If you really want my logs fine, but they really are empty.

[edit]

fired the reporter up manually so you should have my logs too

How do I fire up the reporter manually? I don't think I've ever done that.

Just run bugreport.exe after a crash, it should still send the last runtime logs as they are only destroyed on the next crash/exit.

I do not actually have anything to base this on apart from experience, but it seems to me this bug actually is related to running Dx11 and warping into a sector with a capship present (I can play all day long on Dx9, but its not as pretty). The crash only seems to happen to me when the above conditions are true and I am not 100% but I think it is somehow related to Tridents (as I crash, and things in the sector could have changed in the 60 seconds or so it takes me to get back in game) but practically every time I have crashed, when I get back into the sector a Trident is always present.

The other thing I have noticed, is when I exit the client clean, the last lines of my directx11.log are

success.
Restoring Device Objects...
success.
Reloading Textures...done.
m_pSwapChain->ResizeBuffers(1, 1920, 1080, 87, 0x00000002)
backBufferDesc = 1920x1080 87

but after a crash it seems the last lines are repeated a lot

Restoring Device Objects...
success.
Reloading Textures...done.
m_pSwapChain->ResizeBuffers(1, 1920, 1080, 87, 0x00000002)
backBufferDesc = 1920x1080 87
m_pSwapChain->ResizeBuffers(1, 1920, 1080, 87, 0x00000002)
backBufferDesc = 1920x1080 87
m_pSwapChain->ResizeBuffers(1, 1920, 1080, 87, 0x00000002)
backBufferDesc = 1920x1080 87
m_pSwapChain->ResizeBuffers(1, 1920, 1080, 87, 0x00000002)
backBufferDesc = 1920x1080 87

could be nothing more than being connected longer and the screen being reloaded periodically, but without a setting change why (I think you can ignore this but I'll leave it just in case, seems it is related to me alt+tabbing and not the crash)? Anyway, not saying any of this helps narrow it down, but just thought I would post about the Trident thing, because it really does always seem to happen when one is about when you warp into a sector. I do not crash every time the above conditions are true, but when I do crash they are.

[edit]

Seems if a Trident warps into the sector while I am present, I do not crash, and can then follow that Trident about without any following crashes. But if the first time I encounter a Trident during a session is during a warp, I crash. Hope this helps! Because after years of no crashes having several a day is getting annoying :)

I think my recent crashes coincide with Yoda's; dxlog has same thing, and it was in a sector where a trident was located. however, it doesnt always happen when jumping in - sometimes, ill have been in the sector with it for a while. sometimes. and it doesnt always happen when I jump in either.

anyways, when the crash happens, VO itself always just freezes for around 3-4 seconds before the window times out and it recognises a crash. no error reporter or debugger or whatever appears, just window's rather pointless "searching for a cause" thing that never pulls anything up.

Same thing happens to me, random sector and it doesn't seem like players being in the same sector has any impact. Like others above reports: the game freezes and you get the "Vendetta stopped working" note. Nothing in the error logs here either, tonight it happened 3 or 4 times.

Please post or send your error logs anyway. There may be a common pattern between you that the devs can use.

crashed 12/21/2017 10:15GMT (and a little before that); pewers in B8 and a trident.

DX11 log:
[12/21/17 17:11:28] Setting up Mode List
1024x768: format = 87, s1=0, s2=1, n=60004, d=1000
1152x864: format = 87, s1=0, s2=1, n=60000, d=1001
1176x664: format = 87, s1=1, s2=1, n=59940, d=1000
1280x720: format = 87, s1=0, s2=1, n=59940, d=1000
1280x768: format = 87, s1=0, s2=1, n=60000, d=1001
1280x800: format = 87, s1=0, s2=1, n=60000, d=1001
1280x960: format = 87, s1=1, s2=1, n=60000, d=1001
1280x1024: format = 87, s1=1, s2=1, n=60000, d=1001
1360x768: format = 87, s1=0, s2=1, n=60000, d=1001
1366x768: format = 87, s1=0, s2=1, n=60000, d=1001
1440x900: format = 87, s1=0, s2=1, n=60000, d=1001
1600x900: format = 87, s1=0, s2=1, n=60000, d=1001
1600x1024: format = 87, s1=1, s2=1, n=60000, d=1001
1680x1050: format = 87, s1=0, s2=1, n=60000, d=1001
1920x1080: format = 87, s1=0, s2=1, n=60000, d=1001
selectedAdapter = 00000000, driverType = 1
CreateDevice: hr = 0 (0x00000000)
Creating swapchain
hr = 0 (0x00000000)
Device description: 'NVIDIA GeForce GTX 750 Ti'.
VendorId: 0x000010de
DeviceId: 0x00001380
SubSysId: 0x31021462
Revision: 0x000000a2
[12/21/17 17:11:29] Device has 268435456 bytes total.
[12/21/17 17:11:29] D3D11 is valid.
[12/21/17 17:11:29] SetMode(14, "Vendetta");
unknown query
selectedAdapter = 00000000, driverType = 1
hr = 0 (0x00000000)
msaa 0 count = 0, hr = -2147467259 (0x80004005)
msaa 1 count = 1, hr = 0 (0x00000000)
msaa 2 count = 1, hr = 0 (0x00000000)
msaa 3 count = 0, hr = 0 (0x00000000)
msaa 4 count = 1, hr = 0 (0x00000000)
msaa 5 count = 0, hr = 0 (0x00000000)
msaa 6 count = 0, hr = 0 (0x00000000)
msaa 7 count = 0, hr = 0 (0x00000000)
msaa 8 count = 1, hr = 0 (0x00000000)
msaa 9 count = 0, hr = 0 (0x00000000)
msaa 10 count = 0, hr = 0 (0x00000000)
msaa 11 count = 0, hr = 0 (0x00000000)
msaa 12 count = 0, hr = 0 (0x00000000)
msaa 13 count = 0, hr = 0 (0x00000000)
msaa 14 count = 0, hr = 0 (0x00000000)
msaa 15 count = 0, hr = 0 (0x00000000)
msaa 16 count = 0, hr = 0 (0x00000000)
msaa 17 count = 0, hr = 0 (0x00000000)
msaa 18 count = 0, hr = 0 (0x00000000)
msaa 19 count = 0, hr = 0 (0x00000000)
msaa 20 count = 0, hr = 0 (0x00000000)
msaa 21 count = 0, hr = 0 (0x00000000)
msaa 22 count = 0, hr = 0 (0x00000000)
msaa 23 count = 0, hr = 0 (0x00000000)
msaa 24 count = 0, hr = 0 (0x00000000)
msaa 25 count = 0, hr = 0 (0x00000000)
msaa 26 count = 0, hr = 0 (0x00000000)
msaa 27 count = 0, hr = 0 (0x00000000)
msaa 28 count = 0, hr = 0 (0x00000000)
msaa 29 count = 0, hr = 0 (0x00000000)
msaa 30 count = 0, hr = 0 (0x00000000)
msaa 31 count = 0, hr = 0 (0x00000000)
Creating swapchain
hr = 0 (0x00000000)
m_pSwapChain->ResizeTarget hr = 0 (0x00000000)
m_pSwapChain->SetFullscreenState hr = 0 (0x00000000)
Device description: 'NVIDIA GeForce GTX 750 Ti'.
DedicatedVideoMemory = 2115698688
DedicatedSystemMemory = 0
SharedSystemMemory = 2179203072
Feature Level Supported = b000
Initializing Device Objects...m_pSwapChain->ResizeBuffers(1, 1920, 1080, 87, 0x00000002)
backBufferDesc = 1920x1080 87
Error: Failed to load vs[8] shader.
Error: Failed to load vs[9] shader.
Error: Failed to load vs[12] shader.
Error: Failed to load vs[13] shader.
success.
Restoring Device Objects...
success.
Reloading Textures...done.

I can stop the crashing by switching to DX9, in case this helps anyone else crashing.

but DX9 is less pretty and seems to take more processing power...

It does seem to happen more often when a trident is in sector. I have not bothered to keep track so far of the conditions that the crash happens under, so this is only anecdotal. I have also noticed that once it happens, it usually does not repeat with THAT PARTICULAR trident.

It kind feels like some type of loading based crash of some sort.

you've been lucky. I might crash two or three times, and after that it works fine. again, always on approach to a trident. I gotta see if I can record at what distances it occurs at; I dont think its ever occured if it was greater than 2km out.

As mentioned in the other thread, we've had zero luck reproducing this issue. Has anyone tried unloading plugins to see if that improves stability?

Happened again, 3 times in a row to me, no plugins, undocking from trident.