Codemonkeyx

Thanks @RedKite, we took him out today with a good chunk of the UK/EU contingent of EpicGamers! We'll let you know if it doesn't seem to start spawning normally now.

Apologies for posting about a bug/in-game issue in this forum as usual, but not sure where else to put it. FYI @Kyp / @RedKite My understanding is that the spawn times for raid triggers were increased over the holidays (though maybe they were just being respawned manually?) but ever since the Jan. 9th restart the controller trigger mob (Scavenger Drone ZX1) has not spawned. We've contacted Woody about this and before yesterday's restart he said it was showing something like 11 days until spawn. Yesterday after the restart he indicated it should be ~3 hours based on the number of seconds he said it had, but it never spawned. I've been watching it continuously since. My guess is that something was changed or broken with the spawn in the wake of the Christmas missions / Holiday spawn timer. Can a DEV look into this please? Thanks!

I've been compiling a list of common issues and their solutions on the Net-7 wiki here: https://net-7.org/wiki/index.php?title=Troubleshooting

Hi @Ciannicay, the launcher on the download page is the up to date one. The one on your computer is not. There may be some confusion here about what is really being updated when we talk about "resetting updates"; the launcher is primarily updating the game, which is installed separately. To answer your question, the direct link for the launcher is: https://downloads.net-7.org/Net-7_Install.exe but more than likely you already have this. The problem (and what @bespoke was getting at) is that the launcher on your computer is out of date, and perhaps even after "uninstalling" it and reinstalling, it's not updating, or you have multiple versions of it, etc. There are a lot of possible things that could be going wrong there if the client was originally installed on an older windows version, or you've managed to get multiple installed, etc. What @bespoke described was essentially a scorched earth approach of completely removing any old remnants of the launcher from your system. In your case I think that's a good idea. Do an uninstall from Windows Add/Remove Programs for "Net-7" or "Net-7 Launcher", anything like that, then manually remove this Net-7 folder completely: C:\Program Files (x86)\Net-7 then manually remove this LaunchNet7 folder completely (this is what @bespoke was referring to): %AppData%\Local\LaunchNet7 which will most likely be a path like: C:\Users\<user>\AppData\Local\LaunchNet7 which contains deeply nested XML config files like user.config. Then go into your start menu and see if any "Net-7 Entertainment" folder remains, and if so, look at the properties of those shortcuts and remove all those locations as well. We want to completely nuke everything from orbit, it's the only way to be sure. There should be no traces of Net-7, LaunchNet7, "Net-7 Launcher" or "Net-7 Entertainment" left on your computer. THEN install the launcher from the above link.

EDIT: I just re-read this and realized this is the config directory you deleted, not the program directory. This makes sense now.

Not the same symptom, but try the steps here and see if resetting updates helps: https://net7wiki.bmsite.net/index.php?title=Troubleshooting#MISSING_ASSET_Please_Report_Me

Can you be more specific about what you did here? It is far more likely that there was a problem with your old install which persisted through the "deleted" and reinstall process than that your old install and the files from net-7.org are damaged in the exact same way and others aren't having this same issue. I would try going into the launcher and using the option "Reset Updates": Then use the option "Check For Updates ...": This should go through several cycles of updating and when complete you should see "LaunchNet7 v2.2.0" in the title bar and "Current Version: 545" in the lower right corner, just as above. Give that a shot and see if it helps. More than likely you've got a corrupt file in your install. If the above didn't work you may have to completely remove your install directory above after uninstalling, but without some additional surgery you will lose all your settings, shortcut bars, etc.

I don't have any technical details or history but I assume it's related to packet ordering between the net7proxy and the server and experience has shown that with modern network stacks it definitely needs to be enabled.

Full Screen shouldn't have anything to do with it, make sure all of these are checked on the launcher: I went ahead and posted this on the wiki too (along with some other troubleshooting tips and tricks): https://net7wiki.bmsite.net/index.php?title=Troubleshooting#Frequent_Disconnects_While_Gating_or_Docking

Thanks @Zerodragoon, I'm running in a very different environment on a very high end machine and fiber internet so I'm not surprised things needed some tweaking. I'd definitely accept a PR. That script is primarily based on @Doctor's but updated to AHK2 and made generic so it should work at any resolution, so credit where credit is due!

To be honest I doubt you need a discrete graphics card at all to run EnB. Any CPU with built-in graphics should handle the game just fine. Fortnite is something else entirely.

Sure, what are your characters' names? I'll keep an eye out for you, or hit me or one of the other EpicGamers crew up if you see one of us online.

I can only speak from the perspective of a TE but they get the same levels of Repair Equipment so I think it's valid. I kept Combat Repair Equipment for a long time before I had extra points to spend and it worked just fine for me. This is especially true if you're solo or only concerned about repairing the equipment on the PW doing the hull tanking. You can still repair the equipment of others with Level 5 but it requires targeting each one and repairing individually. While the max rank is about 4x faster, it doesn't much matter because after the short cast time the actual repair takes place in the background and you can go about your business while it continues (e.g. casting other buffs or attacks) and we're talking about seconds here so there aren't a lot of scenarios where the time difference between the two is going to be of major consequence, especially if you repair early and often. When pinched for points losing Area Equipment Repair was definitely one of the first places I would harvest for spare points so I think you'll be fine without it.

It's dead Jim.

Just randomly came across this thread... does anyone still have a copy of the "Earth and Beyond Music Patch 2017.zip"? The dropbox link at the top of this post is dead, though oddly the one on the original thread (a few posts down) still works but it only has the 20 tracks.

For the fuzzy textures issue: Check the Windows registry settings (Win+R, regedit) under the key (these are what E&Bconfig updates): HKEY_LOCAL_MACHINE\Software\Westwood Studios\Earth and Beyond\Render specifically: RenderDeviceTextureDepth (recommend hex 0x20 or decimal 32) TextureFilter (recommend hex 0x2 which is also decimal 2) TextureReduction (recommend hex 0x0 which is also decimal 0) Once in-game try going to: Options -> Graphics uncheck "Use recommended values" and move all the sliders to the maximum "High" (all the way to the right) except "Gamma Control" (which you can set as desired).

That's a crazy complicated set of interfaces you've got there. 😅 I'm guessing this is a laptop, and used for work as well? VPN's, VM's, multiple wi-fi interfaces, ethernet... I'm not too surprised the launcher and net7proxy aren't doing the right thing in light of all that. However, the IP in the launcher is correct compared to the wireshark output when you were using "/LADDRESS:0". It's worth pointing out that this game famously does not work well on wi-fi, though it doesn't typically not work at all in the manner you're seeing... it just has lots of problems with rubberbanding, disconnects, etc. If you have the ability to hook up via ethernet you might give that a shot.

One thing you could try is change "/LADDRESS:0" in the manual command to "/LADDRESS:192.168.50.229" and see what happens. Another thing to look at from this point is the UDP traffic. Initially the login handshake is TCP and that part seems to be working now, then during the galaxy map screen things switch over to UDP and that is where, e.g. people on T-Mobile Home Internet get screwed (you can find threads if you search T-Mobile) because T-Mobile completely blocks UDP. I would not be surprised to see UDP packets going out with none coming back if there is a problem with UDP through your router and/or ISP. Back to the launcher problem, is the source IP address it showed in your wireshark data (192.168.50.229) the same one shown on the launcher under "Local Address"? What does: ipconfig /a show in a CMD prompt? I still have a suspicion that you may have multiple interfaces and that may somehow be throwing off the launcher=>net7proxy hand-off.

FWIW my guess is that the website is actually showing things correctly because I did in fact have those missions in my log. The game/client seems to be the outlier in that it was not showing the very last mission in each of these cases.

Ever since the server reboot and the activation of the Christmas missions (and perhaps more importantly the resetting of last years missions) I've been seeing a bug where there is an off-by-one error for my characters' mission logs. I first noticed it on CodeTT who was inexplicably unable to accept a mission despite only having 11 missions in their mission log. I checked the website and was very surprised to find it showed 12 missions in my Current Missions list, one of which was not showing in game ("Monitoring Antares"; though I'm not sure it matters what it was... the main thing is this was the last mission in their log, i.e. bottom of the list, what would have been #12). I then checked my other characters to see if any others were affected and found that CodePP had the same issue, but with "InfinitiCorp: Profit above all", again, not sure the mission is important, but it was the last one in the mission log. I've since completed both of the above missions. I was still able to complete them despite the objectives not updating and them not showing up in the logs, /fmu not helping, logging in and out not helping, etc. but I completed them and got the rewards as expected and their mission logs now seem normal. Then I started on the Christmas missions and almost immediately found that "Dickens - Bah Humbug!" disappeared from the logs of both CodeJE and CodeTS; once again it was the last mission in their logs, the website shows it, but I can't see it in-game. In-game they show 7 (CodeJE) and 6 (CodeTS) missions in their logs, but on the website they show 8 (CodeJE) and 7 (CodeTS), with "Dickens - Bah Humbug!" as the last mission in both cases and also the one not showing in-game. The above two are still in this state. Any idea what is causing this? Once I get through this on each character will it fix itself? I was talking to @Woodstock HGM in-game during all this, so perhaps he has something else to add. Per his advice I did start reducing the number of missions in each of my characters mission logs (they were mostly in the 10-11 range) but even after getting down to 7/8-ish as above, the problems persist.

As in, it didn't accept your username/password? Or? When was the last time you logged into the game? Can you login to net-7.org with your forum account and reset your game account passwords under Account -> Avatar settings, then try logging in with one of those? The key point here is that the forum/net-7 account is different from the game accounts with separate passwords.

Hey @Kyp, I don't know if you had a chance to look into this yesterday afternoon, but just a heads up that the Christmas NPC's still aren't up. FWIW Woody mentioned that "the switch had been flipped" and it was just a restart that was required, but I'm guessing that probably came from you anyway. Based on some of the Discord chatter it just seems like it may have been flipped and then un-flipped somehow following the maintenance which is why I tagged you here originally.

That is exactly as expected; this is what the net7proxy.exe is for. You keep mentioning "Main.exe" and I have no idea where that would be coming from; there is no "Main.exe" anywhere within the game or Net-7 installs. Did you try running net7proxy.exe manually as I described previously? What happened? cd "C:\Program Files (x86)\Net-7\bin" net7proxy.exe /LADDRESS:0 /ADDRESS:216.219.87.147 /CLIENT:"C:\Program Files (x86)\EA GAMES\Earth & Beyond\release\client.exe" /DML /EXREORDER /POPT

You had a couple contradictory statements in your original message: But it sounds like net7proxy.exe runs... which is another executable. Can you see what the command-line that net7proxy.exe is being run with is in the task manager, etc. (it has been a very long time since I've been on a Windows machine so I can't recall how to see this for a running process off the top of my head, surely powershell has some way to do it)? For example, I launch the net7proxy.exe directly without the launcher using a command-line something like (this is not exactly what I use as I'm playing on Linux and I've omitted some implementation details of the bash script this command is in, but effectively this is it): net7proxy.exe /LADDRESS:0 /ADDRESS:216.219.87.147 /CLIENT:"C:\Program Files (x86)\EA GAMES\Earth & Beyond\release\client.exe" /DML /EXREORDER /POPT This command needs to be run from the CWD (current working directory) of the launcher install bin directory which is by default something like: "C:\Program Files (x86)\Net-7\bin" as net7proxy.exe seems to look for other files it needs in the CWD. This then requires that the /CLIENT param is an absolute path, or at least an accurate relative one (which is what I was worried about before, I've never tried relative and just use the full path). I would try opening an admin command prompt, changing to the above directory, and try running the above command to see if that works just to try and narrow things down. Notably I've always run with the /LADDRESS as 0 and changing that to something else doesn't seem to work (in fact I get behavior a lot like you're describing). Based on your launcher I'm guessing your local IP (192.168.x.x) is being specified there (no need to hide that IP in your screenshots as it's a non-routable address local to your own network that is useless to anyone else, most likely assigned via DHCP on your router, e.g. mine is 192.168.1.219). If you've got that address wrong or something odd is going on with NAT on your network then specifying it may cause problems, likewise if you have multiple network connections (e.g. wi-fi and ethernet, or a VPN) and that is a different interface than the one net7proxy.exe tries to use, that could be a problem, etc. Note that /ADDRESS is the current IP of sunrise.net-7.org (216.219.87.147). Anyway, hopefully something in there gives you some more ideas or things to try, or perhaps narrows down the problem. Good luck!