Jump to content


jetsetdanny

Member Since 07 Mar 2015
Offline Last Active Nov 20 2017 10:05 PM
-----

#8014 Jswed2 Suggestions

Posted by jetsetdanny on 20 November 2017 - 07:46 PM

Guys, I believe I have just come across a ridiculously easy solution to JSWED 2.3.7 freezing after being launched on W10 (after the Creators Update). It works for me, at least!

 

What you need to do, after launching the program, is to 'grab' the upper part of JSWED's window (the white stripe) with your mouse and move the program's window a little bit. It then starts responding!  :D

 

I would be interested to know if it's helped, if anyone else has stumbled upon the same problem.




#8013 Jswed2 Suggestions

Posted by jetsetdanny on 20 November 2017 - 07:42 PM

However, this may be because i have, to the best of my recollection only ever upgraded my operating systems rather than installing a new ones and when the computer needed an upgrade i just swap out the HDD, To this day my HDD label  is still MSDOS 5...

 

That's a remarkable achievement, MetalMickey! I've always done what I think is advertised as the best solution, i.e. clean install.




#8012 Pokes for Fixing the Cell Graphics Bug in JSW

Posted by jetsetdanny on 20 November 2017 - 07:39 PM

The point I was making is that SPECSAISIE prints the initials 'BGB' for at least half of the rooms in JSW!  But you only appear to have spotted the ones that happen to sit in the right-hand columns of the tables ('jutting out' from the main tables, so to speak).

 

If you look again you will see there are 'BGB' entries scattered throughout the tables that you failed to spot the first time!  ;)

 

OK, yes, you're right, I failed to spot those. I didn't really look at the content of the tables, so when I saw some "BGB" entries printed on the side of the tables, I assumed this was how the program was showing it had come across a problem  ;) .




#7953 Pokes for Fixing the Cell Graphics Bug in JSW

Posted by jetsetdanny on 18 November 2017 - 07:28 PM

As for the MM analysis - yes, later on at some point.




#7942 Pokes for Fixing the Cell Graphics Bug in JSW

Posted by jetsetdanny on 18 November 2017 - 05:25 PM

Yes, but SPECSAISIE's BGB_JSW stil analyses them.


  • IRF likes this


#7939 Pokes for Fixing the Cell Graphics Bug in JSW

Posted by jetsetdanny on 18 November 2017 - 05:17 PM

OK, I've done it for you since you've asked about it, Ian  :).

 

Attached below are screenshots of results of running the BGB-JSW function in SPECSAISIE on a basically unmodified JSW file (it's got things like the colour code bypassed, but I believe no editing was done regarding graphics).

 

If I understand the output correctly, SPECSAISIE shows the Cell Graphics Bug (=Block Graphics Bug) occurs in rooms 16, 31, 33, 41, 47, 51, 52, 62 and 63. This partly contradicts the common knowledge about the problem, I think, both in omitting some of the rooms where the bug occurs and by pointing to others where (possibly) it does not occur (unless these are instances of its occurring in unused cell types).

Attached Thumbnails

  • Rooms 00-01.png
  • Rooms 02-03.png
  • Rooms 04-05.png
  • Rooms 06-07.png
  • Rooms 08-09.png
  • Rooms 10-11.png
  • Rooms 12-13.png
  • Rooms 14-15.png
  • Rooms 16-17.png
  • Rooms 18-19.png
  • Rooms 20-21.png
  • Rooms 22-23.png
  • Rooms 24-25.png
  • Rooms 26-27.png
  • Rooms 28-29.png
  • Rooms 30-31.png
  • Rooms 32-33.png
  • Rooms 34-35.png
  • Rooms 36-37.png
  • Rooms 38-39.png
  • Rooms 40-41.png
  • Rooms 42-43.png
  • Rooms 44-45.png
  • Rooms 46-47.png
  • Rooms 48-49.png
  • Rooms 50-51.png
  • Rooms 52-53.png
  • Rooms 54-55.png
  • Rooms 56-57.png
  • Rooms 58-59.png
  • Rooms 60-61.png
  • Rooms 62-63.png



#7938 Pokes for Fixing the Cell Graphics Bug in JSW

Posted by jetsetdanny on 18 November 2017 - 03:44 PM

Should have gone to SPECSAISIE! :D

EDIT: Danny, in case that goes over your head - that's a play on the words of a series of TV adverts for a budget opticians we have here in Britain, called Specsavers. (Someone does something ridiculous due to their poor eyesight, followed by the punchline: "Should have gone to Specsavers!". Check out YouTube if you want a brief diversion.)

BTW, did you try out that function of SPECSAISIE on an unmodified copy of JSW and/or MM, Danny? (To confirm what we already know in relation to the former, or to spot previously unidentified instances in the latter - there may be some lurking in the defined-but-unused cell types?)

 

Thanks for your explanation, Ian. The reference would indeed have been lost on me without it  :lol: .

 

No, I haven't tried out that SPECSAISIE function.




#7934 Pokes for Fixing the Cell Graphics Bug in JSW

Posted by jetsetdanny on 17 November 2017 - 11:40 PM

Which makes me think: is there an automatic tool to list all the occurences of the Cell Graphis Bug in a game?

I am wondering if SPECSAISIE doesn't have such a function? I seem to recall something like this vaguely, but it may just be an illusion...

 

OK, I've checked it and it turns out I was right  :D .

 

As mentioned in Andrew Broad's description of his SPECSAISIE 1.2 (SPECSAISIE 1.3 Beta 5 was also made available to the members of the MM & JSW Yahoo! Group), it has the following function:

 

BGB_JSW: Detect occurrences of the block-graphics bug in a JSW game (an experimental implementation)

 

[Later on Andrew started using the term "Cell-Graphics Bug" instead.]

 

Apparently, this functionality has been there since SPECSAISIE v. 1.0.

 

Furthermore, John Elliott once wondered about incorporating this functionality into JSWED (but has not applied it so far, TTBOMK - something for the future, perhaps?).




#7925 Pokes for Fixing the Cell Graphics Bug in JSW

Posted by jetsetdanny on 17 November 2017 - 07:28 AM

I don't recall any discussion about it, ever, but, as mentioned before, I am interested in creating new games more than the details of the original. So I may have missed something.

It's quite possible, though, that you are the first person to ever bring this up.

Which makes me think: is there an automatic tool to list all the occurences of the Cell Graphis Bug in a game?

I am wondering if SPECSAISIE doesn't have such a function? I seem to recall something like this vaguely, but it may just be an illusion...


#7921 A total rewrite of JSW in 48k using Matthews core code

Posted by jetsetdanny on 16 November 2017 - 05:28 PM

I can conceive of two possible fixes for this (although quirkophiles such as Dr Andrew Broad wouldn't thank me for it!):

 

Quirkophobes would, though!  :lol:




#7912 Free space and code optimisation in "JSW"

Posted by jetsetdanny on 14 November 2017 - 12:47 AM

Well done! :)

It's interesting to follow this discussion, even though I am only a passive observer.
  • IRF likes this


#7854 Jswed2 Suggestions

Posted by jetsetdanny on 08 November 2017 - 01:55 AM

I have no problem with JSWED 2.3.7 on a computer with W7, fortunately :).


#7834 Free space and code optimisation in "JSW"

Posted by jetsetdanny on 04 November 2017 - 10:06 AM

Great stuff, Norman Sword, thank you!  :)


  • IRF likes this


#7825 Jswed2 Suggestions

Posted by jetsetdanny on 03 November 2017 - 10:21 PM

Now, this is not really a suggestion, it's a bug report, but I thought it might not be worth starting a new thread, especially one suggesting that JSWED doesn't work perfectly.

 

After Windows 10 automatic update earlier this week (I think it was at the beginning of this week, or last weekend perhaps, so around the end of October 2017), JSWED 2.3.7 installled on my computer using Windows 10 stopped working. It launches so that its initial screen can be seen, but when I try to load a game it turns out to be frozen, it doesn't respond at all. I can't close it using its own X sign either. However, it can be closed down without any hassle using the Task Manager.

 

That Windows 10 update was a big one, the computer had to shut down and restart several times before it was over.

 

Interestingly, JSWED 2.2.9 installed on the same computer works just fine. But I've grown used to JSWED 2.3.7 so much by now that going back to 2.2.9 does not seem to be a viable option.

 

Both v. 2.2.9 and v. 2.3.7 had been installed on this computer before the Windows 10 update in question. They had co-existed happily (or, at least, peacefully) before. Now only 2.2.9 works.

 

I tried reinstalling the 2.3.7 version (without de-installing it first), but to no avail. I mean, it gets installed, but still doesn't work after I launch it.

 

I have yet to try de-installing it first, and then re-installing, but somehow I have little hope this will help.

 

Perhaps John Elliott could help out, though? Any assistance with having JSWED 2.3.7 work properly with Windows 10 after this recent update would be much appreciated :).

 

Has anyone else had the same problem?




#7824 Free space and code optimisation in "JSW"

Posted by jetsetdanny on 03 November 2017 - 10:07 PM

Yes, it's a really good one, Norman Sword, thank you!

 

Now you will be really impressed by this  :lol: :

 

When creating the Sprite Selection Screen in "Jet Set Mixup", Ian set the attributes for the various numbers which are printed on the screen using a sequence of LD HL,&0000 - LD (&0000),HL instructions. So you have e.g. 21 41 41 22 a4 58, to set some attributes to BRIGHT blue. He went through most (or almost all) colours like this.

 

Now, when working on a similar selection screen related to a project which is discussed elsewhere, I introduced the following optimisation: I grouped the colours, I introduced the first one (say, non-BRIGHT red, i.e. 02) using the same instruction, so 21 02 02 41 a4 58, and then I introduced the following colours using INC H and INC L instructions (24 2C), thus saving one byte with the definition of each new colour, with the exception of when I had to "jump" from the last non-BRIGHT colour to the first BRIGHT one, which had to be done using the LD HL,&0000 instruction once again.

 

The total net saving was of 8 bytes, I believe. Not too impressive, but if it should happen that you just need one or two (or five) spare bytes in the vicinity, it could come in quite handy.