M0ltar

SIGN-UP STATUS: OPEN (SIGNUP CLOSE MARCH 18TH, 2020 AND LEAGUE STARTS APRIL 4TH, 2020) PLEASE NOTE! SATAL Cold War Edition is a separate competition from the normal SATAL and will run along side the vanilla SATAL throughout the year. Teams are allowed to sign up for both leagues! SCHEDULE The schedule for matches will be found at The Merge on Splash One Gaming once signups have closed. All matches are currently set to start at 1400z on Sunday of each week. To check what Zulu time is for you, see here. WHAT IS SATAL COLD WAR EDITION? DCS World Events, in conjunction with Eagle Dynamics are proud to announce SATAL 2020 Cold War Edition! SATAL Cold War Edition brings the same style of action that our normal SATAL is famous for but adds in more stringent weapon restrictions that limit aircraft to Cold War style munitions. STREAMING All streams will be taking place on the DCSWorldEvents Twitch channel with after action replays and highlights available on Youtube. Streaming times have yet to be decided. PRIZES All prizes are TBA. TIMETABLE - April 4th, 2020 - SATAL Cold War Edition kicks off at 1400z - League brackets will depend on the number of teams at signup. - Groupings will also depend on the number of teams. - Matches can be flown at the teams discretion. This means that teams are allowed to schedule their own match times as long as that agreed upon date is BEFORE the set scheduled date on the Splash One Gaming website. For example, if a match between 104th and 64th is scheduled to take place on April 11th, both teams could instead agree to fly the match on March 10th. - If teams fly a match early it MUST be flown on the DCS World Events servers. This is to ensure that no cheating or exploiting is taking place and to provide both teams a neutral battlefield. - All matches will be streamed and track-able on DCSWorldEvents, The Merge and ED forum thread. RULES* - A single league will be used for SATAL Cold War Edition. - All matches will consist of 4v4 - All matches will be flown as a best of 3. - No match participating members or a team are allowed to chat in a live stream during their match time. If a participating member of a team is caught chatting the team will be issued a forfeit for the match and have 3 points removed from their overall standings. A participating member is deemed to be someone that is flying or is a RIO for a given match. Nonparticipating members of a team are still allowed to chat in a live stream. - Bullseye is centered between two airfields. - Once you enter the bubble you must not exit until the opposing team has been neutralized. - There will be an engagement bubble centered on bullseye which teams must control to win the engagement. - Once you leave the bubble you cannot re-enter. - At least one pilot from the winning team must return to base in order to the win the round. - No AWACS or EWR will be available. - Air frame selection is permanent during individual matches. Teams must choose a set line up for each match and stick with that format. - You may NOT change the air frame line up between rounds of a match. eg. choosing 2 F-15C and 2 FA-18C cannot be altered until the next match. - Payload violations and aircraft violations will result in a loss for the round where the infractions took place. Teams should not leave the server/TS until a final decision has been made and agreed. Decisions often occur at the end of the round. Be prepared to fly another round if a referee decision mandates it otherwise you may miss out. - No RTB to refuel and rearm is allowed after entering the bubble. - A ping limit of 250 will be strictly enforced. Server will auto kick anyone over this limit. - All matches will be hosted on the dedicated 64th server based in a German data center. - If a team fails to appear at a designated match a penalty will be issued; -3 points, walkover/forfeit, and the winning team will be awarded 6 kills and 0 deaths. - Teams will be eliminated at the conclusion of the league based on rankings in the SATAL Cold War Edition league play. - The number of eliminations will be determined based on the number of teams that signup to compete in SATAL Cold War Edition. - Rankings will be used for seeding in the end of the year tournament. - Pilots are only allowed to fly for a SINGLE team. If pilots are found to be flying for multiple teams that team will be disqualified. WEAPON AND AIRCRAFT RESTRICTIONS* - Weapons Banned: AIM-120B, AIM-120C, AIM-54 MK47, AIM-54 MK60, AIM-54C, SD-10, R-77, R-27ET, AIM- 9X, and Nukes - Weapon Restrictions: R-27ER (Limit 2 per aircraft) - Breaking payload or aircraft rules during the round leads to an automatic loss of that round for the at fault team. If a payload infraction is noticed only after the match has concluded an automatic loss will be handed to that team at the time of ruling. MISSION & WEATHER* - Various mission locations will be available with random weather. - All matches will take place on Caucuses. - Missions will be similar to the one used in SATAL 2019, but with varying locations. - Missions will be available for download and testing here. This repo will be updated as more missions are added. MATCH MISSION SELECTION Instead of rolling for mission selection like we have done in the past, this year we will be utilizing a veto style selection process so that teams can have a limited say in which missions they would like to fly on. The process for mission selection is below. - There are 19 missions options in total. - Each team has a total of 9 bans that they must issue on missions that they select. - Teams will take turns issuing bans 1 at a time, alternating after each selection, for each mission location that they do not wish to fly on. - Diamond League will use the Diamond League mission set and Gold League the Gold League mission set. - Once each team has selected 9 mission locations to ban the single mission that is left is the mission that will be flown for that match. *Note: Tournament rules, weapons and missions are subject to change REGISTRATION Please make at least your team captain available on the 64th Aggressors Teamspeak during match play. Team captions, as well as being the primary contact, will also be responsible for referee decisions throughout the year. This is needed in order to ensure that all rulings are as impartial as possible. More details about this will be provided as we get closer to league start. ALL TEAMS MUST HAVE A TEAM REPRESENTATIVE AVAILABLE ON THE SPLASH ONE GAMING DISCORD IN ORDER TO COMPLETE REGISTRATION! PLEASE INCLUDE THIS PERSONS DISCORD ID IN YOUR REGISTRATION POST. AN EXAMPLE THAT INCLUDES THIS CAN BE SEEN BELOW. This list of rostered pilots and selected aircraft is not concrete. You are allowed to fly with different pilots for each match bearing in mind the above rules regarding pilots flying in Gold and Diamond league teams. Teamspeak or Discord will be needed this year in order for organizers to have the ability to reach teams if necessary. Names and aircraft are not (yet) binding. Teams may add pilots to their roster during the tournament. Please use the template below as a guide and post in a new post in this thread to register your team. It is very important that you include as many pilots as possible that will be competing in the leagues. It is also crucial that home country of each pilot and Zulu time be included for information on The Merge. SATAL Cold War Edition Example League: SATAL Cold War Edition Squadron Name: 64th Aggressors Teamspeak/Discord: 195.201.110.22 Contact person Discord ID: <64>Moltar:0099 Aircraft Selection. 2*FA-18C and 2*Su27 Pilot Roster: Rage (United Kingdom +1 Zulu) Combz (United States -6) X-Man (Sweden +2 Zulu) Krippz( United States -6 Zulu) Moltar (United States -7 Zulu) Yaga (United States -7 Zulu) Flame (Egypt +2 Zulu)

What version of Reshade are you running?

It depends. A lot of us just fly at 60 FPS and use vsync so it makes sense for us.

That is correct.

Exactly as the title says... The HSD page is causing massive FPS loss in the Viper in MP. The more clients there are the worse the FPS gets. On Growling Sidewinder the Viper is unplayable. Im going from 60 FPS with MIDS off and HSD not showing to 11 with them both on. This video should enlighten you on what the issue is. Again, this is NOT an issue in SP, but only MP so tracks seemed useless.

I dont think you read or watched the video that I posted. The Winwing Throttle has a recentering radar elevation axis as the hornet should. I recognize that the F16 is working as it should in game, but for those of us that have an actual spring loaded axis it breaks the radar elevation for the 16 in game as the actual 16 axis in the real jet is NOT spring loaded. This means that if you have a spring loaded axis irl it causes the 16 in game to recenter. This makes the 16 unflyable. Yes I could bind it to buttons, but I want to bind the radar elevation to the radar elevation axis on my throttle where it should go.

The is more of a user convenience bug due to user hardware. The antenna elevation auto recenter on certain axis that are spring loaded to recenter. This is due, from what I understand, to the fact that the real Viper does not have a spring loaded antenna elevation axis so if you use one as a control input it will auto center. Here is a video comparing the F18 and the F16 and the behavior I am talking about. You will see that the F18 radar antenna elevation will stay where it is supposed to while the F16 recenters on its own. I'm surmising that this is due to the real jets design. The F18 has a spring loaded antenna elevation axis while the F16 does not. The easiest fix for this in my mind would be to put in a specials option that would allow the F16 axis to work like the F18's does. That would allow users control over what type of input device they have an what axis they have available on their controllers.

PM sent

I want to clarify why this is all ridiculous. If pilots were allowed to be shared and fly for multiple teams, pilots could fly for an unlimited number of teams. For example... 104th could register 10 or even 100 teams with the same pilots allowing them to have a higher chance of winning, allowing their pilots to fly more matches and therefore get more experience in competitive flying, and simultaneously putting more strain on competing teams as they have to fly more matches. The very idea that pilots can be shared is beyond rational thought. In what competition anywhere are players allowed to be shared? No competitive esport allows this. No competitive sport allows this. This should not need to be stated in the rules. Further more it seems that the Chinese representatives from the teams that have been removed that have spoken out seem to have conflicting stories. At least 1 has said that they did not know that pilots were being shared going so far as to ask for for the pilot names to ban them. Others have stated that they knew, but didn’t know it was against the rules. This screams coverup and that it was known that this was malicious. This decision is not up for debate. The decision has been made and it will not be changed. What is done is done. Pilots are allowed to register for new teams next year, but the actual teams in question are banned for the remaining year and next year.

Reshade is going to cause some FPS loss. The FPS loss amount is going to great depend on how many filters you're running simultaneously.

Ladies and Gentlemen, It has come to our attention that there has been some foul play at work inside the DCS World competitive scene. More specifically, it has been uncovered that select teams have been sharing pilots allowing them to compete for multiple virtual squadrons. This provides many benefits for individual pilots and for entire teams. Though this rule is not explicitly stated in the rules, several teams have asked in the past if it would be possible for virtual pilots outside of their squadrons to fly with them in sanctioned matches. The response was always ‘no’ to their query - teams must only compete with members from their own virtual squadrons. Therefore, we feel that it should be no question that teams should consist of squadron members only and that those members, even if the squadron has more than 1 team in a given league or a team in each league, no be shared. They may only fly for 1 team. The only exception to this rule is if a Gold pilot wishes to fly for their squadrons Diamond team they may do so for up to, but not to exceed, 3 rounds. The circumstance that has been uncovered clearly shows pilots being shared between at least 2 teams, both of which are in Diamond league. This violates the rules about pilot rostering, stated or otherwise, and because of that must be dealt with. The teams in question are inSKY and Chinese Festival. On the date of November 23rd, during the matches of RVE vs inSKY and UVAF vs CNF, it was found that multiple pilots, using different usernames, but utilizing the same CUIDs, were flying in both the RVE vs inSKY match that took place at 1400 zulu and the UVAF vs CNF match that took place at 1700 zulu. We must also assume that this pilot sharing behavior existed before being identified during the as mentioned matches and is also taking place in and on teams that inSKY and CNF have in Gold league. Because of this, it is the decision of the DCS World Events Team that all teams associated with inSKY and Chinese Festival, Diamond inSKY and CNF as well as Gold league inSKY and BSW, be removed from this years SATAL competition and be banned from entering or competing in all DCS World Events events for at least 1 year from the completion of the SATAL 2019 season. Since teams that were advancing to the end of the year tournament in both leagues have been removed, changes must be made to fill out the brackets. Therefore, 51st and IRIAF will be advancing in place of inSKY and CNF in Diamond league and JG78 and Dragon Squadron from Gold league. We realize that some of you may view this punishment as harsh, but we want to make crystal clear that this type of behavior will not be tolerated in tournaments, leagues, ladders, or casual play whether ignorance, knowingly, or otherwise. We all play and partake in this wonderful sim, DCS World, for pleasure and recreation and we feel that allowing, tolerating, or even lightly punishing such negative behavior as showcased above promotes the idea that illicit activity or actions are okay. This is in no way how we wanted to wish all of you a happy holiday, but we feel that it is something that needed to be addressed. Hope you all are able to stay safe in the month of December and get plenty of virtual or real world flying in. We will see you back in action for SATAL come January. Stay safe and see you all in the skies. Moltar

I would recommend updating your install as the new versions have been drastically increased in efficiency. Try turning off Reshade filters until you isolate the culprits. If you still need further help let me know.

They're meant to augment to an extent. However, you do NOT want to use in game aliasing while using Reshade. If you have Reshade running you should use aliasing from inside Reshade, but in the end its up to you. Just keep trying different configurations of in game and Reshade settings and see what works best for you in the end.

I think for the screenshots I was using Mustangs terrain, but you are going to see similar results using the default terrain from ED.

I have seen numerous people mentioning or asking about Reshade lately and I want to clear the air of any misinformation and/or answer some questions that I see commonly along with an install guide. I have also included, should you want to use it, my custom Reshade profile. Reshade is a tool that when used correctly can really make a game shine and that is exactly what I have tried to get my DCS world Instance to due. If you have any questions about Reshade in general or about installation please do not hesitate to ask and I will try and do my best to help you out. Common Questions How does Reshade work? Will Reshade break integrity check? How do I get Reshade? Why does Reshade look so bad sometimes? Installation Instructions

I agree that having 2 Phoenix is SATAL is too few, but I cant in good faith allow a missile in more numbers that has too many issues in its current deployment. Thats not because of the missile itself being OP, but because there are issues in the sim surrounding it that cause it to be represented in a misleading fashion. I never said the missile itself was OP in my OP. All Ive been saying is that there are issues in the sim that impact the phoenix that cause it to behave in ways that it should not.

I recognize that the missile is easy to notch and it really is, but the foundation of the problem is that the missile will continue to track you through a notch a lot of times and will even track you when you lose line of site. There have been several several times where I have no 14 nails, missile warning or anything showing on rwr and Im line of sighting a phoenix and then it comes bulldozing through a mountain or just picks me up out of no where and flies through my canopy seconds after the missile warning. I have watched tacview. I have watched F10 on GS. I have seen it out of my own cockpit. Whether this is a ghost or not doesn't matter in my eyes and telling people they don't know how to notch doesnt fix the problem; it just side steps it. There are far too many good pilots and F14 testers saying the same thing. The phoenix is bugged. It should not have magic INS. It should not be going pitbull as soon as the search aircraft loses lock allowing the tomcat pilot to turn cold and the missile to lock you from 30 miles. It should not be flying through terrain. It should not be in one location for the shooter and a different location for the defender. It should not lock you after it’s passed your aircraft. It should not have the seeming broken seeker gimbal limits thst it has. The meat of the issue is the phoenix is not behaving as it should. There is a reason why the patch is coming tomorrow and Heatblur have acknowledged that there are issues with it whether it is their doing or ED's. I have had far too many personal instances where I notch a phoenix and it flies straight through my canopy and does not detonate. I have also had too many encounters where I’ve notched the missile for a long long time and when the missile is let’s say 200 yards from me I get a missile warning and it either kills me or flies through my canopy. I’ve gone back and looked at tacviews when this happens and plain as day the Phoenix is tracking me through my notch the whole time. Is it easy to notch when it works correctly? Absolutely! However, seeing the missile and having to continue to defend regardless of it actually being trashed, having it fly through terrain, having it go pitbull from way too far away allowing the shooting aircraft to turn around, and having it guide to you magically without nails or radar indications are major factors and are why it needs fixing and why it’s still limited to 2 in SATAL. By the way since you brought up SATAL, a big reason for it not getting many kills in SATAL is because people launch the MK47 from way to far away. Far enough away that its out of energy when it reaches its target. I have very very rarely seen people notch the Phoenix in SATAL. It is almost always out of energy when it reaches the target and actually, if you go back and watch my streams, you’ll see that more often than not the Phoenix flies straight through the defending aircraft and does not detonate. Ghost missile? Probably. However, even entertaining the idea that missiles are showing for defenders or spectators in a competitive environment in a false location or a different state than the shooter is a big issue and has brought the Phoenix very close to being banned outright. However if I did ban it it would make the tomcat harmless is most senses so I opted to leave it at 2 to make it at least somewhat viable.

You need to make sure the server allows texture mods. The black screen will happen if you attempt to connect to a server that requires pure textures. I connect to servers all the time.

The Championship Tournament schedule has been posted and can be viewed on https://splashonegaming.com/satal/. The 6 top teams will advance from Diamond league and the top 4 from each group, a total of 12, in Gold league will advance. Top placing teams will be given a buy for round 1. I have elected to push it back until January/February and give teams December off both due to the holiday season and so that they have time to prepare. The Tournament will kick off on January 11th and conclude February 1st. Teams will compete on Saturday, however Diamond league will be streamed Saturday and Gold League will be streamed using tracks on Sunday. There are too many matches to get everything streamed in 1 day hence why I decided to break it up. Another however though is that the finals for Gold League will take place on Saturday. I realize this is a protracted schedule, but Ive tried to space things out so that teams are not waiting around and spending entire days flying. Good luck to everyone in the coming matches and the tournament. Its been an awesome year so far! Let's make the 2019 season one to remember.

Its fixed

Video explains it all and shows how to reproduce, but the TLDR is that changing the radar elevation in BVR mode will change the center point for ACM modes azimuth. Bug is present in any PVE mission, PVE instant action, or PVE/PVP multiplayer scenario.

Tacviews have been uploaded for this weekends SATAL. https://drive.google.com/drive/folders/1_6d4rPUIeIQuz0obVCizrmUKLQGuZzMV?usp=sharing A note from this weekend. The CNF UVAF from this weekend, 10122019, will be reflown due to extreme lag. The current date for that match is set for 11232019 @ 1700z.

Due issues with the match, TAW vs CNF, due to lag and desync, I, along with all of the team representatives that weighed in on Discord, have deemed that the match must be reflown. The match has been schedule to take place on November 16th @ 1400z. If you have any questions please let us know.

As the title says, these are bugged. They are slaved to the vertical antenna elevation of the BVR mode. Raising the antenna in BVR mode will cause the Wide Angle mode to look further up, while raising the antenna in BVR causes the Vert Scan to slew left and right. You can only manipulate the antenna elevation in BVR mode. I understand that Wide Angle and Vert should be able to be manipulated in the ACM modes themselves, but I was under the impression that this was not implemented yet. I did not provide a track as for some reason it didnt save when I recorded the video. However, my video explains in detail how to reproduce this issue. This issue is present no matter what A2A weapons are loaded, what mission youre on, SP or MP, etc. You can reproduce it anytime the radar is on, A2A mode is selected and so on. Hopefully we can get this corrected ASAP as it kinda cripples the bug in ACM. Really surprised no one has noticed this yet unless I just missed the bug posting.

The F18 fuselage missiles that drop off the plane and then ignite are using the same launch sounds as the wing mounted missiles that ignite directly from the pylons. This behavior can be seen in any mission or scenario in F2 view. On all other aircraft the fuselage missiles use a different sound that precursors with a weapon release and then the motor ignition sound.