Have you updated Fungus to the latest version?
Hi wolfrug good question... I'm using fungus 3.8. Do you know anyone else using fungus with unity 2018 yet? If it's working fine for someone else part of me wonders if I have some old components floating around in my assets for some reason... Before upgrading I was using 2017 .3 with fungus version 3.8. when I update my Unity to 2018 I begin getting the error. Thanks as always for any help and insight! -Eric
https://forum.unity.com/threads/two-things-i-found-right-off.511999/ Here's an issue about the same thing. There's an answer in the last post that might help you (I'm assuming you'll need to edit the code for that), but it's not a big thing :)
Thank you Wolfrug, that worked perfectly, my game is back up and running! One follow-up question: knowing that (likely) everyone will have that issue when they move up to 2018 do I need to formally file that as a bug report or something similar? -Eric
Not exactly sure how you're getting that in 3.8. Chris submitted a change that handles it. In any event, I've forced a line change in that file, among some other minor 2018.1 changes.
I missed your reply earlier Steve, thank you! BTW, considering your thought here further: is there a post/best practice for a good way to confirm which version I'm using? I always try to keep up to date by going to the asset store and download/importing each new version. Is there a chance I have old components floating around? If so what's the cleanest way for me to keep up to date? Thank you!