Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
UPDATE: Okay now apparently turning on DS4 Windows fixes the issue. I have no idea how to respond to this.
Not the first time this happens, I call it clickteam magic. For no reason the game can start to run like ♥♥♥♥ or fix itself for no reason at all. ♥♥♥♥ me mate.
I don't know if this would help but I found out about a custom exporter for Clickteam Fusion thats called Chowdren. It was used for all of the versions of Freedom Planet IIRC. From what I've read it recompiles Fusion events to C++ which results in better optimization.
http://mp2.dk/chowdren/
http://clickwiki.net/wiki/Chowdren
The first time I ran Spark it was fine. I have a fairly high-end computer, so this is expected. But the second time I ran it - I had similar framerate issues. I was aware of this thread. but I run Windows 8.1 and have a Xbox 360 controller, not Windows 10 and a CronusMax. Despite this, I decided to give it a shot. While I had the game open, I unplugged every USB drive I could and then plugged back in the wireless Xbox 360 controller reciever - this sped up the game, but not to full 60 like I got the first time.
After messing around with my monitor refresh rate and looking at the Device Manager, I decided to restart the computer. Doing this and starting Spark up without any USB gamepad in did the trick. I was able to plug the wireless adaptor in afterwords and the framerate stayed at 60.
It seems that there's some kind of conflict between the way Spark looks for controllers and the USB drivers. It would be great if we could pin down what exactly is going on.