standard first aid list (file paths may vary for servers or non windows users or servers) (s for needs to be done on server/host and client side):
- make a testworld just with the affected mod and one of the other mods as a mod conflict test, don't forget the mod requirements.
- (s) make a file integrety check for space engineers itself.
- (s) delete all modrelated data of the affected mods in the main and world specific storage folder and let it regenerate in case this got corruptet (findable under %appdata%\spaceengineers and %appdata%\spaceengineers\saves\yoursteamid64\yourworldname).
- (s) delete all modrelated data of the affected mods in the workshop folder and redownload it to neutralize eventually data corruption by modupdate (files are findable inside the workshop folder of the steam library folder in which you have installed space engineers).

@TreySidious
in that case please go over the "standard first aid list" if not already done and if that doesnt help report in on the discord with logs and an example world.

just to verify, after un-installing weapons core, my vanilla turrets work perfect again!

weaponcore update broke my turrets. they dont automatically load anymore

@I0_Reaper_0I
ich würd die frage an deiner stelle in englisch stellen da des die sprache is die in der modbeschreibung als einuiges verwendet wurde.

auch einmal als info:
du wirst da mit guter chance über den discord der in de rmodbeschreibung verlinkt ist ne schnellere rückmeldung kriegen als über die kommentare.

kurze frage wie heißt die Mod die du verwendest damit der plant und oder die Galaxy so aus sehen wie in dem video ?

Much love either way, I appreciate the help. <3

Looks like someone else noticed fixed weapons + AI not working for them either on discord, so will see where that goes.

@Mr. President
wouldnt say i am a scholar, but i am a gentleman as long as the other side isnt trying to roast me.


compatibility shouldnt be a problem while using only wc mods, but some older ones that havent been updated for a while to adapt for changes made to wc functions they rely on to function properly might have probs with the changes that have happened.

Thank you for taking the time to reply; you are a gentleman and a scholar, both. Much appreciated.
What I have done so far+extra info:
-test world with just WC. Tried different grids. Built new grid. Issue persisted.
-deleted WC mod data (appdata etc), re-subbed, issue persisted.. though I didn't do world files yet!
-am running weapon pack mods, but all have WC as dependency (so I assume compatibility is ok)

I will finish the 1st aid list and if need be put logs together. Will report back. Thanks again kind sir!

@CTH2004
i did point towards your comment on the wc discord as the response time there is usually faster.

standard first aid list (file paths may vary for servers or non windows users or servers) (s for needs to be done on server/host and client side):
- make a testworld just with the affected mod and one of the other mods as a mod conflict test, don't forget the mod requirements.
- (s) make a file integrety check for space engineers itself.
- (s) delete all modrelated data of the affected mods in the main and world specific storage folder and let it regenerate in case this got corruptet (findable under %appdata%\spaceengineers and %appdata%\spaceengineers\saves\yoursteamid64\yourworldname).
- (s) delete all modrelated data of the affected mods in the workshop folder and redownload it to neutralize eventually data corruption by modupdate (files are findable inside the workshop folder of the steam library folder in which you have installed space engineers).

@Mr. President
take a look here:
https://github.com/Ash-LikeSnow/WeaponCore/wiki/Automaton-Update-Key-Notes

if that and "standard first aid list" (seperate comment due to its size) doenst help its probably time to put together logs and an example world /world with no more mods than absolutly neccessary to reproduce a problem and a premade situation for reproduction of it) and report in and the discord linked inside the moddescription.

Is there something to know about fixed weapons and AI (offensive) blocks? I can't get fixed weapons to fire with AI mode. They work manually, WC is detecting them, they have ammo, etc etc. Angle is appropriate (front facing). Static weapons nor manual facing makes any difference. I'm having a hard time troubleshooting!

okay, I'm makeing a collection for weaponcore mods, is it okay if I use your thumbnail in it?

@TK_Over50
you could use the "unsupported mode" to stop wc from deleting nonwc stuff but it still wont work properly (no working ai, nonwc weapons cant intercept wc munitions and vise versa, . . ) and there is nothing about it that can be done due to se limitations.
if you encounter any problems while using "unsupported mode" you will need to reproduce them with it off to get help with it besides some general always applicable stuff.

wc is a full blown weaponframework and not just a weaponframeworkaddon for the vanilla weaponframework (like for example vanilla+, rearths advanced combat system) and se itself can only handle one full blown weaponframework properly at once.

Just to be clear, there is no compromise for unsupportedmode weapons?

Aight I'll go there, thanks for the response

@TheUndone_Crat
thats a very weird one and i have yet to encounter it.

maybee someone on the discord has an idea what is going on or can with the help of logs and an example world find i what is happening.

Oh and weirdly enough flying as close as possible to the ground in a 2000 block non-wheeled vehicle with similar weapons doesn't cause near as much issue

So I got a very niche issue that's been happening for awhile now. Whenever I'm driving a 10 5x5 wheeled 2000 block monstrosity at decent speed (30m/s+). And I go over a bump or hill in the terrain that brings the hull closer to the ground "Server thread CPU Load" will increase a bit in vanilla. But not to any extent it'll cause lag, at most brings it up to 150%

However when I put weaponcore weapons on the vehicle (just having weaponcore doesn't cause it) it gets much worse, spiking above 300% which causes very noticeable lag spikes

I've turned off shadows and lowered the majority of my graphics settings to no avail. I got the weird feeling this isn't something fixable and I just gotta cope but at the very least is it known why this happens?

If any other information is needed or any questions I'd be happy to answer

@seat2323418
could you please explain what it happening with atleast a few more words, atm it can be either be relatet to preexisting turrets or a custom turret and then it also needs to be cleared up which weapons.

Turrets auto selected but they doesnt fire

@Dr. Glitchgo
while mixing nonwc with wc weapons is not advised you can stop the deletion of nonwc weapons with the unsupported mode (see moddescription) but the nonwc weapons wont have functional aie and nonwc weapons cant intercept wc munitions and vise versa.

@Dr. Glitchgo
first there is no weapon not like by the author, the weapons get deleted are weapons no based on wc which are due to limitations of se itself are not compatible with wc due to se itself only beeing able to handle one weaponframework at once and wc is a full blown weaponframework and not just a weaponframeworkaddon like vanilla+ or rearths advanced combat system.

the deletion of a nonwc weapon shouldnt cause a crash by itself and also shouldnt cause world corruption.
i dont deny that something is going wrong i just say that it shouldnt be.
if you join the wc discord and provide logs from when it happens and an example world (a world with just the mods needed to reproduce a problem and a premade situation for problem reproduction) a investigation can be started to what is going on.

Keeps crashing my game whenever it detects a weapon the author doesn't like. Hey, how about instead of saying "oh you want to use this gun? New world then." maybe add compatibility like "this gun is incompatible with WeaponCore, instead of corrupting your world, the gun will use the Vanilla system."

cheers legend ill have a wander over there now

@the left handed stranger
if i remember it correctly you will need to set them to manual in aiming and firing for it to work, there have been some changes to it just shortly ago.

i for my part dont guide stuff manually into a target, though i suggest asking on the discord for the best response times from the ones on the deep end of the code that can explain what needs to be done to get it working.

nice to see this still active, ive gotten most of the features to work bar one, the tracking of rockets and missiles, ive grouped them, set the manual firing but cant seem to get the knack of getting them to track my curser if thats still a feature of weapon core?

@GK111
its possible to change keybings, though some keys might not work properly if choosen cause of the way how you use them.
the command to change them is findable here:
https://github.com/Ash-LikeSnow/WeaponCore/wiki/Player-Tips#weaponcore-commands

is there any way to change the keybinds? specificly alt and ctrl

@WeirdGuyManus
if you mean with "old circle of where to shoot" the vanilla lock system including the lead indicator that is younger than the wc system for it then yes, but it also has its own lockon system with its own lead indicator.
you just need to do some setting it up via the control menu and you can even have multiple lead indicator with one for each weapon if you so desire.

https://github.com/Ash-LikeSnow/WeaponCore/wiki/Player-Tips#weaponcore-lead-indicator

does this mod take away the old circle of where to shoot to hit the enemy

Anubus, I went on the Discord page and posted the Log file... they have already posted an update. Mine is working like a champ again. Hopefully yours is as well.

@Cannon Glad to know I'm not crazy (this time)

@Anubis, were having the exact same issue and same Fatal Error. This occurred after the WeaponCore update today. Your not alone my friend.

====
17:41:21.4947 [FATAL] Initializer: System.NullReferenceException: Object reference not set to an instance of an object.
at CoreSystems.Projectiles.Projectiles.GetEntityCompareDist(HitEntity x, HitEntity y, ProInfo info)
at CoreSystems.Projectiles.Projectiles.GenerateHitInfo(Projectile p)
at CoreSystems.Projectiles.Projectiles.FinalizeHits(Projectile p)
at CoreSystems.Projectiles.Projectiles.InitialHitCheck(Projectile p, Boolean lineCheck)
at CoreSystems.Projectiles.Projectiles.<CheckHits>b__32_0(Int32 i)

Is there a new issue with weaponcore today? Everytime one of my weaponcore weapons fires, the server crashes.

====
Exception occurred: System.NullReferenceException: Object reference not set to an instance of an object.

at CoreSystems.Projectiles.Projectiles.GetEntityCompareDist(HitEntity x, HitEntity y, ProInfo info)

at CoreSystems.Projectiles.Projectiles.GenerateHitInfo(Projectile p)

at CoreSystems.Projectiles.Projectiles.FinalizeHits(Projectile p)

at CoreSystems.Projectiles.Projectiles.InitialHitCheck(Projectile p, Boolean lineCheck)

at CoreSystems.Projectiles.Projectiles.<CheckHits>b__32_0(Int32 i)

at ParallelTasks.Parallel.For(Int32 startInclusive, Int32 endExclusive, Action`1 body, Int32 stride, WorkPriority priority, Nullable`1 options, Boolean blocking)

at Sandbox.ModAPI.MyParallelTask.VRage.Game.ModAPI.IMyParallelTask.For(Int32 startInclusive, Int32 endExclusive, Action`1 body, Int32 stride)

@riahnoc
there is no forced incompatibility from wc side, its just that se cant handle multiple weaponframeworks properly at once.
wc is a full blown weaponframework and not just a weaponframeworkaddon like vanilla+ or rearths advanced combat system.

though even if you have mods that arent compatible with each other in the world it wont cause se to ctd or hang up or otherwise crash, that is usually caused by file corruption on either se or modende or you setup running out of space for se itself to work properly. having mods incompatible with each other in a world will cause them to not work properly or give a world loading error from my own past experience.

Do love built in incompatibility with fun stuff, What next gonna force my game to crash cause I have a mod yalls don't like on my world?

@SpicyBread
which turrets where that and did they try to hit something that wasn you and you where just in the line of fire?

if you werent even close to the line of fire when they did it it could be something with the are where the shot should hit or trafe beeing of from where it should be.

I've died to my own turrets 24 times just trying to build stuff on my roof, they must be hungry or something because they love blasting me 500 meters away.

no im not new, just havent been on the game for a while

@Jonnyhawkeye
weaponcore handles stuff like firing weapons different from vanilla, if you are completly new to wc i would suggest going over the linked guidestuff inside the moddescription to learn about the differences.

omg as soon As i click the scroll wheel it finally comes up.....i hate how this always happens and sorry for waisting your time..

alright, I try to "Yes" the vanilla way. but the i was trying to enable the hud that helps me lead the target for my guns.i also tried the Ctrl option but it refused to work! like....at all!. guns, missiles, nothing worked the HUD just refuses to come up

@Jonnyhawkeye
let me guess you did try to lock to an enemy the same way as in vanilla?

wc has its own targeting system with miultiple possibilites to lockon to a target:
- via keyboard you can scroll through possible targets via pgup and pgdown
- via mouse with a precision and a are lockon modus as well as the option to turn it off which you can switch through via ctrl

if you want to use painter mode to tell stuff where to shoot you will need to use the mouse and do a doubble click where you want to shoot on the enemy grid.

if that doesnt answer you question please be more precise about what is happening.

you can rebind some of the functions, the commands for that are findable on the github based player tips section.

I cant lock on to enemies anymore, how do i lock on now.

@Demonik
if you have probs with stuff trying shooting through voxel and have already gone over the standard steps (file integrety check, mod conflcit check, cleaning out the files of the affectet mod from the workshop folder and storage folder, testing a new world) to sort reoccuring stuff out make an example world (world with a premade situation and just the barebone amount of mods needed to replicate the problem) and logs form a session where it happens and report in on the discord.

some stuff cant be avoided and also happens in vanilla, for example weapons engaging a target that then goes behind voxel inbetween los checks resulting in weapons shooting into voxel, and atm there are some aftershocks from an overhaul of the los checks on wc side.
just asking when something will happen does not help with trying to get something happen, otherwise the world would be a peacefull place and no one would have any problems.

Any idea on when WC will be fixed with trying to shoot through Voxels?

Ok, thanks for the reply. I was starting to suspect that would be the case; That painting only works with player input.

I suppose I should look around for a script or ask on the discord at some point. Appreciate the time.

@Sai Hottari (2/2)
beside the 2 i did not test any of that myself and i am just a moduser myself so my understanding of backgroundstuff is quite limited.
if you join the wc discord you are probably more in luck on getting someone to definitly answer the question in relation to 1 and 3 if it is possible and how.

if you mean with painter turret a turret set to painter mode that one is if you want to paint a specific point on a target via the wc targeting system and then want a weapon to go after that specific point.