Jump to content

Photo

Bug Report Thread


305 replies to this topic

#301 orange808 OFFLINE  

orange808

    Space Invader

  • 43 posts

Posted Sat Sep 15, 2018 3:27 PM

I have a fresh install of bB and Visual Basic on this Win 10 machine (no previous installations to pollute my registry). I followed the instructions. I have the latest versions. I am familar with coding and Windows. The environment variables aren't an alien concept and they are right. Running as admin. So, when I look at the DPC+ examples, they run well enough. But, if I add a set romsize command, they all break. I tried multiple examples. I can change the romsize on Tinkernut all I want. Any suggestions?

#302 orange808 OFFLINE  

orange808

    Space Invader

  • 43 posts

Posted Sat Sep 15, 2018 3:30 PM

Also, will add that this is an Intel x64 machine. Not an AMD or the new ARM x86 Windows emulation. Not an exotic environment.

#303 RevEng OFFLINE  

RevEng

    River Patroller

  • 4,990 posts
  • Bitnik
  • Location:bottom of the stack

Posted Sat Sep 15, 2018 3:36 PM

bB DPC+ is only 32k. You can't change the romsize.

#304 orange808 OFFLINE  

orange808

    Space Invader

  • 43 posts

Posted Sat Sep 15, 2018 5:38 PM

bB DPC+ is only 32k. You can't change the romsize.

​Fair enough.  I found the documentation to be somewhat ambiguous about this.  It declares that the romsize is automatically set for you, but I didn't understand that sentence was implying that the romsize could not be changed at all.

​How about the multikernel framework with multiple DPC+ 32k parts?

​Edit:  Apologies.  Answered my own question.  That won't work.  The DPC+ kernel alone is too big to fit inside "containers" of 4k.


Edited by orange808, Sat Sep 15, 2018 5:49 PM.


#305 Random Terrain OFFLINE  

Random Terrain

    Visual batari Basic User

  • 28,789 posts
  • Controlled Randomness
    Replay Value
    Nonlinear
  • Location:North Carolina (USA)

Posted Sat Sep 15, 2018 6:52 PM

Be sure to refresh the bB page.



#306 bogax OFFLINE  

bogax

    Dragonstomper

  • 777 posts

Posted Tue Oct 2, 2018 9:41 AM

Not really a bug

 

I am frequently frustrated by having constant macro parameters treated as immediate values.

Not really sure how to deal with that.

How hard would it be to perhaps escape a constant to suppress emission of the "#" ?

(best I could think of)






0 user(s) are browsing this forum

0 members, 0 guests, 0 anonymous users