GRF encoder tool: GRFMaker [under development]
Moderator: Graphics Moderators
What I find more likely, Jpmaster is that one of your action1+realsprite(and/or)action2 blocks (Sprite blocks, in grfmaker speak) is referring to a file that has been moved, renamed, or deleted. Go back through and make sure that all of those match up. That's about the only thing I can think of that would cause such an error.
I appologise for bringing this up in public, but I feel I must defend myself publicly as I've been spited publicly in various places too many times for my liking already. I will try to keep this as civil as possible.
Whitehand, remember who taught you, who held your hand throughout learning GRFMaker, who has been at this entire thing a good deal longer than you, hosts GRFMaker and has had a considerable say in it's overall development, and who maintains a hell of a lot of .grf sets that are probably larger and more complex than yours (For the moment atleast).
If you insist on taking pot-shots at me, implied or explicit, on IRC or the forums, then so be it (I'm letting your implied accusations of me lying about the tourists scheme slide, I have ample proof to proove my case, but it's pointless even bothering).
I've got better things to do than write out these stupid retorts. Entertain yourself with taking your under-the-table stabs at me, you're not getting your lulz out of me.
---
Ehehm, again, I apologise for that. Jpmaster.
Despite my annoyance with Whitehand, he is still quite knowledgeable with grfmaker. If he can't help you solve your problem, good people to also ask would probably be AndersI and perhaps JVassie or Jonty. If not, the View NFO function is also handy to export an copy of the .nfo as it would be compiled. That can often be a good way to track down bugs in code, ss then you can work with the rest of the NFO coding community. Although, trying to implement their suggestions might prove difficult as you learn to associate what GRFMaker 'blocks' correspond to what NFO code.
I appologise for bringing this up in public, but I feel I must defend myself publicly as I've been spited publicly in various places too many times for my liking already. I will try to keep this as civil as possible.
Whitehand, remember who taught you, who held your hand throughout learning GRFMaker, who has been at this entire thing a good deal longer than you, hosts GRFMaker and has had a considerable say in it's overall development, and who maintains a hell of a lot of .grf sets that are probably larger and more complex than yours (For the moment atleast).
If you insist on taking pot-shots at me, implied or explicit, on IRC or the forums, then so be it (I'm letting your implied accusations of me lying about the tourists scheme slide, I have ample proof to proove my case, but it's pointless even bothering).
I've got better things to do than write out these stupid retorts. Entertain yourself with taking your under-the-table stabs at me, you're not getting your lulz out of me.
---
Ehehm, again, I apologise for that. Jpmaster.
Despite my annoyance with Whitehand, he is still quite knowledgeable with grfmaker. If he can't help you solve your problem, good people to also ask would probably be AndersI and perhaps JVassie or Jonty. If not, the View NFO function is also handy to export an copy of the .nfo as it would be compiled. That can often be a good way to track down bugs in code, ss then you can work with the rest of the NFO coding community. Although, trying to implement their suggestions might prove difficult as you learn to associate what GRFMaker 'blocks' correspond to what NFO code.
Currently working under the name 'reldred' on Github, and Discord.
NFO/NML coder, part-time patch writer for JGRPP, and all round belligerent.
14:40 <orudge> I can't say I discriminate against any particular user
14:41 <Aegir> orudge: I can!
NFO/NML coder, part-time patch writer for JGRPP, and all round belligerent.
14:40 <orudge> I can't say I discriminate against any particular user
14:41 <Aegir> orudge: I can!
It flatters me to be put alongside the others here, but it's actually me asking the questions, wanting more examples etc. I'm not really in a position to give answers (yet). Unless it's about something I've already solved, of course...Aegir wrote:... Whitehand, he is still quite knowledgeable with grfmaker. If he can't help you solve your problem, good people to also ask would probably be AndersI and perhaps JVassie or Jonty.
That was in response to the file not found error, AndersI. But anyways, I've got another rant to do
.
Let me just say something that I'm not sure a lot of people have really grasped, using GRFMaker is not going to stop you from having to learn NFO. The trick with learning GRFMaker and learning how to use it well, is to learn what NFO it creates. What actions (Or groups of actions) each block relates to. If you want to use GRFMaker because you don't want to touch NFO, then you want to use GRFMaker for all the wrong reasons. GRFMaker aids in allowing you to code your stuff without having to worry about the nitty-gritty of NFO. You still need to understand how it all works.
Afterall, all of the TTDPatch error messages are going to be referring to bits of NFO, you are going to have to learn how to read and understand NFO to debug your .grf's, and sometimes for even coding things in GRFMaker that you have never coded before.
Yes, GRFMaker could do with a lot more documentation, it could do with more example code, and so forth. But theres a reason why that work hasn't been tackled really head on so-far, and that's that GRFMaker is still an alpha quality software, it's still in heavy development.

Let me just say something that I'm not sure a lot of people have really grasped, using GRFMaker is not going to stop you from having to learn NFO. The trick with learning GRFMaker and learning how to use it well, is to learn what NFO it creates. What actions (Or groups of actions) each block relates to. If you want to use GRFMaker because you don't want to touch NFO, then you want to use GRFMaker for all the wrong reasons. GRFMaker aids in allowing you to code your stuff without having to worry about the nitty-gritty of NFO. You still need to understand how it all works.
Afterall, all of the TTDPatch error messages are going to be referring to bits of NFO, you are going to have to learn how to read and understand NFO to debug your .grf's, and sometimes for even coding things in GRFMaker that you have never coded before.
Yes, GRFMaker could do with a lot more documentation, it could do with more example code, and so forth. But theres a reason why that work hasn't been tackled really head on so-far, and that's that GRFMaker is still an alpha quality software, it's still in heavy development.
Currently working under the name 'reldred' on Github, and Discord.
NFO/NML coder, part-time patch writer for JGRPP, and all round belligerent.
14:40 <orudge> I can't say I discriminate against any particular user
14:41 <Aegir> orudge: I can!
NFO/NML coder, part-time patch writer for JGRPP, and all round belligerent.
14:40 <orudge> I can't say I discriminate against any particular user
14:41 <Aegir> orudge: I can!
- spaceman-spiff
- Retired Moderator
- Posts: 20634
- Joined: 28 Jul 2002 07:08
- Location: Belgium
- Contact:
Why do you bring that up in here ? I see no attack by whitehand !Aegir wrote:I appologise for bringing this up in public, but I feel I must defend myself publicly as I've been spited publicly in various places too many times for my liking already. I will try to keep this as civil as possible.
Whitehand, remember who taught you, who held your hand throughout learning GRFMaker, who has been at this entire thing a good deal longer than you, hosts GRFMaker and has had a considerable say in it's overall development, and who maintains a hell of a lot of .grf sets that are probably larger and more complex than yours (For the moment atleast).
If you insist on taking pot-shots at me, implied or explicit, on IRC or the forums, then so be it (I'm letting your implied accusations of me lying about the tourists scheme slide, I have ample proof to proove my case, but it's pointless even bothering).
I've got better things to do than write out these stupid retorts. Entertain yourself with taking your under-the-table stabs at me, you're not getting your lulz out of me.
Please don't do that
Well, back to work, lot's of it in the near future
Does "use a slot that had a vehicle for another climate" qualify as "new"?
To get a good answer, ask a Smart Question. Similarly, if you want a bug fixed, write a Useful Bug Report. No TTDPatch crashlog? Then follow directions.
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Then no. GRFMaker can't do anything that can't be done in pure NFO.
To get a good answer, ask a Smart Question. Similarly, if you want a bug fixed, write a Useful Bug Report. No TTDPatch crashlog? Then follow directions.
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
I need (want, would like) help in setting the purchase window sprite with GRFMaker. I've tried a number of permutations in the dialogs, but so far nothing has come out right - one of the more interesting results were the purchase window sprite being used as the only engine sprite - in all directions 
I can do it directly in NFO, but I would like to keep my project alive in GRFMaker, as it makes it so much easier to rearrange things, adjust data and positions, etc.

I can do it directly in NFO, but I would like to keep my project alive in GRFMaker, as it makes it so much easier to rearrange things, adjust data and positions, etc.
The way I do it is like this.
After you do what's shown in the picture, connect it to a Var action 2, or just plug it straight back into the regular sprite set.
After you do what's shown in the picture, connect it to a Var action 2, or just plug it straight back into the regular sprite set.
- Attachments
-
- Remember, you can't use a Date Built var with this, because, obviously, the purchase window sprites aren't built.
- purchasewindowsprites.PNG (17.12 KiB) Viewed 4832 times
Now, who put that little box there, in that dialog... I've never looked so far away in that list 
WhiteHand, thanks! Works without problems. My main problem was (probably) that I tried to use the other place, and couldn't figure out how (see picture). Do you know if this part is working, and if so, how to use it?

WhiteHand, thanks! Works without problems. My main problem was (probably) that I tried to use the other place, and couldn't figure out how (see picture). Do you know if this part is working, and if so, how to use it?
- Attachments
-
- This is where I tried to activate the veh.list sprite.
- Question2.png (7.82 KiB) Viewed 4780 times
-
- Works very well now!
- Scr50.png (5.32 KiB) Viewed 4751 times
Unless you have a method of reaching Szappy that does not involve these forums, the only thing I can come up with is "Learn NFO". AFAICT, Szappy has not been seen for nearly a year now.
There might have been GRFMaker updates that were not accompanied by a post here, and I wouldn't know about those, but Szappy's last post was June 12, 2006, which seems like a long time to be silent.
There might have been GRFMaker updates that were not accompanied by a post here, and I wouldn't know about those, but Szappy's last post was June 12, 2006, which seems like a long time to be silent.
To get a good answer, ask a Smart Question. Similarly, if you want a bug fixed, write a Useful Bug Report. No TTDPatch crashlog? Then follow directions.
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Projects: NFORenum (download) | PlaneSet (Website) | grfcodec (download) | grfdebug.log parser
Who is online
Users browsing this forum: No registered users and 1 guest