Jump to content

[1.6.x] RasterPropMonitor - Development Stopped (v0.30.6, 29 December 2018)


MOARdV

Recommended Posts

  On 4/21/2016 at 4:40 PM, HebaruSan said:

Thanks! That's a step in the right direction, but the displays show up as solid blocks of purple instead of drawing shapes and letters. I tried deleting ModuleManager.ConfigSHA and ModuleManager.ConfigCache in case there was some weird caching, and no luck.

rhW6xGY.png

What's the right place to report this packaging issue? Should I check in with the folks on the CKAN threads?

Expand  

I'm having the same problem.

Link to comment
Share on other sites

HebaruSan and _Krieger_, what's your JSI folder contents? There should be four folders, namely Agencies, JSIAdvTransparentPods, RasterPropMonitor and RPMPodPatches. I tried to reinstall RPM with CKAN again and now it installs only one folder - RasterPropMonitor (GameData/JSI/RasterPropMonitor).

Edited by AlexSheFF
Some fixes
Link to comment
Share on other sites

  On 4/21/2016 at 5:47 PM, AlexSheFF said:

http://forum.kerbalspaceprogram.com/index.php?/profile/156657-hebarusan/ and http://forum.kerbalspaceprogram.com/index.php?/profile/160353-_krieger_/ what's your JSI folder contents? There should be four folders, namely Agencies, JSIAdvTransparentPods, RasterPropMonitor and RPMPodPatches. I tried to reinstall RPM with CKAN again and now it installs only one folder - RasterPropMonitor (GameData/JSI/RasterPropMonitor).

Expand  

I have:

  Reveal hidden contents

 

Link to comment
Share on other sites

@HebaruSan - it looks like the font shaders are not being loaded for you.  I'd like to get a log with some debugging info included - please go to JSI/RasterPropMonitor/Plugins/rpm-config.cfg and change the 'DebugLogging = False' to 'DebugLogging = True'.  Once you do that, start the game and enter an IVA with MFDs.  You can then exit.  Post (KSPinstall)/KSP.log somewhere where I can download it so I can confirm my suspicions.

Link to comment
Share on other sites

It seems the issue with the blank grey areas has been resolved. I just went to CKAN and saw that RasterPropMonitor had an update. I installed them through CKAN and then ran KSP. The RPM screens showed up this time and everything seems to be working fine.

Link to comment
Share on other sites

  On 4/21/2016 at 6:10 PM, MOARdV said:

@HebaruSan - it looks like the font shaders are not being loaded for you.  I'd like to get a log with some debugging info included - please go to JSI/RasterPropMonitor/Plugins/rpm-config.cfg and change the 'DebugLogging = False' to 'DebugLogging = True'.  Once you do that, start the game and enter an IVA with MFDs.  You can then exit.  Post (KSPinstall)/KSP.log somewhere where I can download it so I can confirm my suspicions.

Expand  

Sorry for the delay, I did a little mod pruning to clean up the log somewhat, as GCMonitor, SCANsat, and KER were raising suspicious-looking errors. Removing them didn't change anything, though. I don't see anything that looks like a shader problem, but it could be that I don't know where to look.

[LOG 13:27:31.223] Shader: Found embedded shader JSI.Shaders.RPM-DisplayShader-compiled.shader - valid
[LOG 13:27:31.005] Shader: Found embedded shader JSI.Shaders.RPM-FontShader-compiled.shader - valid

http://termbin.com/1r51
 

Link to comment
Share on other sites

  On 4/21/2016 at 6:47 PM, HebaruSan said:

Sorry for the delay, I did a little mod pruning to clean up the log somewhat, as GCMonitor, SCANsat, and KER were raising suspicious-looking errors. Removing them didn't change anything, though. I don't see anything that looks like a shader problem, but it could be that I don't know where to look.

[LOG 13:27:31.223] Shader: Found embedded shader JSI.Shaders.RPM-DisplayShader-compiled.shader - valid
[LOG 13:27:31.005] Shader: Found embedded shader JSI.Shaders.RPM-FontShader-compiled.shader - valid

http://termbin.com/1r51
 

Expand  

No, it looks like RPM thinks the shader is up and running just fine, but the pink is typically a "missing shader" placeholder.  Unless there's something in the *NIX flavors of Unity that are causing my shaders to fail to load, and Unity's giving me its placeholder instead.

Sorry, I don't have an answer yet.

Link to comment
Share on other sites

  On 4/21/2016 at 9:27 PM, PhoenixStar117 said:

Hey, for anyone having the pink screen issues like myself, FIXED IT! At least for me. My fix was removing my little "-force-opengl" from the Steam startup settings. Once it was removed, the screens began to work just fine.

Expand  

I don't use Steam and i still have the pink bars 

Link to comment
Share on other sites

I haven't played KSP in a while, so have skipped a few versions, but with this latest update I'm not seeing as much information on my primary screen as I'm used to. On the left Side it says "SAS :" and "RCS :" but doesn't tell me whether they are active or not. And "Throttle :" used to display the states of my throttle (0-100%) but now doesn't. Same goes for Gear, Brakes and Lights on the right. Any body else experiencing this? I did a manual install (no CKAN) on a fresh install of ksp.

 

RPM_Bug_zpsrlqlzwbx.png

Link to comment
Share on other sites

  On 4/21/2016 at 10:29 PM, edemlama said:

I don't use Steam and i still have the pink bars 

Expand  

Well, perhaps there is a separate setting in the stock game launcher or in a text settings file somewhere in the directory to turn off openGL (but I am no expert, nor even close a proper programmer so don't take my word on it; and I haven't used the stock game since 0.25).

Link to comment
Share on other sites

  On 4/21/2016 at 11:33 PM, carranty said:

I haven't played KSP in a while, so have skipped a few versions, but with this latest update I'm not seeing as much information on my primary screen as I'm used to. On the left Side it says "SAS :" and "RCS :" but doesn't tell me whether they are active or not. And "Throttle :" used to display the states of my throttle (0-100%) but now doesn't. Same goes for Gear, Brakes and Lights on the right. Any body else experiencing this? I did a manual install (no CKAN) on a fresh install of ksp.

 

 

Expand  

Get the latest version (v0.25.0 hotfix 36940) from GitHub.  I found that bug just a short while after the v0.25.0 release.

Link to comment
Share on other sites

Getting grey screens after repeated re-installations and updates.  Tried the hotfix and still getting grey screens.  Tried running in 32 bit as well.  Not sure what's causing it anymore.

http://images.akamai.steamusercontent.com/ugc/271715738869535256/89BA13ECC5E430E9FB0952A0CFA628CCE84E50BB/

My output log file for 64-bit:

https://www.dropbox.com/s/qv8jmag8ah89xpn/output_log.txt?dl=0

Mods I have installed:

  • [x]Science!
  • Asteroid Day
  • Chatterer
  • Contrace Configurator
  • Contract Parser
  • Contract Window +
  • Distant Object Enhacement
  • Docking Port Alignment Indicator
  • Endurance
  • Engine Light (out of date)
  • Kerbal Engineer Redux
  • Kerbal Inventory System
  • Kerbal Attachment System
  • Module Manager
  • PlanetShine
  • Precise Node
  • Real Plume (with stock configs)
  • SCANSat
  • Scatterer
  • SmokeScreen
  • Waypoint Manager
Link to comment
Share on other sites

  On 4/22/2016 at 2:23 AM, MOARdV said:

Get the latest version (v0.25.0 hotfix 36940) from GitHub.  I found that bug just a short while after the v0.25.0 release.

Expand  

Ah, that sorted it, working fine now. Thank you!

  On 4/22/2016 at 10:25 AM, Nittany Tiger said:

Getting grey screens after repeated re-installations and updates.  Tried the hotfix and still getting grey screens.  Tried running in 32 bit as well.  Not sure what's causing it anymore.

 

Expand  

If it helps, I have

  • Chatterer
  • Docking Port Alignment Indicator
  • Kerbal Inventory System
  • Kerbal Attachment System
  • Module Manager
  • PlanetShine
  • SCANSat

installed and RPM works fine. Running 64bit ksp on windows 10.

Link to comment
Share on other sites

  On 4/22/2016 at 10:25 AM, Nittany Tiger said:

Getting grey screens after repeated re-installations and updates.  Tried the hotfix and still getting grey screens.  Tried running in 32 bit as well.  Not sure what's causing it anymore.

http://images.akamai.steamusercontent.com/ugc/271715738869535256/89BA13ECC5E430E9FB0952A0CFA628CCE84E50BB/

My output log file for 64-bit:

https://www.dropbox.com/s/qv8jmag8ah89xpn/output_log.txt?dl=0

Mods I have installed:

  • [x]Science!
  • Asteroid Day
  • Chatterer
  • Contrace Configurator
  • Contract Parser
  • Contract Window +
  • Distant Object Enhacement
  • Docking Port Alignment Indicator
  • Endurance
  • Engine Light (out of date)
  • Kerbal Engineer Redux
  • Kerbal Inventory System
  • Kerbal Attachment System
  • Module Manager
  • PlanetShine
  • Precise Node
  • Real Plume (with stock configs)
  • SCANSat
  • Scatterer
  • SmokeScreen
  • Waypoint Manager
Expand  

You've got at least one mod that's out of date (not updated to KSP 1.1, that is), and it's spamming the error log with exceptions.  When a mod does that, all bets are off about whether other mods will even work.  You will need to remove out of date mods - any mod that has a DLL included with it that has not been specifically updated to KSP 1.1 is suspect.  I suspect Engine Light, for instance, manipulates meshes, and that interface changed under the hood, so it's guaranteed not to work in KSP 1.1, and if the DLL is still there, it's going to to Bad Things.

Link to comment
Share on other sites

  On 4/22/2016 at 12:06 PM, MOARdV said:

You've got at least one mod that's out of date (not updated to KSP 1.1, that is), and it's spamming the error log with exceptions.  When a mod does that, all bets are off about whether other mods will even work.  You will need to remove out of date mods - any mod that has a DLL included with it that has not been specifically updated to KSP 1.1 is suspect.  I suspect Engine Light, for instance, manipulates meshes, and that interface changed under the hood, so it's guaranteed not to work in KSP 1.1, and if the DLL is still there, it's going to to Bad Things.

Expand  

I am experiencing the pink screen issue and grey screen issues with no outofdate mod on OS X. I haven't had time to check my win10 install. I can do this test for you tonite (after work) un modded w raster OS X. Modded with raster OS X. Unmodded with raster win10. Modded w raster win10 and send you screenshots. Also this might help but I currently have no screenshot. I clicked on the different buttons and surprisingly, docking port alignment indicator displayed correctly, all the others retain the issue. 

Link to comment
Share on other sites

  On 4/22/2016 at 12:06 PM, MOARdV said:

You've got at least one mod that's out of date (not updated to KSP 1.1, that is), and it's spamming the error log with exceptions.  When a mod does that, all bets are off about whether other mods will even work.  You will need to remove out of date mods - any mod that has a DLL included with it that has not been specifically updated to KSP 1.1 is suspect.  I suspect Engine Light, for instance, manipulates meshes, and that interface changed under the hood, so it's guaranteed not to work in KSP 1.1, and if the DLL is still there, it's going to to Bad Things.

Expand  

 

Turns out it was a mod conflict, but it wasn't Engine Light.

I suspect it was Stock Bug Fixes, but I can't be for sure.

I uninstalled Engine Light and it didn't fix the bug.

I did uninstall Chute Safety Indicator, Stock Bug Fixes, and Asteroid Day, and all of the bugs I was experiencing including this bug vanished (I was also having decouplers emit smoke).  Since I had no craft using Asteroid Day parts in flight, I assume it was either Chute Safety Indicator or Stock Bug Fixes.

Either way, the problem's solved and RPM is working again. :)

Thanks for your help.

Link to comment
Share on other sites

  On 4/22/2016 at 12:35 PM, Rafael acevedo said:

I am experiencing the pink screen issue and grey screen issues with no outofdate mod on OS X. I haven't had time to check my win10 install. I can do this test for you tonite (after work) un modded w raster OS X. Modded with raster OS X. Unmodded with raster win10. Modded w raster win10 and send you screenshots. Also this might help but I currently have no screenshot. I clicked on the different buttons and surprisingly, docking port alignment indicator displayed correctly, all the others retain the issue. 

Expand  

I would definitely try at least OS X without mods and see if it works.  The other possibility is that I have too narrow of a selection of shader modes, such that some *nix flavors aren't finding a defined mode, and they're falling back to the generic "no shader" shader.  I can make a test build to see if that's it, but I'd need it tested, since I can't reproduce the failure (I'm strictly Windows).

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...