jovial
Moldy Popcorn
Posts: 36
|
Post by jovial on Aug 26, 2021 17:34:23 GMT -5
jovial, Well, can't you make more slides? Of course I can. I already told you this.
jovial, Well, can't you make more slides?
Is this not what you were talking about?
|
|
|
Post by tiberiyltim on Aug 28, 2021 9:37:19 GMT -5
Can I have a look at the code?
Pictures with a white background are used, so the memory does not overflow ... But if you use photos without repeated tiles, then there will be problems.
|
|
jovial
Moldy Popcorn
Posts: 36
|
Post by jovial on Aug 29, 2021 9:06:33 GMT -5
Can I have a look at the code? Pictures with a white background are used, so the memory does not overflow ... But if you use photos without repeated tiles, then there will be problems.
You said "Take 5-7 photos by uploading them one after another. Only then will the bug appear."
I show you 6 photos displaying without any issues.
Then you find another excuse.
I'm done replying to this topic lol
(and no, I didn't save the source code and have zero desire to redo it for you since you're always trying to find something to blame besides your code)
|
|
|
Post by tiberiyltim on Aug 29, 2021 18:32:45 GMT -5
jovial,
You used pictures that do not exceed the tileset limit.
Treat your nerves. You have mood swings. No need to be hysterical.
|
|
jovial
Moldy Popcorn
Posts: 36
|
Post by jovial on Aug 29, 2021 18:57:07 GMT -5
jovial, You used pictures that do not exceed the tileset limit. Treat your nerves. You have mood swings. No need to be hysterical.
Please check your knowledge.
There is no "tiles" for the frame buffer.
You're just too ignorant and refuse to believe it's YOU where the problem lies, not the compiler.
I'm sorry you think telling you the truth is "nerves" and "hysterical". Clearly everyone else is the problem except you and your understanding.
|
|
|
Post by tiberiyltim on Aug 30, 2021 8:10:49 GMT -5
jovial,
This discussion was created to find a solution.
Did you help me? No.
Did you give me a hint? No.
Has the problem been resolved? No.
Am I grateful to you? No.
You only boast, hysterical, accuse.
There is no need to show that you can, while others cannot. Here a specific problem should be solved.
You only demotivate.
Everything that you wrote here is useless. It only gratifies your pride. 0.
|
|
jovial
Moldy Popcorn
Posts: 36
|
Post by jovial on Sept 3, 2021 6:10:37 GMT -5
jovial, This discussion was created to find a solution. Did you help me? No. Did you give me a hint? No. Has the problem been resolved? No. Am I grateful to you? No. You only boast, hysterical, accuse. There is no need to show that you can, while others cannot. Here a specific problem should be solved. You only demotivate. Everything that you wrote here is useless. It only gratifies your pride. 0. I tried to help, you were so insistent that it was a BEX problem, that I find zero reason to help you. After trying to explain that it wasn't BEX's issue, you kept throwing excuses. Sorry your ego is bruised (kidding, I'm not), but maybe if you weren't egotistical and could admit that it was you that is the issue and not blaming it on the compiler, I'd have been more inclined to help you.
Don't have weak skills and quit arguing with people and telling them that they're being emotional and to treat their nerves, and maybe they'll help you.
In fact, maybe you should treat your nerves. Quit being so weak.
And no, not everything I wrote here is useless. The fact that I showed you it can be done proves that the problem is you, not BEX.
|
|
|
Post by tiberiyltim on Sept 14, 2022 8:26:59 GMT -5
|
|
jovial
Moldy Popcorn
Posts: 36
|
Post by jovial on Oct 3, 2022 10:25:20 GMT -5
This isn't the same issue. And there's a fix for the BSR issue. 2 fixes actually. This also isn't your issue with 32x backgrounds. I've already addressed the issue, but you just don't want to believe it.
|
|
|
Post by tiberiyltim on Oct 11, 2022 15:23:00 GMT -5
This isn't the same issue. And there's a fix for the BSR issue. 2 fixes actually. This also isn't your issue with 32x backgrounds. I've already addressed the issue, but you just don't want to believe it.
What do I not want to believe? That such a problem does not exist? This problem does not even occur on the 32X. After repeatedly using this command "Dim LevMap_B_1(63,63) as INTEGER" failure occurs. Probably limited use of DIM. The memory is filled incorrectly. Not overwritten?
|
|
jovial
Moldy Popcorn
Posts: 36
|
Post by jovial on Oct 13, 2022 10:52:31 GMT -5
Dim just sets the size (and scope) of a variable. There's no limited use of it, and I'm not even sure how you're coming to that conclusion. Dim Var(63,63) As Integer
That takes up: 64*64*2 bytes, or 4096x2 = 8192, so 8KB of RAM, which is 1/8th of your total RAM allotment. This has nothing to do with code length, the BSR issue, or 32x backgrounds. The BSR issue is due to code getting placed too far away from the current location the opcode is being called from. Here's an explanation: mrjester.hapisan.com/04_MC68/Sect05Part06/Index.htmlThis really popped up with the use of XGM for BEX. The solution? Find the program someone made called BSRFix, change sound drivers (which, you can still run into this issue regardless of the sound driver), or switch to another compiler. Your 32x issues is just your code.
|
|
|
Post by tiberiyltim on Oct 13, 2022 13:32:21 GMT -5
There is a limitation. You will encounter this if your game has many levels.
I found a solution!
I replaced the level drawing code with:
It was:
It became:
Those. now I use it once
I don't know why, I'm not a great programmer... But a problem arose. I had to find a solution.
If you are writing a large game, then you may have such problems. Solutions found.
|
|
jovial
Moldy Popcorn
Posts: 36
|
Post by jovial on Oct 13, 2022 13:46:53 GMT -5
Well yeah, you ran into issues by using several 8KB arrays. You don’t need to keep doing that, as you found out (you can use the memory tool in bex to see how much is available). It’s not a problem with the compiler, the dim statement, or anything other than trying to allocate more memory than is available. And now you know for future projects (It’s perfectly fine to keep reusing variables as long as you aren’t trying to use the same variable for multiple things at once). In this instance, a single map variable is more than enough. As a hint, you can do all the map stuff without using an array variable, but instead by reading the map from the rom and just loading the data at an offset.
|
|