I am having an issue where there is always at least one screen that will ignore its affected renderer exclusion settings. This happens with more than one mesh renderer and each with it's own screen.

When loading any texture into MainTex, nothing shows up.

Changing the shader to Standard light model and throwing the LTCGI contribution stuff into Emission gets around it

In order to display feedback for options panels controlling the enabled state of LTCGI, I've had to modify the UdonAdaptor to cache the enabled state and provide a getter for it.

Here's what I've done:

    private bool isGlobalStateEnabled = true;
    public bool GlobalStateEnabled
    {
        get => isGlobalStateEnabled;
    }

    public void _SetGlobalState(bool enabled)
    {
        float fstate = enabled ? 1.0f : 0.0f;
        GlobalShader.SetGlobalFloat(GlobalShader.PropertyToID("_Udon_LTCGI_GlobalEnable"), fstate);
        isGlobalStateEnabled = enabled;
    }

Super super simple, but helps a lot. If there's a better or different way to access this value I missed, let me know.
Thanks!

Dragging the ltcgi prefab into the scene creates a popup message you cant close and it freezes the unity editor. After adding U# into the project the popup still kept appearing, the UDONSHARP define got added but the code from ltcgi didnt recompile with it. It worked only after removing and adding back the ltcgi package. It also kept appearing 2 times after, when switching the build platform, that but i was able to close it and it worked

Not sure if there is a fix for that as its probably a unity bug (what might work is a custom define set on the assembly definition), but at least a fix for the popup message would be nice.

LTCGI is not showing any console error logs and is working in editor, but when uploaded to VRChat it is not showing reflections / GI after importing Audio Link.

I have yet to figure out what causes this.

Tried both Filamented and Orels shaders, but enabling LTCGI on either gives me an error as they try to pull the shaders from Assets/_pi_/_LTCGI/Shaders/ when LTCGI is located under Packages/LTCGI/Shaders/

When attempting to install the latest LTCGI package, it throws a large compiling error in the console. Says it does not belong to a U# assembly?

This was tested with SDK 3.0.9 and UdonSharp 1.0.1 via the Creator Companion.

I am trying to use the USharpVideoAdapter, but the script has this error. Tried to diagnose but I can not figure out how to solve it.

Double checked UdonSharp, USharpVideo, and the VRCSDK.

Assets/_pi_/_LTCGI/Adapters/LTCGI_USharpVideoAdapter.cs(63,6): System.Exception: No UdonSharpBehaviour class found in script file, you must define an UdonSharpBehaviour class in a script referenced by an UdonSharpProgramAsse

So I know this is going to be an weird and very specific request, however I'm currently working on a fulldome/domemaster project and I would love to include this if I can get it functioning right. I've attached a test video below as to what I am doing to help explain this very specific use case I have. I've tinkered around with the cylinder method and got a result but nothing close to what I was hoping to figure out, thus the request for a sphere/halfsphere/dome shape (if at all possible). No harm if it isn't something that can be done with relative ease and is a declined request, just thought I would ask!

Using version 1.3.2 w/ ProTV as the VideoPlayer.

When I import LTCGI 1.5.0 and ProTV 3.0.0-beta.16 (Unity 2022.3.6f1) i get following error:

VideoManagerV2 is not used anymore in the new Version of ProTV. It uses VPManager now.

Solution may be to modify LTCGI_ControllerExternal.cs (line 187) to read:

var valueInConfig = float.Parse(line.Substring(line.LastIndexOf(' ')).Replace('f', ' '), System.Globalization.CultureInfo.InvariantCulture);

After many tries in new SDK 3.3.0 where Play mode is not more needed, LTCGI seems not work anymore, no visible effect, because script generate also in runtime for build & upload.

Maybe i miss something, but last tests showed no more effect on walls.
Can you take a look at it?

LTCGI_RuntimeAdapter class not found OR mismatch

According to the file <UNITY_PROJECT>/Library/PackageCache/at.pimaker.ltcgi@14b23485f4/Runtime/LTCGI_UdonAdapter.cs, there is already statement from line 16:

#if UDONSHARP
[UdonBehaviourSyncMode(BehaviourSyncMode.None)]
public class LTCGI_UdonAdapter : UdonSharpBehaviour
#else
// FIXME: This makes the filename mismatch the class name
// - I think Unity doesn't like that?
public class LTCGI_RuntimeAdapter : MonoBehaviour
#endif

Yes, Unity 2021.3.23f1 does not like that.

Screenshots

The UdonAdapter class indeed transformed into regular Runtime Adapter class. However, due to some nature of C# (perhaps?), the filename must match with its class name.

Therefore currently it only works (maybe?) for VRChat & perhaps not standalone nor any other VR games, since the file name of the adapters combined to or propagated for is LTCGI_UdonAdapter.cs, while the converted to regular class name is LTCGI_RuntimeAdapter : MonoBehaviour (different than filename).

Workaround

Possible workaround & patch?:

Separate those adapters to each respective filename

• Transplant. Copy whole Udon Adapter class into a new file LTCGI_RuntimeAdapter.cs next by UdonAdapter file.
• Scrub. scrub both these file so the Udon ones only activates if there is UdonSharp installed per #if UDONSHARP. And the regular runtime ones only activates if there is no UdonSharp per #if !UDONSHARP.
• This should make class query work since now the class names matches with their filename.

Or maybe, keep UdonAdapter name, while when Udon is not installed it acts as regular Runtime Adapter?

So after VRChat updated to 2022, I tried to upload my world and LTCGI is not working anymore. I think it could have something to do with the lack of play mode during build. So it's more a SDK 3.3.0 problem, than 2022, but because 3.3.0 is old already, I will report as a 2022 problem.

What's the issue: LTCGI doesn't affect third-party shaders (orels, Mochie and Fillament tested) unless there's a single LTCGI_Screen set as dynamic

Video Player: VideoTXL, but it's not only video texture being affected, static textures too and emitters.

There's a workaround, if you have a single dynamic screen all the other ones even if it's set to static start working again. But only on editor.
Avatar lighting still work (dynamic disables it?). So I don't know what's the culprit for it, or if it's a issue caused by my own Unity setup.

I would like to request a version of ltcgi that could possibly work in a standalone form with out the udon side of it or use on other platforms that lack it. Possibly a sdk2 port or just something that works in any unity project.

I've run into issues trying to install this to a 2022 project, I'll give you a rundown of what the issues are but I think the TL;DR is going to be to just ask you to install LTCGI to a fresh 2022 project and fix the issues that arise.

The following occurred in a completely fresh project made with the VRCCC.
LTCGI 1.4.1 was installed via the VRCCC method.

1.) First, this dialogue, which I'll press "Confirm" on.

2.) Next, upon attempting to open the new project, this warning dialogue from Unity. I am going to click "Yes, for these and other files that may be found later" because otherwise it pops up every time the project is opened. Note that the next few issues arise even if you click "No" anyway.

3.) When trying to drag the LTCGI Controller prefab into the scene (VRCDefaultWorldScene), shader compile errors are thrown and then these shaders are thrown into the "Failed to Compile" list category in Unity when selecting shaders on a material.

4.) I thought "okay, so LTCGI shaders are borked, fine, I'll just use something else" and imported Orel's shaders.
However I then found that while in this state the LTCGI variant of Orel's shader also fails to compile...

5.) Okay, so now I knew this is an issue that needs addressed if I want LTCGI to work.

Now I'm no programmer, but upon inspection it appears that in the file it's complaining about, "LTCGI_config.cginc", there's a line that says "not-available".

This text just looked out of place to me, and as if it's a placeholder text that Unity substituted in upon reaching an error. So I looked into the repository for the original code and, sure enough, this is what's supposed to be there.

So I first tried just changing the "not-available" text to that URL, but Unity would keep changing it back to "not-available" automatically. Clearly it was unhappy with the absence of something, and that something was probably AudioLink.

So I tried installing AudioLink and, sure enough, the issues went away. So the only solution was to actually install AudioLink to the project. If you do that, that line in the LTCGI_config.cginc will change to the AudioLink URL on its own and the shaders will succeed to compile. Removing AudioLink will cause the shader compile errors to resurface.

As far as I'm aware, AudioLink isn't intended to be a dependency for LTCGI.
If it is, well I couldn't find anything in the repo or documentation to suggest that.
So if this isn't intended behavior, definitely look into doing an update pass for LTCGI.

I figured these may just be issues that arose with the 2022 upgrade that just haven't been addressed yet.

There may be other bugs that I just haven't found, I don't know what everything is supposed to look and behave like so I have no frame of reference for just visually telling whether anything is wrong or not. So definitely poke around and make sure it's working as intended in 2022.

Thanks.