Origin ray fail over and over.

[Krougal]

Game started rubberbanding on me badly, so I restarted and framerate tanked. Over and over log shows:

2023-09-04T16:03:59 99.473 WRN 2379+3 Origin ray fail (1856.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.473 INF 2379+3 Origin Reposition (-1856.0, 32.0, -1392.0) to (-1840.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.476 WRN 2379+3 Origin ray fail (1840.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.476 INF 2379+3 Origin Reposition (-1840.0, 32.0, -1392.0) to (-1824.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.495 WRN 2380+1 Origin ray fail (1824.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.495 INF 2380+1 Origin Reposition (-1824.0, 32.0, -1392.0) to (-1808.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.498 WRN 2380+1 Origin ray fail (1808.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.498 INF 2380+1 Origin Reposition (-1808.0, 32.0, -1392.0) to (-1792.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.501 WRN 2380+1 Origin ray fail (1792.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.502 INF 2380+1 Origin Reposition (-1792.0, 32.0, -1392.0) to (-1776.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.505 WRN 2380+2 Origin ray fail (1776.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.505 INF 2380+2 Origin Reposition (-1776.0, 32.0, -1392.0) to (-1760.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.508 WRN 2380+2 Origin ray fail (1760.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.508 INF 2380+2 Origin Reposition (-1760.0, 32.0, -1392.0) to (-1744.0, 32.0, -1392.0)

 

Ok, I found a solution at least https://www.reddit.com/r/7daystodie/comments/14dn2kb/origin_ray_fail_a21/

Would be great if I could find my drone though, since it had items of value.

[Riamus]

On 9/4/2023 at 4:06 PM, Krougal said:

Game started rubberbanding on me badly, so I restarted and framerate tanked. Over and over log shows:

2023-09-04T16:03:59 99.473 WRN 2379+3 Origin ray fail (1856.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.473 INF 2379+3 Origin Reposition (-1856.0, 32.0, -1392.0) to (-1840.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.476 WRN 2379+3 Origin ray fail (1840.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.476 INF 2379+3 Origin Reposition (-1840.0, 32.0, -1392.0) to (-1824.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.495 WRN 2380+1 Origin ray fail (1824.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.495 INF 2380+1 Origin Reposition (-1824.0, 32.0, -1392.0) to (-1808.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.498 WRN 2380+1 Origin ray fail (1808.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.498 INF 2380+1 Origin Reposition (-1808.0, 32.0, -1392.0) to (-1792.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.501 WRN 2380+1 Origin ray fail (1792.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.502 INF 2380+1 Origin Reposition (-1792.0, 32.0, -1392.0) to (-1776.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.505 WRN 2380+2 Origin ray fail (1776.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.505 INF 2380+2 Origin Reposition (-1776.0, 32.0, -1392.0) to (-1760.0, 32.0, -1392.0)
2023-09-04T16:03:59 99.508 WRN 2380+2 Origin ray fail (1760.0, -278.0, 1392.0)
2023-09-04T16:03:59 99.508 INF 2380+2 Origin Reposition (-1760.0, 32.0, -1392.0) to (-1744.0, 32.0, -1392.0)

 

Ok, I found a solution at least https://www.reddit.com/r/7daystodie/comments/14dn2kb/origin_ray_fail_a21/

Would be great if I could find my drone though, since it had items of value.

Check your log at the beginning (or check console right after the game loads) to see coordinates for your drone.  If they are real coordinates, go there and you can get your drone at long as you didn't already clear ownership or delete the drone files.

 

If it is NaN for coordinates, then you aren't going to be able to get it back and can only use "jd clear" (no quotes) in console to clear ownership so you can place another.  It may also be necessary to delete the two drone files if that doesn't resolve the problem for you.

[Riamus]

A suggestion for the future is if you start getting that rubberband effect while driving with your drone out.  Stop and pick up your drone.  Wait to put your drone down until you're not going to be driving around for a while.  That usually is enough to prevent this from happening but you do need to stop right away.

[Soz]

Same, fourth time, ALWAYS drone related. It goes out of range, no idea why but having just started a new game after the REGION file corruption problem annihilated countless hours,  as soon as I got the blurry super low fps, I looked for my drone. Gone. Then the console - same as every time for over a month

 

Love the game [and the instant reply!!!] - experience tells me that this entire region of the map will do this forever, fly over it in a gyro and you go down like a DC10
 

=========================
Hundreds of this to start
=========================
Look rotation viewing vector is zero
Mesh '[NGUI] UIAtlas': abnormal mesh bounds - most likely it has some invalid vertices (+/-inifinity or NANs) due to errors exporting.
Mesh bounds min=(-nan(ind), -nan(ind), -nan(ind)), max=(-nan(ind), -nan(ind), -nan(ind)). Please make sure the mesh is exported without any errors.
Look rotation viewing vector is zero
Mesh '[NGUI] Font Material': abnormal mesh bounds - most likely it has some invalid vertices (+/-inifinity or NANs) due to errors exporting.
Mesh bounds min=(-nan(ind), -nan(ind), -nan(ind)), max=(-nan(ind), -nan(ind), -nan(ind)). Please make sure the mesh is exported without any errors.

====================================================================
Then mostly "Look rotation viewing vector is zero" + "Mesh... " etc
====================================================================
 
========================================================
And then this for the next 20,000 lines before quitting;
========================================================
2023-10-11T18:29:58 649.732 INF 40776+1 Origin Reposition (-512.0, 48.0, 448.0) to (-768.0, 64.0, 512.0)
2023-10-11T18:29:58 649.738 WRN 40776+1 Origin ray fail (768.0, -310.0, -512.0)
2023-10-11T18:29:58 649.739 INF 40776+1 Origin Reposition (-768.0, 64.0, 512.0) to (-752.0, 64.0, 512.0)
2023-10-11T18:29:58 649.744 WRN 40776+1 Origin ray fail (752.0, -310.0, -512.0)

 

Edited October 11, 2023 by Soz (see edit history)

[Jugginator]

We're on it