That would be path around obstacles (stations and the like) right? Or would it mean you pimped the tsp solution, meaning "optimize route" doesn't freeze the client on waypointy routes?

Singularity - EVE-FEATURE-FSD-UNIVERSE - 8.42.710206

testing Archon with 3 x Done Link Augmentor II (DLA II) modules plus 2 x Omnidirectional Tracking Link II (OTL II), 2 x Drone Damage Amplifier II and 2 x Drone Navigation Computer II modules fitted. Show info from market for Warden II shows Optimal Range 60km; Tracking 0.012 rad/sec; Damage Modifier 1.44x.
After ship launched with active OTL II mods, Show Info for Warden II in drone bay displays Optimal Range 75km, Tracking unchanged and Damage Modifier 5.3131.
When drones deployed with active OTL II mods, Show Info displays Optimal Range 60km, Tracking 0.012, Damage Modifier 1.44x.
Optimal and Damage Modifier is updated only when drone located in drone bay. Tracking is not updated even though 2 x OTL II mods are active or active with Tracking Speed scripts.
Other drones also do not update Optimal, Tracking and Damage Modifier details.

Unable to bug report - error message displayed when submitting bug report "Unexpected error from the bugs service". Bug report saved to disk within game - will attempt to send at later time/date.

Bug Report

Open the assets dialog and select a system, right click and choose set destination. A message appears "Can't set waypoint - must be planet, constellation, or region."

Observed on two accounts in different solar system but both system were null sec.

If I understand the data migration goal, you are taking data from database to some json (or any format, does not matter) which will be included into your source control system.

So... i'm now wondering, since you say "it will be re-injected with updates into the database", will the static data change ? Will we be still able to just use those data as we used to ? Or will we have to change all queries ?

You also enumerate some data that are concerned by this migration, but is this the exhaustive list ?

Bug Report

Open the assets dialog and select a system, right click and choose set destination. A message appears "Can't set waypoint - must be planet, constellation, or region."

Observed on two accounts in different solar system but both system were null sec.

This big change will have an impact on the 3rd party devs, due to some static data export (SDE) changes.
The new static data export for the universe data will be exported to an sqlite file.
The structure of the tables exported to this file will remain the same.

Yup 4-5 years ago they revised rules to prohibit travelling more than 20AU outside orbit of outer planets. Don't remember how far off solar plane you can get though maybe its a sphere set by that outer planet orbital radius + 20AU."

I am not able to download the mac patch. I keep getting exception reports.

Help?

Can you provide us with the exceptions? Pastebin is good for dumping the EVE Launcher logs to.

millions of third party devs cried out in terror, and were suddenly silenced.


After having perfected GARPA's import of the MSSQL SDE over the years, I can only imagine what havoc CCP switching to a whole new format (and then eventually adding stargates to a dynamic galaxy or whatever) will wreak on us guys trying to provide navigation and economic tools. Years ago there was talk of #devfleet and a whole new developer program -- never materialized. CCP is making big changes without supporting the devs. Hanging out on IRC with a few people doesn't count. After 10 years, I'm sure you're all keenly aware how much the game's continued success actually relies on third party devs. How about getting a program in place with a CSM-like NDA where devs can preview changes and actually get their tools prepped out BEFORE the major changes drop on sisi (or on TQ, because that's when SDEs are released). We have years of work-hours invested in certain things. I know Wollari was asking about this type of possibility at Fanfest 2013 (because I was standing right next to him at a pubcrawl when he brought it up).

However if you don't have time to change your tools (if you need to make some big changes) there is no rush on doing that, because the actual data in the tables will not have changed between this SDE and the previous SDE .

I think you aren't taking into account quite a key point in CCP Nobody's post, namely:
Because at this time nothing will be changing in the information provided in the SDE, it was not a priority for us to bring third party developers on board with the change at an earlier date. Instead we've been focused on ensuring this change is as bug free as possible, which is why we are only recently finalizing the details of the SDE.

It will aloow CCP to easier edit Universe Data, such as adding star systems or altering/adding positions of existing star systems items such as stations, stargates and even planets.

I imagine this is the first step towards a more dynamic Universe where things can change more often and esier than they do now.

You do not recall correctly, this was never possible. The XYZ-coordinates were only displayed in the 'Create bookmark' and 'Edit bookmark' dialogues but you could not in any way edit the coordinates.

So to ask a dumb question, will this mean that this testing involves mirroring TQ? Or will it be unmirrored until further notice?

Can you provide us with the exceptions? Pastebin is good for dumping the EVE Launcher logs to.

Wish I could. It outputs a large text file that I can not copy/paste. That said, I'm trying to re-create the incident again so at the very least I can screen shot the section of the code that it scrolls to, and it seems to be working fine now....

All that smells to me like a long term plan to add more systems in faster interactions... ;)

Greetings Capsuleers!

...

The universe data contains, for example: the positions for all systems, planets, gates, asteroid belts and the asteroids in these belts.

...

how about stations? I'm not seeing, e.g,

QYZM-W V - Carebear Rehab Center ( Minmatar Service Outpost )

Bug reporting it will put the issue in front of a dev faster.