SAS Mod v1.0 report bugs here

M16 Firemode:
- according to the weapon description the M16 should have a burst fire mode, but there is no such mode ingame

Goggles Overlay:
- I think the goggles should have an overlay similar to the gasmask, currently there is no difference between goggles and pure balaclava

frags dont work

As said before, the H&K33 scoped looks like the launcher when other people see you using it and the mask restriction vision is still on when you are using the scope.

@Raptor

From -> http://www.armyproperty.com/Equipment-Info/M16A1.htm

"The major difference between the M16A1 and M16A2 is the fact that the M16A1 could operate in full-automatic mode, emptying an entire 30-round magazine in just a few seconds; whereas the M16A2 is restricted to 3-round bursts, a feature which preserves ammunition and improves accuracy."

The error is in the description because it is taken from the first lines of the Wikipedia page of the M16 and they concern all M16 variables, the one used in the mod is the M16A1 which has just single and auto mode.
We'll correct the description.

About the googles overlay, there is a bug in the final version and the overlay is not showed (we did that and it worked since last beta version), this will be corrected aswell in the first patch.

@WIZ
We tested the frags in BS mode only atm and they did their job there, what you mean with "don't work"?

@Sam
That will be fixed in the patch aswell, thanks for the report

Actualy for the frags i playied with Kamp a few rounds and they worked, against sus and civs.

suggesting add "tango down" or "xray down" to comms

About sounds:

About game engine:
- I have Swat4x.exe, cmd.exe & sasmod.exe in my taskmgr.... We really need it all or we can do another way with only one .exe???

I posted this in the stickied thread as well, but you can copy the entirety of the ContentExpansion\System folder into Swat mod v1.0\system and just run swat4x.exe from there with no problems at all that I've found (just be certain to not overwrite anything already there. i.e click 'no' when asked to overwrite stuff).

This is what I do to get sas mod to work properly with 3D analyze (I use it to emulate hardware T&L by getting the CPU to do all the number crunching).

The sasmod.bat file does the same thing, except it 'cd's into the System\ directory in the sas mod and then runs the swat4x.exe in ContentExpansion's System\ folder from there.

About sounds:

About game engine:
- I have Swat4x.exe, cmd.exe & sasmod.exe in my taskmgr.... We really need it all or we can do another way with only one .exe???

I posted this in the stickied thread as well, but you can copy the entirety of the ContentExpansion\System folder into Swat mod v1.0\system and just run swat4x.exe from there with no problems at all that I've found (just be certain to not overwrite anything already there. i.e click 'no' when asked to overwrite stuff).

This is what I do to get sas mod to work properly with 3D analyze (I use it to emulate hardware T&L by getting the CPU to do all the number crunching).

The sasmod.bat file does the same thing, except it 'cd's into the System\ directory in the sas mod and then runs the swat4x.exe in ContentExpansion's System\ folder from there.

I'll try. Thanks Masterson.
P.S. I did added more in my prev. message.

Sweet

How about you guys 1st unlock the original SAS Mod thread? I wanted to give positive feedback and I was unable to do so...

Anyway, so far, I have no complaints on the SAS mod, great job for a very 1st release, there are few minor bugs I spotted, but nothing too serious, take a look:

1. Crosshair is unballanced pixel-wise, specifically the right side.
2. Weapon sounds volumes are improperly variable, for example a pistol can sound louder than an assault rifle.
3. Bumps don't display well on new models if settings are on medium or lower.
4. Briefing menu images for new models appear very low quality and blurry.
5. The new radio comms still not radio-filtered.

That's about it.

See you on the field

P.S. Also, the flashbang sound seems to change sometimes from the custom one to the default Swat 4 one, did you guys purposelly do this? If not, it's a bug

Suspects, in some standard maps (like Fun Time Amusement), had the body armor with the word POLICE.

Even though this is a 'bug report' thread, I'd like to start out by giving my compliments and a big THANK YOU to Jokeller and Francis for creating this awesome mod! Now that it's released you'll probably enter a phase in which lots of people will tell you what should still be improved and it will be impossible to satisfy all of them. But this mod is like a breath of fresh air into the COOP community and I salut you for that!

That being said, I also have 2 comments to make at this moment...

- Even though I know that the SAS don't play for points, there is a small thing I'd like to point out about the scoring system. It still reduces the score by 5 points for injuring civilians. While this by itself is perfectly fine, my beloved 'sparky' friend is not there anymore to make troublesome civilians comply in a 'friendly' way (I think I'd prefer a punch in real life though). So I have to punch some sense into them, which will cause the same 5 points deduction. Is there any way to fix this? Is it possible to make punching not being counted as damage without loosing the stunning effect? (so we can still keep the deduction should you accidentally shoot a civ)

- The second thing is about wedges. In my opinion they aren't very realistic. Just like with the optiwand, you can't stick them under every door just like that. They also can be placed way to fast and now that you're able to carry 3 of them in one slot, they just feel a bit overpowered. Maybe reducing them to 1 per slot and increasing the placement time would give a more balanced and realistic feeling?

Anyway, thanks again for all the hard work you guys put into this mod! I'll keep you posted should I find any bugs someone else hasn't already found out about...

Suspects, in some standard maps (like Fun Time Amusement), had the body armor with the word POLICE.

I think I read somewhere you have to add a ServerPackage=sas_sus into a file...I think it's listed in another forum.

Not sure if this fix is about the police imprint:

I also noticed yesterday that me and other people playing in your server can't see the new suspects skins (there is a blank bdu, missing texture).
To fix this detail you should go in the Swat4xDedicatedServer.ini and doing the following steps:

- Go under the [Engine.GameEngine] section
- Scroll till the last 2 lines that should look like this:
ServerPackages=SwatDesignerClasses2
GameSpyManagerClass=SwatGame.SwatGameSpyManager
- Adding this line between the two:
ServerPackages=sas_sus

So it will look like this:

ServerPackages=SwatDesignerClasses2
ServerPackages=sas_sus
GameSpyManagerClass=SwatGame.SwatGameSpyManager

Thanks for reply.

I checked my "Swat4xDedicatedServer.ini" and it already contains the line "ServerPackages=sas_sus".

I'll recheck tonight ingame.

Since I'm working on a Swat 4 patch with Mcfluff and since we will be working on a prequel, I messed around ini's and archives for some time.

The suspects having police tags on their backs sometimes may not be the mod's bug but purely game engine's as it "reads" existent vanilla files at 1st and then the modified files from mod folder, and should something miss from the mod folder the vanilla stuff is played/displayed instead. This leads to some strange cases where even though nothing is missing from the folders the engine reads it as that it's missing and uses vanilla content instead, it's probably pure executable memory flaw so there's little anyone of us can do about it without the game source code.

The game has many bugs and considering it's official support stopped many years ago it's doing very well IMHO.

it's probably pure executable memory flaw so there's little anyone of us can do about it without the game source code.

Does the SDK not include the source? Ive delved into the Rvs source but never looked at the SWAT SDK

it's probably pure executable memory flaw so there's little anyone of us can do about it without the game source code.

Does the SDK not include the source? Ive delved into the Rvs source but never looked at the SWAT SDK

SDK is usually a stripped down version of final products source code, it may include resources necessary for mod creation but it won't necessarily uncover the executable and dll sources as this could easily lead to violations and cracking.

Sure someone can bite-crack them, but that's illegal and in most cases can bring many new bugs.

The things is different with Open Source where everyone on this planet can contribute, which is not a case with Swat 4 and specially Unreal Engine.

Hi there,

first I would like to thank the SAS-Mod developers for their outstanding work on the SAS Mod.
Very well done and much fun to play.

I played that for some time now and must say that for the first release it is very stable and quite bug free to me.

Moving around feels much more smooth now and I love those new sounds.

As I read you are planning to patch the Mod in future, I have collected some Improvement suggestions while playing the SAS Mod.

So here they are:

Lightsticks / Chemlights
1. Give more of them to the players as they don't fill much space in your pockets.
2. Make them last longer when deployed.
This way they should get way more useful when marking clear rooms / areas especially on custom maps.

Aggressive Arrest
Make that possible like it is in the SSF 3.2 Mod so we can do proper stealth operations without yelling for compliance.

Alphabetically sorted Map voting list
Default implementation into the mod:

Open your SwatGui.ini file. Search for

[SwatMPVotingPanel_MapList_List]

and add below:

TypeOfSort=SORT_AlphaExtra

So now it should looks like this:

[SwatMPVotingPanel_MapList_List]
TypeOfSort=SORT_AlphaExtra
DisplayItem=LIST_ELEM_ExtraStrData
bVisibleWhenEmpty=True
WinTop=338.360077
WinLeft=705.319946
WinWidth=269.000244
WinHeight=304.849884
bScaled=False
bBoundToParent=False
bScaleToParent=False

Source: http://induktio.net/wiki/Sorted_voting_list

Separated keybinds for IssueCompliance and Interaction in the Mod's user.ini
Default implementation into the mod:

Instead of or additionally to:
F=IssueComplianceOrInteract

Put in:
MouseWheelUp=IssueCompliance
MiddleMouse=Interact

This would greatly enhance the stealth capabilities of a lot of players, as they wouldn't yell for compliance by accident anymore when trying to open doors / collecting weapons etc. and missing the spot while pressing the key.

VoiceOvers
Two sets of voiceovers:
A screaming / shouting set (like those voiceovers from "The Regiment")
and a whispering set for adding atmosphere to stealth operations

Well, that's it for now.
I would be happy if you took those suggestions in consideration of implementation into the SAS Mod.

Thank you for your attention,
r:g

I guess your .ini tweaks about the sorted map list and the Compliance/Interact-issue would be better placed in Mavens Tweak Guide: http://www.sasclan.org/modules.php?name=Forums&file=viewtopic&t=10719

Not sure if it can be implemented in the mod, since (lazy) people (like me) may simply copy their old .ini files from vanilla Swat4 to the mod. This way you don't need to setup all keybinds and stuff again.

Ghost, those are some nice suggestions there

Raptor, I wonder how many people do that. Simply copying ini files may give you vanilla keybinds and save time, but, it causes damage in more than one way.

If you use the vanilla ini files in mods, you may not notice any significant difference, but the "damage" made is hidden. The modded ini files contain lists of archives and files needed for game engine to load, check and pass to your system before play, by using the vanilla ini files, game engine does all that but for default and unmodded files, this will not stop modded files from being loaded because the Unreal Engine is built to double check everything which is the case with those ini files. In simple words, using vanilla ini files in mods will always prompt double checking, thus rasising chances of double files loads, glitches, loading time and even higher ping, in some extreme cases it can even corrupt files. So I suggest that you beat that "lazy" and spend 5-10 mins copy-pasting keybinds into new mods ini files instead as it may just save you the unecessary trouble

@Maven: I know about it, but luckly we have the mod developers at hand

So actually there are (afaik) just 2 small changes at the server side:
- enable team specific weapons to avoid frags in coop ( http://ast.ucoz.org/forum/19-370-2509-16-1338576254 )
- load one package to prevent small graphic errors ( http://ast.ucoz.org/forum/19-370-2520-16-1338649007 )

For some hosting issues sas mod wiki is successfully ported to

www.sas-mod.eu

Nice work there

DUKE, Germany

Might be a bit unecessary and/or over powered(considering we've already got the BSG), but it'd be cool if you could use the remington shotgun for door/hinge breaches.

Maybe I've been playing TR too much.