Okay so now I'm getting another error = https://prnt.sc/2e0jOFU505WZ
Posts by Kippa
-
-
-
-
Hello,
As the title says I have constant red messages spamming in the console, my raid times are between 30-35 minutes and I have no extracts available on any map I play on. I downloaded and installed NeverLoseEquipment because of these issues and I have to wait until for my insurance returns. The red messages were happening before I installed any mods and I haven't tampered with any files so I'm very confused why this is happening. The raids times and extracts may be caused by FAIT but I'm still unsure on this.
Is anyone else experiencing this issues and is there a fix for these? In the mean time I will be doing some testing to see if I can narrow things down, hopefully someone can explain things better.
-
Hi Fin, I am getting this error on Interchange playing as PMC the message doesn't appear on other maps, what could be causing this? = https://prnt.sc/HXl54Uv2-4Xy
I accidently closed the server and then realised I need the debug hash to give you more detail but I will try and replicate the error with the debug hash to hand sorry for that.
My last couple of raids I have had no extracts, the raid times were 30-35 minutes instead of 45 minutes and when I press the tilde key to show the console it spams red messages constantly every second = https://prnt.sc/nmFVUQdDj8Vx
I have no idea what it causing this to happen, I never had this problem in version 2.3.1.
-
maybe, can't promise anything tho
It's better than a no so I'll take that lol. Thanks for responding!
-
I love this mod I was just wondering could you maybe add or port some other British weapons in to Tarkov like the L115A3 Long range 'sniper' rifle, L129A1 sharpshooter rifle and any others that are even possible to add to Tarkov? I wish BSG added more "Britishness" to the game in terms of weapons and characters, if you have watched the Raid full length film there are British special forces or units of some kind so you would expect more of a British impact but there isn't.
Thanks for your work bud!
-
I get the same message as well = https://prnt.sc/qx4aoBcmOEgl
I think we will have to wait until it comes back online or until Lua updates the link, this happens from time to time.
-
Could anyone share their advanced inventory config for healing items? I just can't seem to have that ai's only have one healing item type in their inventories.
Second to this! The AI's inventories always have at least 2 blue gunpowder's, 2 or 3 melee weapons and 4+ medical items and not the best quality items either things like AI2's, Bandage, standard splints etc.. not enough variety with meds.
-
I just did a raid on Factory with the latest version of FAIT and no AI spawned and I got this reference error message in my local server - https://prnt.sc/EXzhoktbvs_7
My Debug Hash below -
4079081775ă4365,14ă241ē85Ć664,7294đĔ04693ē7,55801Ć2330ij06Ī1ijĨ215ċ2ĉŁ9,Ļ8ăĮ2ćĘą1,9637Ħ73ĬĞ19Ī6Ą700Ő02ėĐğĝ871āćĸ8Ĕ626ďĚ68Ŷ5şěʼn0,|ŎżżŎ|assaultŽpmcboƊfollowergluharƄƆƈƑƓƕƗƙƛƝrscouƣƔƖƘƚƜƞsecurity,ƒưƦƳƩsnipeƾƤƱrkojaDžƽƿƥƘƆDžtƞljǀƘbƈlƽ|ƃƅƇƉgrƭp,beǙuƶcŽ-0.ĎƁ.ľ,2.čďǽŎ1.2ǾȃǿǷ,dz3ǽĨƁǹȌǿǽżPMCsȐŽƏtnameshƘLjƶLJƟtetȟmwƻhƬmmƄŽȂȏȉȏſȄȇȸȵǽȂȴȃƀŽƠǤƊǡƌƎƐǚǔƧƴƟǣƢɈNjǂƵƬƮɏǁƨƵƷƹƻǒNJɖɋDŽdžLjǡǫǭǯ,ɁƢǦǨŽȶſǻŅȸŁŽżĴŽ|ƁżǡŎĜɺɰɽȉĜȲǽžɴĎǡ4ĎėɶĀ,Įɶʇʉʆ|ʌʎǡ|Ŗǹʒżɼ|ȼɶ-ǿŲžȖ|ɶɳȹȸĪdz8ĝȸŸɬʛɹɷŅʲȉʒʀɶȺʁʃʯʯǡĬŏʲˀăʏ|˃˂Ď˄ʖ2ʱɶȂʜʞǡʠȍɬʤʦʳȌɸďǴďȿĈŽȉʢʝ,ˢȺȺˆż˟ǡǼŪʲ˟İʲ˫Ď˭ɶ˯ŪʏIJīʲˌ˺ɶżŜˎɾˣʜ˓ēȱǽʆpumǩƏƉ˗Ⱥȿȿˆd52cc5ba4bħĸĀėşķȂ5cdeb2ğd7fşc̣e7ceĆɼɹȯpȚȜȞȠ,ȢƘaȥȧeȩȫȭȯȕ˘ʨ̒ȷżǵȃɷ.ʬȵȁ˛ʂɮʢɻʛȻɰŎʸŎȂżȂʂͥ˽̥īɱʴ͎˙ɱşȸ̒5:Ĭ:ͰȂaƔɧͺlͻ;ͽͿȖ
-
are snipers spawning for you? I think there might be an issue with LUA's rework, because they sure did spawn with FAIT. I've played several raids in customs and none spawn.
edit: nevermind...it was just a long string of bad luck I guess... next ride after this on spawned lol
How do you get them to spawn? I haven't been able to get any to spawn for some reason
-
How-do,
I don't think it's a big issue as I have the same pop up message when going in to my hideout after restarting SPT, it doesn't happen all the time it's just on the odd occasion but the hideout is perfectly fine. As for Live Tarkov, it happens on there too so I'm going to assume it's a bug with the game itself but I could be wrong I'm not sure. I wouldn't worry about it unless someone with more information than I have says otherwise.
-
I believe BSG disabled the ability for players to free-look with the mouse wheel in one of the previous updates I can't remember exactly which one but it's not an AKI issue.
-
Update! The latest patch 1-21-6a has fixed this issue.
If you are referring to the PMC's being levelled 0-2 is fixed in 1-21-6a, that isn't true sadly. Every PMC I kill is always levelled 0-2 for whatever reason is unknown to me, not sure if Fin is aware of this but it needs looking in to.
-
Not sure if anyone is experiencing this on the latest version for 2.3.0. All pmcs regardless of USEC or BEAR were assigned as raiders (pmcbot). Their dog tag names are from raider's name list and their level can only be 0 or 1. I have narrow down to only run with this mod and removing the mod the role assignment was fine again.
Yeah I am having this issue too. Did a few raids and found that the majority of the dog-tags and the names of PMC's were Raider names and were levelled between 0-2. It's not a big issue but it just means more RNG to find higher levelled PMC's.
-
Hi, I seem to be having an issue with Scavs and my Player Scav not having any weapons or gear. In the config I only changed the Overall Difficulty multipliers, Silly Changes at the bottom of the file and a few other values but nothing that would drastically change the gear for the AI.
The screenshots I have attached are all from consecutive raids and not from the same one,
I wanted to make sure that it didn't just happen in a single raid.Update: I messed around with some of the settings for the last 12+ hours and I have found that 1 in 5 or 6 Player Scav raids there is no gear for my Player Scav and in my PMC raids about 30-35% of the Scavs (of all total AI spawned) in the raid stand still frozen/won't aggro with no gear or weapons. It could be user error or there's just something not working together, still unsure but hopefully I can figure it out.
-
"Faupi-HideoutArchitect" cause problem
Okay I'll mark that one down, if there's anymore just update your comment please bud.
-
With the release of 2.2.3 earlier today I completely reinstalled SPT, created a profile and loaded in to the game successfully with no errors and no mods installed.
Next, I closed the game and started adding mods while making sure they are compatible with 2.2.3 and removing any that cause errors. Everything seem to be working accordingly, no errors in the console window and start up was successful, brilliant. I clicked on any of the traders and this is were I notice nothing has loaded and my stash has nothing also.
Prior to making this thread I have since tested removing all mods from the list but I still seem to experience this issue/bug, hopefully someone can explain what is happening and I have attached screenshots.
-
Continuing from my previous post earlier I believe the gear issue with FAIT is there's something in the Raiders inventory or an ID value causing the error trace but other people may need to test this out for themselves so we can identify if this is correct.
If anyone has the same/similar issue please try what I did below and reply to this to see if this works or it doesn't work, I'm curious to see if it's a particular or the same item(s) causing the error traces.
I went in to the Config Editor and set "Change gear for this group" for Scavs and PMC's to true and Raiders to False and no errors show up in the console window and the game works as normal. Raiders are still OP, possibly even more than PMC's in terms of gear which isn't too surprising since FAIT isn't changing the Raiders inventories. I'll be doing some more testing on this so I can narrow it down further and will update later.
(Fin if you are already aware of this just know I'm only trying to help mate and you can ignore this lol)
-
Forgot to mention too, the mods in my list have been re-configured to work with 2.2.2 (I had to go in to the package.json files and change a value in there to make it work).