https://villavu.com/forum/showthread...61#post1290061
Right?
If you fixed it you didnt update the repo![]()
https://villavu.com/forum/showthread...61#post1290061
Right?
If you fixed it you didnt update the repo![]()
isnt that good, also forgot here to remove the trail after a few seconds
That pascal plugin doesn't have anything to do with the current one. In fact, I might remove that Repo to get rid of confusion. The C++ ones already work. The pascal one was just there in case someone wanted "Pascal" only code after seeing how much C++ hate goes on around villavu..
But again, DXI works fine: https://github.com/Brandon-T/DXI/tree/master/DXI https://github.com/Brandon-T/DXI/releases
I am Ggzz..
Hackintosher
I am Ggzz..
Hackintosher
I don't think mousetrails would be something that people would use except for debugging maybe, or if they just wanted to see it for a little, so the extra CPU wouldn't be that big of an issue.
Yeah but with options comes many other options. Being able to specify what the trail looks like (shape), the colours, the length, crosshairs, etc.. Not just a boolean. It can actually still be done via a plugin. Just map the same memory that SMART mapped and write to its image buffer but is it worth it? If done in Direct-X or OpenGL rather than through SMART's image buffer, it's going to require the translations and vertices of every trail.
TLDR: Write to SMART's image buffer. Can easily be passed to any plugin for more speed. Personally, I actually won't mind adding this to the plugins or to SMART since I haven't coded much in a long time, but I'm not sure why when it can be done in Simba or in a plugin.
Last edited by Brandon; 07-13-2014 at 10:48 PM.
I am Ggzz..
Hackintosher
I'm glad I've brought this up, as many people have been wanting it as well. =)
Tsunami
There are currently 1 users browsing this thread. (0 members and 1 guests)