Conversation

Notices

1. Kawaoneechan (kawa@mas.to)'s status on Wednesday, 27-Dec-2023 06:41:05 JST Kawaoneechan

   An interesting observation: when I run a debug build of #Noxico in #VisualStudio2015, all the debug outputs in a populated town board make the game run very slow, like 20 to 30 FPS. The _exact same build_ running from #VisualStudio2019 updates the exact same town board at a full 60 FPS.

   Running it from outside either IDE also gives 60 FPS for the same board.

   I find that quite interesting. Does anyone have any insights about this?

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Wednesday, 27-Dec-2023 06:41:04 JST Foone🏳️‍⚧️

     in reply to

     @kawa how'd you fix it?

   • Kawaoneechan (kawa@mas.to)'s status on Wednesday, 27-Dec-2023 06:41:05 JST Kawaoneechan

     in reply to

     I have been given a very interesting suggestion and now it runs at a nice 30 something with barely a hitch when running from VS2015.

     I don't understand why, but it does.

   • Kawaoneechan (kawa@mas.to)'s status on Wednesday, 27-Dec-2023 07:06:35 JST Kawaoneechan

     in reply to

     • Foone🏳️‍⚧️

     @foone Originally I had a thin wrapper with the [Debug] attribute that called Console.WriteLine(...). For whatever damn reason, that's slow when running from VS2015's IDE.

     It was suggested to use System.Diagnostics.Trace.WriteLine(...) instead. I *still* have an Output panel full of shit, but for whatever damn reason it runs much smoother. Not as smooth as from outside of the IDE or VS2019, but... yeah.

     Weird, but I'll take it.

   • Foone🏳️‍⚧️ (foone@digipres.club)'s status on Wednesday, 27-Dec-2023 07:06:35 JST Foone🏳️‍⚧️

     in reply to

     @kawa ahh, yeah.
     it's a weird thing: computers are so fucking fast these days, but writing logs to console can STILL be incredibly slow.