playMaker

Author Topic: Editor Window Default is Pitch Black  (Read 4405 times)

acornbringer

  • Junior Playmaker
  • **
  • Posts: 75
    • Acornbringer.com
Editor Window Default is Pitch Black
« on: August 22, 2018, 10:23:00 AM »
Hi there!

I decided to download the latest version of PlayMaker for my new project but when I brought up the editor window, the first thing I noticed was the work space background was pitch black instead of the usual grey making things very hard to see overall.

I went into the settings and changed the theme from the default - which was dark - to the light theme and saw a slight change from the pitch black to a dark grey. I can't help but feel like something is off with these setting in this version.

Can anyone clear this up for me? Is something wrong or are things working as intended?

Thanks in advance!

PlayMaker 1.9.0.p4
Unity 5.6.3p1 (plus)
Windows 10

lukew

  • Playmaker Newbie
  • *
  • Posts: 42
Re: Editor Window Default is Pitch Black
« Reply #1 on: February 27, 2019, 11:10:35 PM »
Sorry for replying to old topic but I've got same error today. Maybe someone would find it useful.

I was testing Playmaker upgrades from 1.8.x to the latest version on some temporary projects. In one of them, editor background become black and there were some other errors with colors (like action headline selection color).

I was trying a lot of things. Reimporting Playmaker, deleting Playmaker and importing it again, deleting whole Library folder, deleting all other assets etc.

Nothing helped until I've deleted all assets in the ProjectSettings folder. I've no idea which one was causing the problem (as I've deleted all of them at once) but there was something there that caused the issue.

Any idea which one of them could be the reason of this kind of bug?

acornbringer

  • Junior Playmaker
  • **
  • Posts: 75
    • Acornbringer.com
Re: Editor Window Default is Pitch Black
« Reply #2 on: February 28, 2019, 06:17:13 AM »
Hey Lukew,

I ended up reverting to an older version of PM that I thankfully had saved and haven't encountered the problem again. Unfortunately this means I never found a solution to this problem but hopefully someone who could tell what's up will see the thread and help out.

To make things easier, could you say what version of Unity you are using as well? I think there may be a correlation with this issue.

lukew

  • Playmaker Newbie
  • *
  • Posts: 42
Re: Editor Window Default is Pitch Black
« Reply #3 on: February 28, 2019, 09:31:11 AM »
Hey acornbringer,

I was using Unity 2017.1.0.p4 in this case.

In my case deleting all ProjectSettings assets helped but I was doing it on a temporary project. After deleting them and restarting Unity I had to right click and reimport Playmaker folder. Would be nice to know which one of the project settings assets is related to this. Project was empty. Playmaker was the only thing in it after deleting everything else ealier (to check if there is any other asset unrelated to Playmaker that could cause the error).

I have no idea if something in one of the project settings assets was causing the bug or maybe Unity refreshed *something* related when rebuilding these assets (after launching the editor just after deleting them).

Anyway, after deleting project setting assets something happened and the bug was not visible anymore. And it must be something different than just completly deleting and importing Playmaker again as it wasn't helping.

Any ideas what could be related to this error?

I would just add that selected action headline (in the state list on the right side) was highlighted with a dark blue color instead of default light blue. That's another weird thing along the black background.

I'm not sure but as far as I remember many Playmaker UI elements were darker than normally. Elements like errors/no errors indicator, play/pause/next frame buttons etc.

BTW.

Here is a similar topic from 2013, but there is no resolution there:
http://hutonggames.com/playmakerforum/index.php?topic=4557.0
« Last Edit: February 28, 2019, 09:45:59 AM by lukew »

lukew

  • Playmaker Newbie
  • *
  • Posts: 42
Re: Editor Window Default is Pitch Black
« Reply #4 on: February 28, 2019, 03:52:54 PM »
I've just found that it happens when the color space is set to Linear. When I've deleted all setting assets it just created new ones with default set to Gamma, that's why it 'removed' the issue. Anyway, with linear it's still there.

My main project uses Linear space and now I'm wondering if I can update Playmaker in it as it would probably trigger this error there too. Any idea what's the reason of that?

Maybe it won't be happening in new Unity versions. Anyway you always suggest to first update Playmaker and then update Unity. Should I update Playmaker, ignore the issue and update Unity?

My plan was to update Playmaker and Unity to 2018.3 but with this error I'm wondering if I should do it. Could this make some changes in files or somehting that would stay in the project?

---

I've also did a test on a new, empty project.

1. Create new empty project in 2017.1.0.p4
2. Set color space to Linear
2. Install Playmaker 1.9.0.p8 from Asset Store

Result: Playmaker editor is black
Screenshot: https://i.imgur.com/TgvKW0V.jpg

I can switch dynamically between Gamma and Linear and Playmaker becomes dark always when Linear mode is active. With Gamma the window looks fine.

Here is a similar topic on Unity forum, the editor color change look very similar on their screenshots: https://forum.unity.com/threads/regression-in-linear-space-game-scene-editor-are-way-more-dark-from-2017-4-lts-to-unity-2018-2b.528733/

Also, there is a console error that I'm always getting when installing/reimporting Playmaker. I've found some threads on Unity forums, here and some other asset forums with same error. Anyway I'm not sure if it could be related because I'm getting same error when installing Playmaker 1.8.4.f5 which works fine in Linear.

I've already installed Microsoft .NET Portable Library Reference Assemblies 4.6 but error is still visible after installing/reimporting.

Quote
[AssemblyUpdater] Assembly reference folder does not exist: 'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETPortable\v4.6\'
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Mono.Cecil.AssemblyResolutionException: Failed to resolve assembly: 'System.Runtime, Version=4.0.10.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
  at Mono.Cecil.BaseAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name, Mono.Cecil.ReaderParameters parameters) [0x000f7] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.BaseAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name) [0x00007] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.DefaultAssemblyResolver.Resolve (Mono.Cecil.AssemblyNameReference name) [0x00025] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.MetadataResolver.Resolve (Mono.Cecil.TypeReference type) [0x00040] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.ModuleDefinition.Resolve (Mono.Cecil.TypeReference type) [0x00006] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.TypeReference.Resolve () [0x00006] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.Mixin.CheckedResolve (Mono.Cecil.TypeReference self) [0x00000] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.SignatureReader.ReadCustomAttributeEnum (Mono.Cecil.TypeReference enum_type) [0x00000] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.SignatureReader.ReadCustomAttributeElementValue (Mono.Cecil.TypeReference type) [0x0002f] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.SignatureReader.ReadCustomAttributeElement (Mono.Cecil.TypeReference type) [0x00015] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.SignatureReader.ReadCustomAttributeFixedArgument (Mono.Cecil.TypeReference type) [0x00015] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.SignatureReader.ReadCustomAttributeConstructorArguments (Mono.Cecil.CustomAttribute attribute, Mono.Collections.Generic.Collection`1[T] parameters) [0x0002e] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.MetadataReader.ReadCustomAttributeSignature (Mono.Cecil.CustomAttribute attribute) [0x0003c] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.CustomAttribute.<Resolve>b__35_0 (Mono.Cecil.CustomAttribute attribute, Mono.Cecil.MetadataReader reader) [0x00000] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.ModuleDefinition.Read[TItem,TRet] (TItem item, System.Func`3[T1,T2,TResult] read) [0x00029] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.CustomAttribute.Resolve () [0x00017] in <aa9db9129f9d4243a99d025330e76d74>:0
  at Mono.Cecil.CustomAttribute.get_ConstructorArguments () [0x00000] in <aa9db9129f9d4243a99d025330e76d74>:0
  at AssemblyUpdater.Steps.MoveToNamespace.Visit (Mono.Cecil.CustomAttribute customAttribute, Unity.Cecil.Visitor.Context context) [0x000a5] in <fc8204afd8f44ddfb3725526ef3671e2>:0
  at Unity.Cecil.Visitor.Visitor.Visit (Mono.Cecil.TypeDefinition typeDefinition, Unity.Cecil.Visitor.Context context) [0x00042] in <a2988452bd13497f8d7a464ae6072554>:0
  at Unity.Cecil.Visitor.Visitor.Visit (Mono.Cecil.ModuleDefinition moduleDefinition, Unity.Cecil.Visitor.Context context) [0x00024] in <a2988452bd13497f8d7a464ae6072554>:0
  at Unity.Cecil.Visitor.Visitor.Visit (Mono.Cecil.AssemblyDefinition assemblyDefinition, Unity.Cecil.Visitor.Context context) [0x00024] in <a2988452bd13497f8d7a464ae6072554>:0
  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00038] in <a90417619fac49d5924050304d0280bb>:0
   --- End of inner exception stack trace ---
  at System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) [0x00053] in <a90417619fac49d5924050304d0280bb>:0
  at System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) [0x00000] in <a90417619fac49d5924050304d0280bb>:0
  at Unity.Cecil.Visitor.Visitor.Visit[T] (T node, Unity.Cecil.Visitor.Context context) [0x00038] in <a2988452bd13497f8d7a464ae6072554>:0
  at Unity.Cecil.Visitor.Extensions.DoAccept[T] (T definition, Unity.Cecil.Visitor.Visitor visitor) [0x0001e] in <a2988452bd13497f8d7a464ae6072554>:0
  at Unity.Cecil.Visitor.Extensions.Accept (Mono.Cecil.AssemblyDefinition assemblyDefinition, Unity.Cecil.Visitor.Visitor visitor) [0x00001] in <a2988452bd13497f8d7a464ae6072554>:0
  at AssemblyUpdater.Steps.AssemblyUpdaterStepBase.Apply (AssemblyUpdater.Core.AssemblyUpdaterContext context) [0x00013] in <fc8204afd8f44ddfb3725526ef3671e2>:0
  at AssemblyUpdater.Core.AssemblyUpdaterPipeline.RunUpdateRound (AssemblyUpdater.Core.AssemblyUpdaterContext context) [0x00036] in <fc8204afd8f44ddfb3725526ef3671e2>:0
  at AssemblyUpdater.Core.AssemblyUpdaterPipeline.Run (AssemblyUpdater.Core.AssemblyUpdaterContext context) [0x00009] in <fc8204afd8f44ddfb3725526ef3671e2>:0
  at AssemblyUpdater.Application.Program.CheckForObsoleteAPIUsage (AssemblyUpdater.Application.CommandLineSpec config) [0x0008c] in <fc8204afd8f44ddfb3725526ef3671e2>:0
  at AssemblyUpdater.Application.Program.Main (System.String[] args) [0x00057] in <fc8204afd8f44ddfb3725526ef3671e2>:0
UnityEditor.Scripting.APIUpdaterHelper:DoesAssemblyRequireUpgrade(String)
« Last Edit: February 28, 2019, 06:35:56 PM by lukew »

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 3987
  • Official Playmaker Support
    • LinkedIn
Re: Editor Window Default is Pitch Black
« Reply #5 on: February 28, 2019, 07:25:49 PM »
Good catch with the color space. I'll post an update to fix this shortly...

I don't think the error is related, but I'll investigate.


lukew

  • Playmaker Newbie
  • *
  • Posts: 42
Re: Editor Window Default is Pitch Black
« Reply #6 on: February 28, 2019, 10:01:39 PM »
Hey Alex,

Great to hear that you are investigating this error.

Do you think that it's related to using older versions of Unity like 2017.1 or 5 with latest Playmaker versions?

I've updated Playmaker to the latest version in my main project, but it uses 2017.1.0.p4 so te color change error is visible.

I want to upgrade Unity to 2018.3. Would this error dissapear in Unity 2018.3 if Playmaker version in my project is 1.9.0.p8?

I'm wondering if I should wait for a fix and then upgrade Unity or maybe it's fine to upgrade it now without waiting for fix.

Is there any reason that I should not upgrade Unity to 2018.3 (from 2017.1) now while I already have Playmaker 1.9.0.p8 installed with visible "editor color error"?
« Last Edit: February 28, 2019, 10:05:48 PM by lukew »

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 3987
  • Official Playmaker Support
    • LinkedIn
Re: Editor Window Default is Pitch Black
« Reply #7 on: March 01, 2019, 12:19:55 AM »
I just uploaded 1.9.0.p9. It should fix the color errors in all versions of Unity.

If you update to 2018.3, be sure to update PlayMaker in the Asset Store to get the proper version for 2018.3. The asset store can be a little buggy when switching Unity versions: https://hutonggames.com/playmakerforum/index.php?topic=20096.0

lukew

  • Playmaker Newbie
  • *
  • Posts: 42
Re: Editor Window Default is Pitch Black
« Reply #8 on: March 01, 2019, 12:31:51 AM »
Thanks for the fix!

Quote
If you update to 2018.3, be sure to update PlayMaker in the Asset Store to get the proper version for 2018.3

Are there different versions of same Playmaker version for specific Unity versions?

If I would upgrade do 1.9.0.p9 now (on Unity 2017.1.0.p4) via the Asset Store and then I will upgrade Unity do 2018.3, do I need to reinstall Playmaker 1.9.0.p9 from the Asset Store again?

I'm wondering if it's true as you always recommend to upgrade Playmaker before upgrading Unity, so what would be the reason of that if additional update is required after Unity upgrade.

Please let me know how it works. Sorry for any inconvenience.
« Last Edit: March 01, 2019, 12:33:59 AM by lukew »

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 3987
  • Official Playmaker Support
    • LinkedIn
Re: Editor Window Default is Pitch Black
« Reply #9 on: March 01, 2019, 01:00:12 AM »
There are versions of PlayMaker uploaded for Unity 5.3, 5.4, 2017.1 and 2018.3.

So if you update from 2017.1 to 2017.4 you don't need to update PlayMaker since they use the same version of PlayMaker.

But if you update from 2017.1 to 2018.3 you need to update PlayMaker since they use different versions.

Make sure you update and then install from the Welcome Screen: https://hutonggames.fogbugz.com/f/page?W11

I've added a section to the Installation page about updating Unity. Let me know if it's clear!
« Last Edit: March 01, 2019, 01:01:53 AM by Alex Chouls »

lukew

  • Playmaker Newbie
  • *
  • Posts: 42
Re: Editor Window Default is Pitch Black
« Reply #10 on: March 01, 2019, 01:13:22 AM »
Ok, got it!

I've just upgraded Playmaker to 1.9.0.p9 on Unity 2017.1 and the dark UI bug is gone!

So, now I will be upgrading Unity to 2018.3. As far as I understand, after upgrade to 2018.3 is done, I would need to  redownload Playmaker from the Asset Store in Unity 2018.3 (I'm deleting cache Asset Store files for this, so it would download proper version) and install 1.9.0.p9 again? Is it right?

So in this case 1.9.0.p9 will override 1.9.0.p9 but actually the 2018.3 version of this release will override 2017.1 version of this release (1.9.0.p9).

Is it a proper way of doing this?

« Last Edit: March 01, 2019, 01:16:02 AM by lukew »

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 3987
  • Official Playmaker Support
    • LinkedIn
Re: Editor Window Default is Pitch Black
« Reply #11 on: March 01, 2019, 01:16:48 AM »
Yes. As always backup your project first!

EDIT: If your project has errors after updating Unity, the Welcome Window may not show automatically. If you need to, you can manually import PlayMaker from: Assets/PlayMaker/Editor/Install after updating in the Asset Store.
« Last Edit: March 01, 2019, 01:20:01 AM by Alex Chouls »

lukew

  • Playmaker Newbie
  • *
  • Posts: 42
Re: Editor Window Default is Pitch Black
« Reply #12 on: March 01, 2019, 01:24:00 AM »
Thanks for the clarification and all answers!

BTW. Is it normal that Playmaker could override template assets just after opening them in newer versions of Playmaker? I can see in the version control that templates are changed after opening them.

I assume that they are updated to the actual version of Playmaker because of some changes in its core or actions code.

Alex Chouls

  • Administrator
  • Hero Member
  • *****
  • Posts: 3987
  • Official Playmaker Support
    • LinkedIn
Re: Editor Window Default is Pitch Black
« Reply #13 on: March 01, 2019, 10:35:16 AM »
Yeah, updating PlayMaker can cause templates to be updated. If you want to double check the differences you could use force text serialization in your project and do a diff on the file when you commit changes.

lukew

  • Playmaker Newbie
  • *
  • Posts: 42
Re: Editor Window Default is Pitch Black
« Reply #14 on: March 02, 2019, 11:29:05 AM »
Hey Alex,

I was using 2017.1.0.p4 with Playmaker 1.9.0.p9 (which fixed the dark editor bug in linear) before the update.

Now I've updated Unity to 2018.3.6f1 and then downloaded Playmaker 1.9.0.p9 from the Asset store (after deleting the cache/package from the Asset Store cache) to to get the 2018.3 version as it's suggested.

After importing it from the Asset Store and installing it from the Playmaker Home Screen everything went fine. Anyway, the editor is now very bright. This looks same as before, but now it's bright instead of dark.

Here is the screenshot (this is default theme with black background): https://i.imgur.com/PU7vj67.jpg

I've just checked it in empty project on 2018.3.6f1. Downloaded Playmaker 1.9.0.p9 from the Asset Store (after deleting Asset Store cache files again) and it looks same. Editor is very bright.

I assume that it could be fixed somehow by you like with the previous case. Anyway I'm wondering if it's safe to use Playmaker now (running the game in play mode, opening and editing templates, editing fsms etc.) when the editor is 'bright'?

I've updated whole project (30GB) and it took 10+ hours with making backups, starting it with the new version etc. and I'm wondering if it's fine to work now or if I would need to revert the project to backup version and 2017.1.0.p4  (which wouldn't be handy and would take a lot of time).
« Last Edit: March 02, 2019, 11:59:07 AM by lukew »