Ah... bummer.E.D.Revolution wrote:Slowing down to a crawl. I'm so busy with real life here that I barely had time to work on the case.
Hope you find time to finish the case. And include even MORE Jeopardy puns!@
Moderators: EN - Forum Moderators, EN - Trial Reviewers
Ah... bummer.E.D.Revolution wrote:Slowing down to a crawl. I'm so busy with real life here that I barely had time to work on the case.
Now it works fine.E.D.Revolution wrote:Until I get home I won't be abe to see the problem. It might be taking too long to load. Try loading the thing again
Oh. I didn't see the edit. I'm going to send you the PM.E.D.Revolution wrote: EDIT: You might have a memory leak. Go to the PyWright main folder and delete the log and last log. Then run the system. Run until it crashes. Send me the crash report (the log and/or last log file) via PM. Also, try to set PyWright.exe as the highest priority when running it, which can be set via task manager.
The customization power of PyWright is unbelievable. If you've played through the PyWright version, you can see that I can customize UIs very well.Domyce432 wrote:I think he changed the engine because PyWright has got:
- Smoother game (AAOfps < PyWrightfps); True 60 fps. Don't have to deal with gif nonsense. Also things load a hell of a lot faster and a hell of a lot more cleanly.
- Custom Engine (I think he means the customized in-game buttons, like the Press Button); This is a neat plus, the custom buttons and whatnot.
- More accurate authenticity; Yes, and I customized the engine to do so.
- Double screen (Just like the original games, but lower screen is customizable); The double screen has its advantages vs the "all evidence on screen" AAO has.
- Easy-looped music; Looping is much cleaner on Py.
- And more stuff I don't know about.
So THAT's why you changed engine.E.D.Revolution wrote:
The customization power of PyWright is unbelievable. If you've played through the PyWright version, you can see that I can customize UIs very well.I have a lot of ideas I want to implement for my series. In my head, I know I can do them on AAO, but I also know it's going to be very messy. When I saw what Py can do, I started to think that I can do this much more seamlessly and cleanly than what I can do on AAO.Spoiler : :
Heck, I was doing a lot of experiments on PyWright to test my ideas. I found a better way to implement Psyche Locks authentically. I have a proven proof-of-concept for implementing Perceive authentically. Both of those standard AA features are already able to be scripted into any PyWright game. But I've rewritten the code for Psyche Locks for authenticity and simplicity (I've mentioned this in the v6 Psyche Locks guide). And the next update for PyWright will include improved Psyche Locks based on my code and assets. Psyche Locks, while much better implemented on v6, has some things that still get to me (this is related to the loading issues).
Anyway, there's a lot of stuff I want to do for ASA that can be done on both systems. I prefer PyWright just due to how much better it is to AAO.