Quaksen

If they were in the modpack before, and are now gone, they're most likely outdated, and Aslain is waiting for an update before he can re-add them.

If you're having trouble finding it, on Windows 10, simply open the start menu, and type in "magnifier"

Windows 10 has a magnifier you could use, for cases like that. (if you're on Windows 10.. I don't know about the other Windows versions, but they probably have similar too) Not sure about the installer itself, how troublesome or not it would be do fix it so you could enlarge it like you describe

As a sidenote, you may wanna take a look at this, since I see the tier marks overlapping your contour icons : As for the Russian text in crosshairs, it's something that everyone has to live with, for the time being.. Don't know about the errors in reload time though.

Long story short: It's basically a zip file, without compression, and the contents is the old swf/pyc files.

Errr, the old aim? Not sure what you're talking about there... There's two versions: The old illegal version, that would snap to a target, without highlighting it. You're not getting that back. And the new version, that'll lock to a target, only if you have it highlighted, or depending on your selection, right click and then later on highlight a target.

See the issue in Aslain's picture, under the red circle. It's a WG issue.

Maybe someone has an idea - but it requires them to be using Xpadder as well though

Hehe Happy tanking

(If only people would read the FAQ )

Your first set of logs, was from #01 modpack version. So that isn't really relevant anymore. Your second set of logs, has mods from outside the modpack - which is why you're being asked to try only with the modpack, and provide the logs from that attempt.

Missing required logs. Please attach them. You probably selected a mod that changes the language of the client.

Sound pack: Probably not updated yet. Crosshairs: When they are made English. Until then, live with the Russian, or don't use one

Good to hear

Please attach logs Also moved to correct section.

Those error lines are the result of the line that Aslain pointed out. The permissions error on reading the config file.

Not surprised by that. Windows "Smart" Screen is known to be the culprit in many cases

Should be fixed now, try again

Hehe yeah... It freaks out because it's a brand new file, and Microsoft hasn't certified the file (probably costs money, and takes time to get that done..)

The most common is actually that it's Windows' own stuff that screws up, and doesn't show anything, but prevents the file from running anyways

Some antivirus software is most likely behaving badly, if you check Task Manager, you will probably see it with high CPU usage or something like that.

Attach logs - or everything is pure guesswork. But a good guess is you're installing a big DLC, which is being extracted.

Mods in 9.17.1 can be in "mods" or "res_mods" folder - depends on how they're packed by the mod authors. Mods in 9.17.0.x was only in "res_mods" folder. Hope that helps?

Define last version? 9.17.0.x? 9.17.1 is the version where "mods" folder was introduced.

With the modpack installer, there's nothing to worry about. If you're doing things manually, you can see from the zip files folder structure where things should be.