mirror of
https://github.com/hrydgard/ppsspp.git
synced 2026-04-25 22:26:04 +03:00
[GH-ISSUE #3979] Macross Ultimate and Triangle frontier #1615
Labels
No labels
Atrac3+
Audio
CPU emulation
D3D11
D3D9 (removed)
Depth / Z
Feature Request
Font Atlas
GE emulation
Guardband / Range Culling
HLE/Kernel
I/O
Input/Controller
MP3
Multithreading
Needs hardware testing
Networking/adhoc/infrastructure
No Feedback / Outdated?
OpenGL
PGF / sceFont
PSMF / MPEG
Platform-specific (Android)
Platform-specific (Windows)
Platform-specific (iOS)
PowerVR GPU
SDL2
Saving issue
User Interface
Vulkan
arm64jit
armjit
armv6
x86jit
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ppsspp#1615
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Gary1234567 on GitHub (Sep 29, 2013).
Original GitHub issue: https://github.com/hrydgard/ppsspp/issues/3979
Hi
Macross Ace Frontier is working perfectly after V091-1013 build even water is displayed nicely.No issues with build and this game is now perfect.
Macross Ultimate and Triangle Frontier still had random freezing issues and black boxes arround the thrusters but is no longer able to open or load after build 1187 if I am correct.
Macross Ace Frontier still works like a charm even with the latest build of 29/9/13
Please fix
Thanks for emulator.
@unknownbrackets commented on GitHub (Sep 29, 2013):
Do you mean v0.9.1-1187-gff8c6ba? Can you check the last version that worked and the first version that stopped working? There are several in between those versions, and narrowing it down would help a lot.
-[Unknown]
@papel commented on GitHub (Sep 29, 2013):
The bugs in Ace Frontier are:
@Gary1234567 commented on GitHub (Sep 29, 2013):
Hi
v0.9.1-1074-ga1f3591 Macross Ultimate and Triangle Frontier loaded and playable (random freezing and black boxes arround thrusters) but v0.9.1-1187-gff8v6ba none of these 2 games loaded and only shows black screen up to latest build I have been checking each build each day and none worked so far.
All graphic glitches have been solved with latest built for Macross Ace Frontier and game works and looks flawless.
Problem started with build of between 20 - 23 Sept 2013
Sorry I cant be more specific as I missed some builds
Gary
@Gary1234567 commented on GitHub (Sep 29, 2013):
Downloading older builds between 1107 and 1187 to find broken build will come back with built that broke these games.
@Gary1234567 commented on GitHub (Sep 29, 2013):
ppsspp-v0.9.1-1106-g01def3b-windows-x86 - Worked loading
No build to download between
ppsspp-v0.9.1-1112-g74f58ed-windows-x86 - Stopped working or laoding only black screen
Hopes this helps.
@Gary1234567 commented on GitHub (Sep 29, 2013):
ppsspp-v0.9.1-1106-g01def3b-windows-x86 Games not stable random freeze and save problems altough Ultimate Frontier more stable and playable graphic problem with black boxes arround thrusters still giving problem and large explosions render in a triangle form instead of round.Last problem with large explosion is fixed in Ace Frontier game.
Gary
@unknownbrackets commented on GitHub (Sep 29, 2013):
Is it affected by multithreaded, like #3883?
-[Unknown]
@Gary1234567 commented on GitHub (Sep 30, 2013):
Yes when I select multithreaded with JIT the game loads but stops after 10 second with a freezed screen if i deselect multithread i only get black screen,
Ace Frontier is not affected by this only Macross Ultimate and Triangle Frontier
@dbz400 commented on GitHub (Oct 5, 2013):
@Gary1234567 , if you simply comment out CoreTiming::ForceCheck() , work okay ?
@dbz400 commented on GitHub (Oct 5, 2013):
Alright .I just tested it and worked okay in multithread mode .Therefore it is the same issue as #3883

@unknownbrackets commented on GitHub (Oct 5, 2013):
Are you sure you meant #3887?
-[Unknown]
@dbz400 commented on GitHub (Oct 5, 2013):
Typo .#3883 should be whihc is CoreTiming::ForceCheck() in sceGeListUpdateStallAddr()
@shadowviper23 commented on GitHub (Oct 7, 2013):
@raven02 sorry i'm new to all this, how does one actually apply this fix you have posted? is it something we can apply or do we have to wait till its in a release? i would love to be able to get macross triangle frontier working if it is possible
@dbz400 commented on GitHub (Oct 8, 2013):
That one is not proper fix and you have to wait or use old build which work for this game.
@shadowviper23 commented on GitHub (Oct 8, 2013):
@raven02 arlight then, i just never found a build that did not freeze after 3-5 minutes, what build should i look for? i dont mind small artifacts like the blocks around thrusters so much. but i dont want to freeze always. if there is no build that does that then i will just wait and keep an eye out on this thread
@dbz400 commented on GitHub (Oct 9, 2013):
So far i tested even though CoreTiming::Advance() , it still freeze after a while as well as multithread mode .Only the following is okay and no freeze
@shadowviper23 , loosk like old build also freeze .I think you may need to wait for proper fix or compile your own build .
@unknownbrackets commented on GitHub (Oct 9, 2013):
What if you add after in GPUCommon.cpp:
This:
Or something. Does that affect it?
-[Unknown]
@dbz400 commented on GitHub (Oct 9, 2013):
Yep , works prefectly and no freeze
@dbz400 commented on GitHub (Oct 9, 2013):
FF Type-0 also good with this change.
@unknownbrackets commented on GitHub (Oct 9, 2013):
If you take out
CoreTiming::ForceCheck()are they both still happy?That change is very possibly legit, but it could cause problems in single threaded for some games which update the stall address a lot.
What if you do:
Does that still work (it may not, and it could even be less correct, I dunno..)?
-[Unknown]
@dbz400 commented on GitHub (Oct 9, 2013):
Remove CoreTiming::ForceCheck() is also okay
@dbz400 commented on GitHub (Oct 9, 2013):
This bootup okay however gonna freeze after few mins
if (list.pc == list.startpc)
cyclesExecuted += 300;
@unknownbrackets commented on GitHub (Oct 9, 2013):
Okay, if we can't find any games that
cyclesExecuted += 300;causes slowdown for (Legend of Heroes: Trails in the Sky certain areas, Sword Art Online in field, some other games from that time are likely suspects), then that's probably a good change. Probably updating the stall takes a hit on GPU processing anyhow, not sure.-[Unknown]
@dbz400 commented on GitHub (Oct 9, 2013):
Alright .let me have a quick test on those games.
@dbz400 commented on GitHub (Oct 9, 2013):
Tested (Legend of Heroes: Trails in the Sky and Sword Art Online in few scenes and seems to be fine and no slowdown.
@unknownbrackets commented on GitHub (Oct 9, 2013):
Oh, ClaDun X2 as well, I'll try to check it in ~7 hours or so. It will most likely work, I just remember that game had a timing problem (if the list finished too early, though, I think.)
-[Unknown]
@dbz400 commented on GitHub (Oct 9, 2013):
Sure .Hopefully it works well.
@unknownbrackets commented on GitHub (Oct 9, 2013):
Okay, I checked it really quick, it seems fine. I think we can keep the ForceCheck and just add this, it probably makes sense.
-[Unknown]
@shadowviper23 commented on GitHub (Oct 9, 2013):
man i honestly wish i knew what you guys where talking about here... i'd love to be able to help out instead of being a leach. i guess still the only thing i could help with would be tests.
so it seems you might have a fix? i dont know how to compile my own with those changes, do you think they will be pushed soon to the auto compiled/dev releases?
@dbz400 commented on GitHub (Oct 9, 2013):
Thanks @unknownbrackets .Here it is
2cdb2d1@shadowviper23 , you can check again when merged .
@shadowviper23 commented on GitHub (Oct 9, 2013):
hey guys just tested out build 1660 the freeze is gone it seems, though the black boxes around the thrusters are still there, along with i think a lock up it gets trying to save that basically makes the game unplayable, this is an actual game lockup has a message that i can not read with no buttons doing anything. at times there is the usualy emulator freeze for 5-10 seconds though but thats probably nothing. oh and i did not have to run it with multithreading turned on, this worked on a fresh non tuned ppsspp 1660.
I will try gundam battle universe and assault survive, the other two games that had the freeze in a little while and see if they run great
@SOMEGUY789 commented on GitHub (Oct 14, 2013):
Yup I can confirm the above. Whenever the game tries to save or load it hangs on the loading or saving message.
@shadowviper23 commented on GitHub (Oct 14, 2013):
yup i still have the same issues, Ultimate frontier runs fine, save for the black boxes around thrusters still, but its playable.. however triangle has that major freeze upon trying to save after a mission, and since the game uses mandatory autosave it freezes every mission with no way around it.
gundam battle universe now properly works also i did test that one aswell... didnt notice any graphical issues on it either, so the boxes seem to be for just the macross ultimate and triangle frontiers.
@raven02 and @unknownbrackets , if you two or anyone else have some time to look into these issues it would be great, i can help you anyway that i might could, with log files or anything (just need a brief shakedown on what files) just let me know and i will get them to you. also.. should we reopen this or create a new? would love if we could get the save freeze to stop, and of course also the thruster boxes to go away but that's a secondary issue. for this title
@SOMEGUY789 commented on GitHub (Oct 17, 2013):
@shadowviper23
I'd wait a few days and if no one reopens this make a new thread or add to an existing one. I've looked and the other threads for these games are all closed save for two which are dealing with this issue so you may want to post in them.
@shadowviper23 commented on GitHub (Oct 17, 2013):
hmm i couldnt find those threads
@SOMEGUY789 commented on GitHub (Oct 18, 2013):
#2702 and #1231 these two, I meant to say issues.