[RELEASED] MadGoat SSAA and Resolution Scale

[Raul_T]

Hello everyone !

MadGoat SSAA & Resolution Scale is now 50% off as part of the Asset Store Spring Sale!

[Raul_T]

SSAA & Resolution Scale 2.0.8 is live on asset store!
Whats new in 2.0.8

• Fixed issue causing SSAA to throw invalid screen resolution errors on initialization in HDRP
• Minor fixes to ensure initial compatibility with HDRP 8.x.x
• Minor fixes to ensure initial compatibility with URP 8.x.x

[zisiang]

Hi, thank for your bringing us this amazing AA asset.

Previous (some time 2 weeks ago), I was still able to download and install the MadGOat SSAA & Resolution Scale into my Unity project(s).

Today, I encountered a new issue, as it can be seen on the screenshot, it says “Failed to import package with error: Couldn’t decompress package”. I have manually removed the downloaded package from my computer, and redownload it again, the situation is still occurring. For this test, I am using Unity2019.2.19f1 with HDRP setup.

Do you think I may have missed anything or any suggestions about how could we get this fixed…?

Best wishes, Zi

[Raul_T]

@zisiang

Hi, thank for your bringing us this amazing AA asset.

Previous (some time 2 weeks ago), I was still able to download and install the MadGOat SSAA & Resolution Scale into my Unity project(s).

Today, I encountered a new issue, as it can be seen on the screenshot, it says “Failed to import package with error: Couldn’t decompress package”. I have manually removed the downloaded package from my computer, and redownload it again, the situation is still occurring. For this test, I am using Unity2019.2.19f1 with HDRP setup.

Do you think I may have missed anything or any suggestions about how could we get this fixed…?

Best wishes, Zi

Sorry for the inconvenience. Seems like the latest patch we pushed went corrupted during upload to asset store servers. We try to solve this as fast as possible.

[Raul_T]

@zisiang

Hi, thank for your bringing us this amazing AA asset.

Previous (some time 2 weeks ago), I was still able to download and install the MadGOat SSAA & Resolution Scale into my Unity project(s).

Today, I encountered a new issue, as it can be seen on the screenshot, it says “Failed to import package with error: Couldn’t decompress package”. I have manually removed the downloaded package from my computer, and redownload it again, the situation is still occurring. For this test, I am using Unity2019.2.19f1 with HDRP setup.

Do you think I may have missed anything or any suggestions about how could we get this fixed…?

Best wishes, Zi

The issue should now be fixed!

Thanks for bringing this to our attention and sorry once again for the inconvenience

P.S. make sure to delete the old package from the asset store cache on your drive before downloading the new one to avoid issues.

[zisiang]

Hi Raul, thank you so much for fixing this - I will give it a try asap and see how does it go

At the meantime, Unity2019.3.6f1 onwards officially supports HDRP for VR, do you think we can use MadGoat AA for it (SteamVR)?

Cheers, Zi

@Raul_T

The issue should now be fixed!

Thanks for bringing this to our attention and sorry once again for the inconvenience

P.S. make sure to delete the old package from the asset store cache on your drive before downloading the new one to avoid issues.

[Raul_T]

@zisiang

Hi Raul, thank you so much for fixing this - I will give it a try asap and see how does it go

At the meantime, Unity2019.3.6f1 onwards officially supports HDRP for VR, do you think we can use MadGoat AA for it (SteamVR)?

Cheers, Zi

The SSAA VR script on its own should work on any SRP, however our custom image filters are not implemented on HDRP and even URP for VR (mostly due to how unstable VR and its API was on SRPs) so downsampling filtering will fall back to whatever the SRP uses internally to resize textures (iirc bilinear).

This being said, the supersampling itself should work on VR, but filtering and postprocessing AA will be limited to pipeline defaults. If you find any issues with it and it doesn’t work at all please let me know and we can figure this out.

P.S. Thanks for letting me know about VR being marked as stable, I wasn’t aware of this. Will definitely look into it.

[Raul_T]

A small sneak peek of some awesome new features coming in 2.1.0

• Partial TSSAA support for built-in pipeline (makes use of post processing stack v2 at the moment, a proprietary implementation will probably come in future versions)

• Support for VR SinglePass Instanced rendering

• Support for URP Camera Stacking (no sneak peek for this yet - under construction)

• New sharpen feature - brings back a great amount of texture detail that gets lost in filtering and Post AA
  

  
  
  (open pictures in full size for comparison)

• Greatly improved upsampling render quality by allowing for post processing AA and sharpening with resolution scales under 100%
  

  
  
  (open pictures in full size for comparison)

- New operation mode for rendering at fixed resolutions - Useful for benchmarks etc.

The big update should be dropping in the upcoming weeks if nothing bad comes up! Also don’t hesitate to give us feedback or ideas

– Raul

[RobRab2000]

Woo! Super exciting! Can’t wait!

[Stormbreaker]

Hi @Raul_T ,

I’ve been having some trouble with the API. In my game options I have a simple checkbox to enable or disable dynamic resolution scaling. When enabled the mode should be set to Adaptive with limits 0.5f - 1.5f. When disabled the resolution should be fixed at 100%. Here is the code I’m using:

        Debug.Log("Dynamic res changed: " + dynamicResolutionChanged);
        if(dynamicResolutionChanged && madGoatSSAA)
        {
            if(dynamicResolution)
            {
                Debug.Log("Dynamic resolution enabled, adaptive");
                madGoatSSAA.SetAsAdaptive(0.5f, 1.5f, Filter.BICUBIC, 0.8f, 1f);

            }
            else
            {
                Debug.Log("Dynamic resolution disabled, fixed");
                madGoatSSAA.SetAsScale(1f);
            }
            dynamicResolutionChanged = false;
        }

This is the log output when my scene is first started with the SSAA component visible. As you can see the mode should be set to Adaptive, however nothing changes on the component and it remains in the default state.

I then disabled dynamic resolution in my game options. This seemed to set the component correctly however I’m not sure why the operation mode changed to “Custom” rather than “Resolution Scale”.

I then re-enabled dynamic resolutions in my options and as you can see the mode was not set to adaptive however the filter was set.

This doesn’t seem right. Any idea what is going on here?

EDIT: To add on an additional question, how does adaptive resolution with target 60 FPS decide to enter supersampling mode when V-Sync is enabled? As this locks the framerate to 60 I get the impression it will never supersample.

[Raul_T]

@Stormbreaker

Hi @Raul_T ,

I’ve been having some trouble with the API. In my game options I have a simple checkbox to enable or disable dynamic resolution scaling. When enabled the mode should be set to Adaptive with limits 0.5f - 1.5f. When disabled the resolution should be fixed at 100%. Here is the code I’m using:

        Debug.Log("Dynamic res changed: " + dynamicResolutionChanged);
        if(dynamicResolutionChanged && madGoatSSAA)
        {
            if(dynamicResolution)
            {
                Debug.Log("Dynamic resolution enabled, adaptive");
                madGoatSSAA.SetAsAdaptive(0.5f, 1.5f, Filter.BICUBIC, 0.8f, 1f);

            }
            else
            {
                Debug.Log("Dynamic resolution disabled, fixed");
                madGoatSSAA.SetAsScale(1f);
            }
            dynamicResolutionChanged = false;
        }

This is the log output when my scene is first started with the SSAA component visible. As you can see the mode should be set to Adaptive, however nothing changes on the component and it remains in the default state.

I then disabled dynamic resolution in my game options. This seemed to set the component correctly however I’m not sure why the operation mode changed to “Custom” rather than “Resolution Scale”.

I then re-enabled dynamic resolutions in my options and as you can see the mode was not set to adaptive however the filter was set.

This doesn’t seem right. Any idea what is going on here?

EDIT: To add on an additional question, how does adaptive resolution with target 60 FPS decide to enter supersampling mode when V-Sync is enabled? As this locks the framerate to 60 I get the impression it will never supersample.

Hey!

Sounds like a bug with the API and I’ll have to look more into it to be sure what happens there. I’ll let you know as soon as I find anything

And for the other question, seems like you’re right. I’m shocked nobody (including me) ever noticed or reported this before. I’ll see what I can do about this.

Thanks for reporting!

[Stormbreaker]

@Raul_T

Hey!

Sounds like a bug with the API and I’ll have to look more into it to be sure what happens there. I’ll let you know as soon as I find anything

And for the other question, seems like you’re right. I’m shocked nobody (including me) ever noticed or reported this before. I’ll see what I can do about this.

Thanks for reporting!

No problem. If anyone faces this issue in the meantime as a workaround I’ve added two SSAA components to my camera, one adaptive and the other fixed. Now I just toggle the components enabled status depending on the checkbox state. This only works for me because I have set configurations, if the player is allowed to adjust target refresh rate / scaling limits it won’t work for you.

[Raul_T]

@Stormbreaker

No problem. If anyone faces this issue in the meantime as a workaround I’ve added two SSAA components to my camera, one adaptive and the other fixed. Now I just toggle the components enabled status depending on the checkbox state. This only works for me because I have set configurations, if the player is allowed to adjust target refresh rate / scaling limits it won’t work for you.

Hello again!

The adaptive API issue is due to a line of code in the API methods that somehow went missing with some previous update and slipped through our pre-release tests. You can fix it by adding this to each SetAsAdaptive function in the SSAA scripts:

InternalRenderMode = RenderMode.AdaptiveResolution;

For example:

As for the vsync targeting issue, I’m working on something and I’ll get back to you soon

P.S. I’ll push a 2.0.9 patch with both fixes and some other fix of a postprocessingstack integration issue reported on discord ASAP

[Stormbreaker]

@Raul_T

Hello again!

The adaptive API issue is due to a line of code in the API methods that somehow went missing with some previous update and slipped through our pre-release tests. You can fix it by adding this to each SetAsAdaptive function in the SSAA scripts:

InternalRenderMode = RenderMode.AdaptiveResolution;

For example:

As for the vsync targeting issue, I’m working on something and I’ll get back to you soon

P.S. I’ll push a 2.0.9 patch with both fixes and some other fix of a postprocessingstack integration issue reported on discord ASAP

Thanks, just tested and this fixed the issue. Looking forward to the vsync update

[Raul_T]

@Stormbreaker

Thanks, just tested and this fixed the issue. Looking forward to the vsync update

I came up with something to support vsync target framerate, could you check this out?
Replacing the

protected IEnumerator UpdateAdaptiveRes() {...}

with the following in MadGoatSSAA.cs should do the trick:

protected IEnumerator UpdateAdaptiveRes() {
    yield return new WaitForSeconds(UnityEngine.Random.Range(2, 5));
    if (InternalRenderMode == RenderMode.AdaptiveResolution) {
        var compFramerate = AdaptiveResTargetVsync ? Screen.currentResolution.refreshRate : AdaptiveResTargetFps;
        if (PerfSampler.CurrentFps < compFramerate - 5) {
            InternalRenderMultiplier = Mathf.Clamp(InternalRenderMultiplier - 0.1f, AdaptiveResMinMultiplier, AdaptiveResMaxMultiplier);
        }
        else if (PerfSampler.CurrentFps >= compFramerate + (AdaptiveResTargetVsync ? -1 : 10)) {
            InternalRenderMultiplier = Mathf.Clamp(InternalRenderMultiplier + 0.1f, AdaptiveResMinMultiplier, AdaptiveResMaxMultiplier);
        }
    }

    if (enabled) StartCoroutine(UpdateAdaptiveRes());
}

This will allow the plugin to supersample as long as the framerate matches the refreshrate. Will also be included in the 2.0.9 patch.

[Mozq8]

Hello there, Unity 2019 LTS, I’ve been experimenting with the asset and I got 2 questions:

1. For some reason, whenever I try to apply motion blur (PPS v2) the whole image becomes very blurry
2. Is it possible to use the asset with PC games? I heard that it can be pretty heavy for gaming

[Raul_T]

@Mozq8

Hello there, Unity 2019 LTS, I’ve been experimenting with the asset and I got 2 questions:

1. For some reason, whenever I try to apply motion blur (PPS v2) the whole image becomes very blurry
2. Is it possible to use the asset with PC games? I heard that it can be pretty heavy for gaming

Hello!

1. The issue you are talking about will get fixed in patch 2.0.9 that I mentioned some posts before.

@Raul_T

P.S. I’ll push a 2.0.9 patch with both fixes and some other fix of a postprocessingstack integration issue reported on discord ASAP

2. Not sure if you are the same person, but earlier I explained to someone over discord how the SSAA works and how the performance scales in regards to games:

It’s hard to measure the performance of SSAA at a general level since it hardly depends on what you render on screen. SSAA basically does supersampling, so it renders the game at a higher resolution then downsamples the image back to the screen res.

It’s also not really a replacement to SMAA/TAA since it can be way more performance heavy, but it can be used as an option on top of post processing AA when the hardware allows for it (think about the resolution/render scale sliders in most AAA games these days)

So the performance impact behind SSAA is similar to comparing your game on 2 screens of different resolutions. For example if you target 1080p, SSAA x4 on 1080p will have the same requirements as playing on an 4k monitor since it basically renders at 200% resolution and scales it back to the screen size

[Raul_T]

SSAA & Resolution Scale 2.0.9 is live on asset store!
Whats new in 2.0.9

• Fixed issue with API causing adaptive mode to not be set correctly via code
• Fixed issue causing adaptive mode to not super-sample when using vsync as target
• Fixed issue causing SSAA to break motion blur (Fix requires PostProcessing Stack v2 integration to be enabled in extensions tab)

[Raul_T]

SSAA & Resolution Scale 2.0.10 is live on asset store!

Whats new in 2.0.10

• Fixed issue causing SSAA to not initialize correctly when instancing a new camera from existing one
• Fixed issue causing SSAA to not initialize correctly when disabling and re-enabling camera component
• Fixed deprecated code errors on 2019.4+

[Raul_T]

SSAA & Resolution Scale is now on sale at 50% off on asset store!
Check it out at LINK