Jump to content

Number Six

Homecoming Team
  • Content Count

    301
  • Joined

  • Last visited

Community Reputation

694 Excellent

About Number Six

  1. @Postalityjr Yes. Many of the developers and GMs have been using the new launcher for 1-2 months now; we were just waiting on the code signing certificate to start the public beta. I never run tequila anymore.
  2. Yes, it will. I edited it right after posting to mention that, but in case you didn't see it in the scroll of new messages.
  3. The existing macros will work if you're standing next to a base portal (including the new summonable mini-portals), or have the window open after using the base transporter power. Or if you're in a base already, for quick base-to-base movement.
  4. Bad news then, Page 6 is not going to beta today. 😉
  5. Long-standing annoyance: Teleport powers have never worked inside that ring. It's because the geometry for the force field only has triangles facing outward instead of two layers like everything else, so the teleport checks find backfacing polygons and think that you're trying to teleport out of bounds. Not really feasible to fix short of a new model for the whole ball. Could really use one anyway; it's way too low detail to be running around inside and there are seam mismatches everywhere.
  6. It is. The launcher core already builds on Linux and I was testing the CLI at one point. In theory the UI should also be portable since IUP supports GTK, though it hasn't been tried yet and there may be some issues to sort out due to slight differences between the platforms. There isn't a whole lot of reason to do so though. The design intent is that the launcher should be closely tied to the architecture of the game, as it makes things like launching with the correct parameters and working directory much easier. A Linux native launcher might be useful for updating, but couldn't actually launch the game since it can't install or use wine on whatever distribution you happen to be running, and there really isn't much benefit to be gained by dealing with the headache of that extra complexity. If and when there's a native Linux game client, then would be the time for the native build of the launcher to match it.
  7. The launcher is static and doesn’t draw any frames unless you’re interacting with it in some way and it needs to repaint. It uses Direct2D by default so if the GPU is sending less frames to the monitor it may be a video driver thing, possibly doing vsync when it does update. What if you also have something else running that is updating the screen more frequently? You could try modifying the shortcut to start the launcher with a -nowdl flag. That will fall back to GDI rendering like any standard Windows application, though it may be slightly less responsive.
  8. From the log it looks like something is going wrong with the UI code and causing it not to run. The launcher core is actually starting to download files, but you can’t see what it’s doing. If you kill the process and run the launcher again (not the install but the one under bin/win64), what happens?
  9. Hit cancel and look for a launcher.log file under logs in the location where you installed it. It sounds like it's having trouble downloading the launcher package with the latest version of itself.
  10. I see it, thanks! It may take a little bit to dig into since it wasn't the obvious case, but hopefully that will have the information I need to determine the actual root cause.
  11. Not in this build. Whatever is causing that one is smashing the stack badly enough that the crash reporter can't run, making it impossible to get a memory dump or even a stacktrace. The windows event logs confirm that it's a crash, however since it's happening inside ntdll it doesn't give me anything to go on. I suspect some sort of graphics-related overflow in the rendering engine from so many objects appearing at once, but don't have solid enough information to prove that.
  12. Unfortunately I haven't been able to reproduce it under controlled circumstances -- the ones that I could reproduce were just fixed but it seems to still be happening for some people -- and the clues in the memory dump don't seem to point to anything useful. The next time it happens, can you go to the advanced options and select "Full Memory Dump"? The upload will be quite large, so please only do this once, and also indicate in the notes that it's the one with the fulldump so that I can find it easier.
  13. Please try it now on the latest update. 26.5.2778 if using the new launcher, or... restart Tequila and hope for the best since I don't think it shows the version number anywhere.
  14. Yep, got it. Looks like it's just randomly dying after checking the packages for updates; no indication of problems up to that point. Do you have a 'crash' subdirectory, and if so can you send me the files inside?
  15. Can you grab C:\Homecoming\logs\launcher\launcher.log and DM it to me so I can take a look?
×
×
  • Create New...