Question/Passability problem

[Ally]

Hello to all...
I was doing tests on my project and I have encountered this problem and I can not solve...


e settings I used in tilesets, are these:


View attachment 55476View attachment 55478


As you can see from the screen, the passability are not right:


View attachment 55475


But, in the first plant, the passability is correct: O_________O






I using the script of VXAce Star Passability Bug Fix...

 

[Andar]

please describe in the text what exactly the problem is - your screenshots are not enough to understand what you consider wrong or correct.


Because from my looking at those pictures, that is what I consider correct...

 

[Ally]

please describe in the text what exactly the problem is - your screenshots are not enough to understand what you consider wrong or correct.


Because from my looking at those pictures, that is what I consider correct...

As you can see from this screen, the character's head is cut...
And I can not understand why...


The passability seem set correctly...

 

[_Shadow_]

Blind guess:


Open tileset B.


Is The top left tile set to passability star?


If no, set it to star and test your passability again.

 

[mlogan]

His head is cut off because you have that piece set to star passability, which means it will be above the sprite. Yes, that is why you are using the script - to prevent that from happening. So therefore, it would seem you somehow do not have the script set up correctly.

 

[Ally]

Blind guess:


Open tileset B.


Is The top left tile set to passability star?


If no, set it to star and test your passability again.

View attachment 55476


Yes, it is already set with the star...

 

[_Shadow_]

View attachment 55476

Wait, I meant the top left tile of the WHOLE TILESET in the database. Not in the picture. Or does it happen that the top left tile of the whole tileset is the top left of the picture???


If so, leave it blank and place the leaves elsewhere.

 

[mlogan]

The tile is acting as it should. OP is using a sprite that is taller than 32 pixels, thus there is a collision issue. OP says they are using the script to fix that, so therefore it seems the script, for whatever reason, is not doing what it should

 

[_Shadow_]

The tile is acting as it should. OP is using a sprite that is taller than 32 pixels, thus there is a collision issue. OP says they are using the script to fix that, so therefore it seems the script, for whatever reason, is not doing what it should

Oh! Is that so? I misunderstood the problem.


Well then @Ally should screenshot the script settings and any setup he/she did I guess, so we can help further.

 

[Ally]

Wait, I meant the top left tile of the WHOLE TILESET in the database. Not in the picture. Or does it happen that the top left tile of the whole tileset is the top left of the picture???


If so, leave it blank and place the leaves elsewhere.

Yes, I use a larger sprite...
Here is the tileset B:





This is the setting of the script:





And this, of the tileset:

 

[Shaz]

The issue is because you have the character between two tiles with a star passability, and they should appear behind one and in front of the other.  The script does not cater for this, and I think there were other cases where it also didn't work properly.  I attempted to write a fix, and it did fix most of the problems, but this one issue I could not solve.  If it's possible, just move the lower tiles down one space to avoid getting the PC in such a situation.

 

[Ally]

The issue is because you have the character between two tiles with a star passability, and they should appear behind one and in front of the other.  The script does not cater for this, and I think there were other cases where it also didn't work properly.  I attempted to write a fix, and it did fix most of the problems, but this one issue I could not solve.  If it's possible, just move the lower tiles down one space to avoid getting the PC in such a situation.

I have tried it with a plant without other objects around, and the problem remains the same ç_____ç

 

[Shaz]

That should definitely not happen with that script.  Do you have it installed in the right place?  Should be just below Materials.  Could you give a screenshot of your Scripts file, showing the list of scripts you have installed?  It might be due to where you have the script, or maybe a conflict with another script, so I'd be interested to see what else you have in there.


You might also try the fix that I made and see if it solves the problem.  I think it's in that same thread (or I might have made a new thread for it).

 

[Ally]

Here, the my script:

You might also try the fix that I made and see if it solves the problem.  I think it's in that same thread (or I might have made a new thread for it).

I don't think I have seen your fix...
Can you please give me the link?

 

[Shaz]

Ugh!  sorry - the fix I made was for the MV version, not for Ace.


All I can suggest is moving the Large Sprite Fix right to the top of the custom scripts and testing, and if it doesn't work, move it right to the bottom of the custom scripts (immediately above Main), just to see if there's another script that's conflicting with it.

 

[Ally]

Ugh!  sorry - the fix I made was for the MV version, not for Ace.


All I can suggest is moving the Large Sprite Fix right to the top of the custom scripts and testing, and if it doesn't work, move it right to the bottom of the custom scripts (immediately above Main), just to see if there's another script that's conflicting with it.

I tried to move the script, I not receive no errors, but does not work the same ç_ç


EDIT:


I did various tests...
Unfortunately, the script does not work when there are nearby objects...


I modified this line:


UpperTerrain = 6


and updated the priority of tilesets and it works ... probably conflict with other script.

Anyone can create a fix for this?
is quite annoying, and not be able to use bigger character, it can not be a problem...

 

[mlogan]

I'm going to go ahead and move this over to Script Support, since we've determined that's the issue.

 

[Ally]

I'm going to go ahead and move this over to Script Support, since we've determined that's the issue.

Thanks so much!
I hope @Neon Black can solve the problem ^^

 

[Ally]

Using this script, I have solved the problem:





It might be useful add this link in the original topic, so other people can solve the problem...