| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 0002010 | Lionheart | [All Projects] General | public | 2009-04-17 10:33 | 2011-06-03 22:33 | ||||||||
| Reporter | Hexaae | ||||||||||||
| Assigned To | JOTD | Project Info | Lionheart (Thalion) http://www.whdload.de/games/Lionheart.html | ||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||||
| Status | closed | Resolution | not fixable | ||||||||||
| Summary | 0002010: Lionheart: Flickering mountains parallax background (start 1st level). | ||||||||||||
| Description | Install: Lionheart (Thalion) http://whdload.de/games/Lionheart.html GameVersion: english,pal,2 disks SlaveVersion: salve 2.1 (07-oct-06) Flickering mountains parallax background (start 1st level). Imperfect music: missing some sounds... | ||||||||||||
| Tags | No tags attached. | ||||||||||||
| Machine | A1200 | ||||||||||||
| CPU | 68040 | ||||||||||||
| CPUSpeed | 75 | ||||||||||||
| ChipSet | AGA | ||||||||||||
| GFXCard | Picasso IV | ||||||||||||
| ChipMem | 2 MB | ||||||||||||
| FastMem | 128 MB | ||||||||||||
| Workbench | OS 3.9 | ||||||||||||
| KickROM | 40 - Kick 3.1 | ||||||||||||
| KickSoft | None | ||||||||||||
| WHDLoad | 16.9 | ||||||||||||
| imported | yes | ||||||||||||
| Attached Files |
| ||||||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
Hexaae (reporter) 2009-05-20 12:25 |
I still confirm these bugs using WinUAE 1.6.0beta or 1.5.4... Can't degrade it properly and background sky or water will flicker depending on what you degrade :( Also music misses some samples if you hear carefully the music in the 1st level or intro. |
|
Retro-Nerd (reporter) 2009-05-20 21:29 |
Press "I" do deactivate the interlaced (and flickering) background. Even the game manual mention it. ;-) |
|
Hexaae (reporter) 2009-05-21 00:10 Last edited: 2009-05-21 00:15 |
C'mon! I'm not so lame! :D I'm not talking about that interlaced flickering but bad parallax flickering of mountains, corrupted clouds, bad water effect... depending how you adjust WUAE slowing it down. Unfortunately I've not been able to get rid of all parallax/water errors even with JIT off, NOCACHE tootlype etc. I still hope JOTD can make a miracle to better temporize those elements referesh on screen. I can't remember if this happened on my real A1200 + B1260@66MHz too... Here is an example with NOCACHE and JIT OFF: http://g.imagehost.org/0141/Immagine_5.jpg Water "flickers" with bad masks... I don't know how to describe it using words =) |
|
Retro-Nerd (reporter) 2009-05-21 00:21 |
I remember we talked about on EAB some time ago. Lionheart had troubles in older WinUAE version (v1.2 or so), but i don't notice any graphic bugs in recent versions, TCD neither. You post imho way too many WHDLoad bug reports about bugs i've never seen in WinUE on my XP PC.I blame your computer. ;-) |
|
Hexaae (reporter) 2009-05-21 00:25 Last edited: 2009-05-21 00:29 |
It depends on what you do with WUAE: if you just load ADFs of games using 1.3Kick + 68000 or if you have emulated a real WB, like me. On the same EAB thread all others but you reported gfx glitches with Lionheart though... :) I'll resume the thread... I forgot about that. I'm curious to hear if for JOTD it's Ok Lionheart with WUAE 1.5.4+ |
|
Retro-Nerd (reporter) 2009-05-21 00:29 Last edited: 2009-05-21 00:31 |
Read it better. It's all fixable. And of course i don't use diskimages. I use ClassicWB for the best compatibility. I used AmiKit and AmigaSYS ages ago. But this modern Amiga setup isn't suitable for WHDLoad games. This Amiga packs uses GFX card, JIT and specific patches. I told you that several times. Toni too. |
|
Hexaae (reporter) 2009-05-21 00:34 Last edited: 2009-05-21 00:45 |
All WHDLoads I have with UAE work fine FYI from an emulated "modern" WB3.9, with a pair of adjustments (JIT off for example, and/or changing immediate blitter etc.). I simply put this tooltype in WHDLoad games: "ExecuteStartup=C:uac-configuration cachesize 0 immediate_blits true" for example to disable JIT and disable immediate blitter. This way you can use a "real" WB and still play great Amiga WHD games better than getting crazy with every custom game adjustment and the ADFs... All but Lionheart! :( What's your settings for Lionheart WHD? I Tried everything, even without loading WB (boot with no SSeq) but doesn't change gfx glitches with Lionehart WHD... I can't belive, sorry, you can play Lionheart WHD without a single gfx glitch ;) I've been able to adjust emulation to make clouds flicker only randomly but still happens sometimes. So I wondered if it is something that with some waitblits etc. can be solved using a WHDLoad slave... |
|
Retro-Nerd (reporter) 2009-05-21 00:55 Last edited: 2009-05-21 01:01 |
Maybe Jotd makes a fix for fast emulated Amigas. I have no problems here with Lionheart in ClassicWB/Gamebase+WHDLoad in the latest WinUAE beta. I have an A1200 with 030 Turbocard, 8 MB Fastram and use the same settings in WinUAE. No JIT, No Graphic card, no FPU. CPU -> Chipset slider 4 steps from the left. Or "Match Amiga 500" speed as Retroplay suggested. |
|
Hexaae (reporter) 2009-05-21 01:19 |
No way. Still gfx glitches. As I already said I tried everything, and obviously also no JIT, Match A500 speed etc. always gfx glitches. Please, can you upload your Lionheart version in the Zone? |
|
Retro-Nerd (reporter) 2009-05-21 01:24 Last edited: 2009-05-21 01:25 |
It's no version issue. I use Killergorilla's preinstalled version. Use ClassicWB/Gamebase for WHDLoad games and Amikit/AmigaSYS for all other Amiga related stuff. THAT is the solution to your problem. Live with it, or use your real Amiga. :-) |
|
Hexaae (reporter) 2009-05-23 17:28 Last edited: 2009-05-23 17:31 |
No it's not as I have ALREADY TESTED it from a WB3.1 (even without running Startup-Sequence) and changing all possible WUAE emulation modes including 020 cpu, no JIT obviously, etc. etc. It still shows gfx issues. Maybe you're lucky and have a slow PC where the problem doesn't show up. Please, stop adding your twitting comments "it works for me". It's not of any help and I've already tested with your suggestions (?). I want JOTD comments only, author of the slave. He will say if the slave has some problems (it could be a blitter emulation speed depending also on the HW) after testings on WUAE. For sure the docs say the slave HAVE BLITTER ISSUES and for sure all other 238 WHDLoad games I tested work fine on the same WUAE. Belive me: it's not me unable to set up WUAE, it's hard to understand Retro-Nerd? |
|
Retro-Nerd (reporter) 2009-05-23 17:35 Last edited: 2009-05-23 17:38 |
It's hard to understand that it works FINE for 3-4 other people, but not for you. Maybe the game has still minor blitter issues, but they are fixable with the latest WinUAE and tweaked settings. And by the way: WHDLoad was made for REAL AMIGAS with hdds. And you know that it works better there. Stop your "game xyz" isn't working properly in WinUAE. Please!!! :-)) |
|
Hexaae (reporter) 2009-05-23 17:44 Last edited: 2009-05-23 17:53 |
Why do you want to use Mantis for trolling? I've simply asked to JOTD. If he cares about WUAE emulation he'll do something, if not he will say simply "don't care" and/or "I can't reproduce them". I know what WHDLoad is made for. I've been a real Amiga user for many years, and you can even see some of contribs in Aminet. I'm a registered WHDLoad user since long time ago who have asked something to the slave's author. This is not a forum and you're not a moderator. Stop adding useless comments (read my first 2 lines above in this msg) and let's wait JOTD comments. |
|
Retro-Nerd (reporter) 2009-05-23 17:52 |
Trolling? Mmh, YOU are the guy who floods this fine mantis tracker with ridiculous bug reports!!!! Anyway, maybe you can annoy JOTD hard enough to fix your "problems". |
|
Hexaae (reporter) 2009-05-23 18:00 |
Your comments are ridiculous and totally useless (if you at least could suggest something more than "it works"...) and you are flooding Mantis. Stupid me who reply to your useless and unhelpful posts like these. |
|
Retro-Nerd (reporter) 2009-05-23 18:06 |
At least i made reports about REAL bugs. What should i add, a WinUAE video clip or what? Go and find some real bugs, like "Illegal instructions" or "resload". |
|
Hexaae (reporter) 2009-05-23 18:16 Last edited: 2009-05-23 19:01 |
I do this already, thanks. No you're just trolling and acting like a moderator offended by what I really don't know... I report bugs that I'm sure and often bloated by your useless comments as you can read here f.e.: http://mantis.whdload.de/view.php?id=2019 where finally JOTD himself confirmed. Don't know why you have to add your unhelpful comments this way and then accuse me I'm flooding... If I'm wrong sometimes I simply apologize and quickly add a comment that says "you can close this bug, I was wrong" so YOUR posts are really useless inflating the Mantis board. Be more constructive at least. I'll stop here, and won't reply your comments anymore, for Mantis' sake, really. |
|
Retro-Nerd (reporter) 2009-05-23 20:19 |
For your sake: This is my last hint, as you obvisously didn't try it: Use the NOVBRMOVE tooltype in a standard WB setup, no JIT. If it doesn't work than it's cleary your PC. The Quitkey doesn't work anymore then. |
|
Hexaae (reporter) 2009-05-23 20:42 Last edited: 2009-05-23 20:51 |
This is your first hint you mean, probably... No honestly didn't try NOVBRMOVE as it makes the WHD installation useless for me since can't exit. I can already play the game with WUAE loading the ADF in Quickstart A500 mode hence the problem reported wasn't "I cannot play Lionheart with WUAE". If I gave you this impression you were wrong. The problem is that this WHD slave as it is now has these gfx glitches problems, mentioned in the doc itself (blitter errors) and NOVBRMOVE results as a "workaround" since you sacrifice one of the best features of WHDLoad (2nd only to the fact that you actually install them on the HD). So thank you but I still consider my report not OT at all. NOVBRMOVE does work (never mentioned by the way, not even on EAB...) and solves all gfx glitches indeed! This is a useful hint (from a tech point of view) for JOTD though, since the problem left in the slave can be in that area... |
|
Retro-Nerd (reporter) 2009-05-23 20:51 Last edited: 2009-05-23 20:56 |
It IS possible to use the quitkey with the NoVBRMove tooltype in WHDLoad games. Some of the WHDLoad patcher said that on EAB some time ago. Unfortunately this doesn't work with the current slave in Lionheart. So yes, it needs a special slave update for WinUAE. And now, peace. :-) btw: you said that you've already tried everything. So i assumed you tried this tooltype too. ;-) |
|
Hexaae (reporter) 2009-05-23 20:55 |
Would be great this kind of solution: not moving the VBR to run fine the game, but with the quitkey option still working. It's a pleasure to observe that after all we have produced something useful. Of course, peace! ;) |
|
JOTD (developer) 2009-05-23 21:25 |
I'm also glad that something positive came out of this discussion. The fact that NOVBRMOVE helps about the problem is interesting, but does not mean anything to me now :( At worst, I can make the game exitable with NOVBRMOVE on easily. But the best fix would be a proper fix. I have to rework this one fully since there are other major problems on it. I'll do my best to make it enjoyable on Amiga and WinUAE |
|
Hexaae (reporter) 2009-05-23 22:02 |
Great! Just for curiosity: but a game exitable with NOVBRMOVE can have some drawbacks (f.e. OS instability when you quit to WB, since we're talking about VBR...)? |
|
JOTD (developer) 2009-05-24 07:15 |
no, the only problem is the necessity to add a proper QUITKEY (required anyway as there are still some 68000 users!!). NOVBRMOVE prevents WHDLoad from checking other stuff (trace mode, mostly) but when the game is already properly cracked, it's not a problem. The TIMEOUT feature (mainly used for testing) does not work either. Restart key won't work, obviously. Apart from that, there is no problem of corruption (not like NOMMU). |
|
JOTD (developer) 2009-08-30 22:58 |
cycle exact blitter does the difference: without it, the sky flickers, with it, display is perfect. WinUAE only bug. Closing it. |
|
JOTD (developer) 2009-08-30 22:59 |
cycle exact in WinUAE works for me |
|
Hexaae (reporter) 2009-08-31 01:34 |
Just tested... much better but there are still gfx glitches when clouds scrolls. Try playing for 1-2 mins the first level. |
|
Hexaae (reporter) 2009-12-18 16:26 |
Nothing new? NOVBRMOVE ttype is the only way to avoid horribly flickering parallax background (sky and/or mountains), but this way you can't quit the game! :( |
|
Hexaae (reporter) 2010-01-11 20:33 |
Cycle exact doesn't solve the problems with WUAE 2.0.1. Just alleviates them a bit but water/sky/mountains still have problems. Can you please provide a NOVBRMOVE but still able to QUIT version? |
|
Hexaae (reporter) 2010-12-09 12:02 Last edited: 2010-12-09 12:31 |
Still nothing new? Have to use NOVBRMOVE (and can't quit back to WB) to make parallax stop flickering in this gorgeous game! :( Exact cycle still have glitches and random flickerings... |
|
haynor666 (reporter) 2011-05-17 19:56 |
Probably you won't see fix. |
|
JOTD (developer) 2011-06-03 22:33 |
Time to close that bug again. Won't be fixed by any other way than the tricks indicated in the thread. Sorry. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-04-21 00:42 | administrator | New Issue | |
| 2009-04-21 00:42 | administrator | Status | new => assigned |
| 2009-04-21 00:42 | administrator | Assigned To | => JOTD |
| 2009-04-21 00:42 | administrator | Machine | => A1200 |
| 2009-04-21 00:42 | administrator | CPU | => 68040 |
| 2009-04-21 00:42 | administrator | CPUSpeed | => 75 |
| 2009-04-21 00:42 | administrator | ChipSet | => AGA |
| 2009-04-21 00:42 | administrator | GFXCard | => Picasso IV |
| 2009-04-21 00:42 | administrator | ChipMem | => 2 MB |
| 2009-04-21 00:42 | administrator | FastMem | => 128 MB |
| 2009-04-21 00:42 | administrator | Workbench | => OS 3.9 |
| 2009-04-21 00:42 | administrator | KickROM | => 40 - Kick 3.1 |
| 2009-04-21 00:42 | administrator | KickSoft | => None |
| 2009-04-21 00:42 | administrator | WHDLoad | => 16.9 |
| 2009-04-21 00:42 | administrator | imported | => yes |
| 2009-05-20 12:25 | Hexaae | Note Added: 0001077 | |
| 2009-05-20 21:29 | Retro-Nerd | Note Added: 0001079 | |
| 2009-05-21 00:10 | Hexaae | Note Added: 0001080 | |
| 2009-05-21 00:11 | Hexaae | Note Edited: 0001080 | |
| 2009-05-21 00:15 | Hexaae | Note Edited: 0001080 | |
| 2009-05-21 00:21 | Retro-Nerd | Note Added: 0001081 | |
| 2009-05-21 00:25 | Hexaae | Note Added: 0001082 | |
| 2009-05-21 00:28 | Hexaae | Note Edited: 0001082 | |
| 2009-05-21 00:29 | Retro-Nerd | Note Added: 0001083 | |
| 2009-05-21 00:29 | Hexaae | Note Edited: 0001082 | |
| 2009-05-21 00:30 | Retro-Nerd | Note Edited: 0001083 | |
| 2009-05-21 00:31 | Retro-Nerd | Note Edited: 0001083 | |
| 2009-05-21 00:31 | Retro-Nerd | Note Edited: 0001083 | |
| 2009-05-21 00:34 | Hexaae | Note Added: 0001084 | |
| 2009-05-21 00:36 | Hexaae | Note Edited: 0001084 | |
| 2009-05-21 00:43 | Hexaae | Note Edited: 0001084 | |
| 2009-05-21 00:45 | Hexaae | Note Edited: 0001084 | |
| 2009-05-21 00:55 | Retro-Nerd | Note Added: 0001085 | |
| 2009-05-21 01:01 | Retro-Nerd | Note Edited: 0001085 | |
| 2009-05-21 01:19 | Hexaae | Note Added: 0001086 | |
| 2009-05-21 01:24 | Retro-Nerd | Note Added: 0001087 | |
| 2009-05-21 01:25 | Retro-Nerd | Note Edited: 0001087 | |
| 2009-05-23 17:28 | Hexaae | Note Added: 0001091 | |
| 2009-05-23 17:31 | Hexaae | Note Edited: 0001091 | |
| 2009-05-23 17:35 | Retro-Nerd | Note Added: 0001092 | |
| 2009-05-23 17:37 | Retro-Nerd | Note Edited: 0001092 | |
| 2009-05-23 17:38 | Retro-Nerd | Note Edited: 0001092 | |
| 2009-05-23 17:44 | Hexaae | Note Added: 0001093 | |
| 2009-05-23 17:45 | Hexaae | Note Edited: 0001093 | |
| 2009-05-23 17:46 | Hexaae | Note Edited: 0001093 | |
| 2009-05-23 17:52 | Retro-Nerd | Note Added: 0001094 | |
| 2009-05-23 17:53 | Hexaae | Note Edited: 0001093 | |
| 2009-05-23 18:00 | Hexaae | Note Added: 0001095 | |
| 2009-05-23 18:06 | Retro-Nerd | Note Added: 0001096 | |
| 2009-05-23 18:16 | Hexaae | Note Added: 0001098 | |
| 2009-05-23 18:17 | Hexaae | Note Edited: 0001098 | |
| 2009-05-23 18:18 | Hexaae | Note Edited: 0001098 | |
| 2009-05-23 18:20 | Hexaae | Note Edited: 0001098 | |
| 2009-05-23 19:01 | Hexaae | Note Edited: 0001098 | |
| 2009-05-23 20:19 | Retro-Nerd | Note Added: 0001099 | |
| 2009-05-23 20:42 | Hexaae | Note Added: 0001100 | |
| 2009-05-23 20:50 | Hexaae | Note Edited: 0001100 | |
| 2009-05-23 20:51 | Retro-Nerd | Note Added: 0001101 | |
| 2009-05-23 20:51 | Hexaae | Note Edited: 0001100 | |
| 2009-05-23 20:55 | Hexaae | Note Added: 0001102 | |
| 2009-05-23 20:56 | Retro-Nerd | Note Edited: 0001101 | |
| 2009-05-23 21:26 | JOTD | Note Added: 0001104 | |
| 2009-05-23 22:02 | Hexaae | Note Added: 0001106 | |
| 2009-05-24 07:15 | JOTD | Note Added: 0001109 | |
| 2009-08-30 22:58 | JOTD | Note Added: 0001416 | |
| 2009-08-30 22:59 | JOTD | Note Added: 0001417 | |
| 2009-08-30 22:59 | JOTD | Status | assigned => resolved |
| 2009-08-30 22:59 | JOTD | Resolution | open => fixed |
| 2009-08-31 01:34 | Hexaae | Note Added: 0001418 | |
| 2009-12-18 16:26 | Hexaae | Note Added: 0001612 | |
| 2009-12-18 16:26 | Hexaae | Status | resolved => feedback |
| 2009-12-18 16:26 | Hexaae | Resolution | fixed => reopened |
| 2010-01-11 20:33 | Hexaae | Note Added: 0001632 | |
| 2010-12-09 12:02 | Hexaae | Note Added: 0002169 | |
| 2010-12-09 12:02 | Hexaae | Status | feedback => assigned |
| 2010-12-09 12:31 | Hexaae | Note Edited: 0002169 | View Revisions |
| 2011-05-17 19:56 | haynor666 | Note Added: 0002343 | |
| 2011-06-03 22:33 | JOTD | Note Added: 0002363 | |
| 2011-06-03 22:33 | JOTD | Status | assigned => closed |
| 2011-06-03 22:33 | JOTD | Resolution | reopened => not fixable |
| Issue History |