Build: 3044 Mode: Survival Mode: Peer2Peer Coop SERVER NAME: Local SEED-ID: Any, tested with several ones If applicable: MODIFIED PLAYFIELDS: Yes and No (tested with non modified as well) Reproducibility: Currently always Severity: Major Type: Warp Summary: Warp target not locked Description: No matter what target i lock onto in the galaxy map, it ends up showing 185 LY warp distance, and even though i get the Orange warp target marker, as soon as i hit K , it just says no warp target locked. Steps to Reproduce: Start game, spawn ship, try to warp
Your warp drive allows jump to range of 30LY maximum. If you edit the proper configuration file you can extend that range. PS Your title is very misleading.
I select any warp target, including one only 6.1 LY away, and as soon as its selected it shows 187 + LY away, and it doesnt say its to far away, it says NO WARP TARGET SELECTED. NO target can be warped to, except within sector. So title is very accurate
I asked a friend of mine to test now as well. When he had version 3042 he could warp fine on a newly generated Default Multiplayer scenario. Then he updated to version 3044, and started fresh same game with all same settings, and he got same problems with warp
He seems to be aware of the jumpable distance. and.. No, the title is fitting. SP/Survival Vanilla Just tried it too. Even if you pick a Star in 10LY distance the Distance to jump is displayed as 185 LY
I have now let a third friend do same test, and same issue after updating experimental. So it seems we have something broken in the release
I have tried in SP, Co-op & on my own server all using the Default MP scenario I cannot find a single star that triggers the distance like you show. Please attach the save game there must be a missing step somewhere that triggers this.
@Pantera do a fresh install and see what happens, and check your build number. 3044 is the one we have issue with.
He does not have to do it - he is on the same Build as me. And I can't either perform the jump You can see his build number on the last picture
Ok it happens when you click on the "Lock target" button but doesn't happen when placing your cursor over a warp target & using CTRL-Left to lock on. Will check.
Same Problem here. https://steamuserimages-a.akamaihd....292/5BBB5B4B4BE9B8DCAA3AF8A10568806F2B94CDC9/ https://steamuserimages-a.akamaihd....687/83B3DBC1A7290468F833858146A363932A13CDD6/
Build: Experimental 1.0 - 3044 Mode: Survival Mode: Singleplayer SERVER NAME: N/A SEED-ID: 52325 If applicable: MODIFIED PLAYFIELDS: No Reproducibility: Always Severity: Major Type: Warp Summary: Cannot System Warp, LY Distance too great Description: Started Experimental 1.0 - 3044 today, can't warp between systems. Lock Target button generates some incredibly large LY distance ( > 100) no matter what system I select. I can locally warp within the solar system still. I noticed this first on my 12.3 save, where warping to any system gave me a 199 LY distance for every system in the galaxy map. Created a 1.0 - 3044 new survival game (the seed # attached), spawned in a CV and same issue albeit with only a 185 LY distance. Again, can still locally warp in the solar system. If you're on the galaxy map, and instead create a waypoint to any system, what seems to be the actual LY distance is displayed. Once setting this waypoint, I can locate it by twisting my ship around in space, and it's in a completely different location than the "Locked Target" waypoint. My amateur guess is either the game is hard-locking onto some point far away in the galaxy map every time (which is why the distance shifts slightly between new games), or the LY calculation is busted and returning some pseudo-random LY distance. Steps to Reproduce: > Open Galaxy Map > Select any system not the home system > Click "Lock Target" !!! Screenshots, Crash Logs, any other Relevant Information or Download links:
Same here. In the distance line it shows the correct distance: 27,6 LY. But below you can see the distance that will get locked: 185,6 LY
