Black screen in Visionaire Player after latest update

  • #10, by afrlmeWednesday, 24. October 2018, 21:44 2 years ago
    Any errors mentioned in the log? After you've run the game via the editor, go to the bit on the toolbar with the 2 play button icons & hover over them. Select "messages.log" & it will open up the folder where the log for the game is saved.

    Or you can check the log while running the game via the editor by pressing TAB to open up the developer console & clicking on the log option.

    Alternatively, if you are using multiple screens then you could use this method to display a live updating version of the log while you are running the game.

    Imperator

    6932 Posts


  • #11, by davide-civelliFriday, 26. October 2018, 09:31 2 years ago
    Any errors mentioned in the log? After you've run the game via the editor, go to the bit on the toolbar with the 2 play button icons & hover over them. Select "messages.log" & it will open up the folder where the log for the game is saved.

    Or you can check the log while running the game via the editor by pressing TAB to open up the developer console & clicking on the log option.

    Alternatively, if you are using multiple screens then you could use this method to display a live updating version of the log while you are running the game.

    Hello again! I include a short part of the log file that the game produce. There are many shader errors. Obviously before updating Visionaire the game run without any problem (I don't know how to link a .log file, sorry!)

    9:27:27.413:Failed to run string in Lua:  
    9:27:27.413:String content: local eff="tv2" 
    shaderAddEffect(eff)  
    shaderRemoveEffect(eff) 
    shader_effects[eff].num.strength=1  
    bind(eff, "time", field("shader_iTime"))  
    Objects.tv.ShaderSet = shader_effects[eff].num() 
    9:27:27.512:Failed to run string in Lua:  
    9:27:27.512:String content: read_ini() 
    9:27:27.513:Failed to run string in Lua:  
    9:27:27.513:String content: shaderBlur(2, 0) 
    shaderLightness(-1, 0) 
    9:27:27.596:Failed to execute hook function 'shaderMain':  
    9:27:27.605:Failed to execute hook function 'shaderMain':  
    9:27:27.614:Failed to execute hook function 'shaderMain':  
    9:27:27.631:Failed to execute hook function 'shaderMain':  
    9:27:27.647:Failed to execute hook function 'shaderMain':  
    9:27:27.663:Failed to execute hook function 'shaderMain':  
    9:27:27.682:Failed to execute hook function 'shaderMain':  
    9:27:27.698:Failed to execute hook function 'shaderMain':  
    9:27:27.713:Failed to execute hook function 'shaderMain':  
    9:27:28.730:Failed to execute hook function 'shaderMain': 

    Newbie

    19 Posts

  • #12, by afrlmeFriday, 26. October 2018, 11:01 2 years ago
    Can you try disabling the shader toolkit script by unticking the definition checkbox button please?

    Out of curiosity, have you only just recently upgraded? Simon updated the shader toolkit script recently so it could be possible that you still have the old version. Here's the new shader toolkit: https://www.visionaire-studio.com/luadocs/downloads/shadersc...

    Also Lua version was updated from 5.1 to 5.3 & some of the functions/operators that were available in 5.1, such as table.maxn are now deprecated.


    There are links on the 2 pages that I just linked that list incompatibilities.

    Imperator

    6932 Posts

  • #13, by davide-civelliMonday, 29. October 2018, 09:26 2 years ago
    Can you try disabling the shader toolkit script by unticking the definition checkbox button please?

    Out of curiosity, have you only just recently upgraded? Simon updated the shader toolkit script recently so it could be possible that you still have the old version. Here's the new shader toolkit: https://www.visionaire-studio.com/luadocs/downloads/shadersc...

    Also Lua version was updated from 5.1 to 5.3 & some of the functions/operators that were available in 5.1, such as table.maxn are now deprecated.


    There are links on the 2 pages that I just linked that list incompatibilities.

    Ok, I resolve it, after your last message: I updated the shaders and the problem is gone!
    Thank you for the tips

    Newbie

    19 Posts

Write post