DSP Robotics Support

Exo wrote:

CoreStylerz wrote:You mean creating a new dll.dll and replace it for building new wrapped plugins exo, or you're talking about making a wrapper to include the output wrapped schematic .dll exo?

I mean wrapping the dll.

Sorry for the double exo, mistake.
Have you some documentation to read about so i can get started?
Nubeat posted in the other topic this software link:
http://www.dllwrapper.com/

Seems capable to create 64bit wrapper around x86 application. I've downloaded the trial, but there's the need to make an header file before.
What values are passed by our FS plugins? and types?

Dear Jorge & Malcolm,

Please come down from your heavenly thrones and shed some light from your programming philosophies.
A little insight will go a long way.

I think as the talk is going on here, MyCo, Trog, Exo and other folks who participate in beta tests - are talking with devs about there options. No need to leave heavenly thrones.

tester wrote:MyCo, Trog, Exo and other folks who participate in beta tests - are talking with devs

For about the 1000th time

If we spot a specific bug and report it, we sometimes will get to test a new .exe or vst.dll to make sure that the fix works under the same test conditions that it was reported for. Even then, it will usually only be a last minute "sanity check" before a patch is released - and only because we have shown that we are reliable reporters of bugs with enough knowledge of how FS works and how to run proper tests that the dev's find our feedback useful.
For example, I never saw a Beta or any patches for the latest release - I learned of it at the same time as everyone else, when it was announced here. None of the fixes or updates originated with me, so it would have held up the release to have had me test them at short notice.

Other than that, we can make suggestions, and point the dev's in the general direction of any threads that we think they should take a look at - anyone here can do that, and your suggestions will be given no more or less consideration that ours get.

That's it! - we know nothing more than anyone else about "roadmaps" or what's being worked on right now. And we know better than to ask, because we know they won't tell, and it just makes the conversation awkward - like if you were to ask the guests at a dinner party to tell you graphic details about their sex lives (maybe I just don't get invited to the right dinner parties )

We get no special favours from DSPr, and we are not "prophets" with a direct line to "god" - we're just the guys that bash the bots, and have better than average knowledge of FS.

If anyone wants to believe otherwise, that's entirely up to them - you may hold on to whatever fantasies and delusions help you get through the day.
"He's not the Messiah, he's a very naughty boy!" as Monty Python would put it!

To clarify, my point is:

1) I bet, devs listen to people who they can work with on problems, where communication isn't creating obligatory demands and public complaints. Beta testers are closest approximation; they earned trust not without a reason, isn't it?
2) I doubt that devs listen to (freely communicate with) people who lament (demand) on x64 support (or anything else in that particular manner). Closest aproximation people know what kind of attitudes I mean.

By talking, I mean exactly what you said - spotting problems and asking for solutions or possible directions, without creating this (...) uncomfortable feeling of knife opening in the pocket. Theoretically everyone can talk to devs, but not everyone will make a good impression. Sometimes it is a matter of cross-language differencies, sometimes a matter of inability to communicate peacefully (so called "toxic relationship").

Talking to people who only demand something in an obligatory way, and publicly complain on something over and over - is simply risky. As a developer - would you talk to such people freely? I bet not. Would you publicly admit that you avoid such contacts? I bet not as well. Do you have such customers on your own? I bet yes, if you are selling your stuff.

In other words - whoever is captured on being beta tester - is simply doomed by definition. Run or take advantage of it!

The poor discussion and the continous complaint about features missing has been degraded because of lack of communication from developers!
So im kind bored of your sentences tester, seems that in your view dspr IS Kremlin...

Same as synthmaker forum, the lack of feedback from the product holder has generated bad mood and less confidence in this company software.

That's it.
If really they care us and the will avoid complaint's they should reply or discuss with us.
I live also if they don't go 64 bit... Just can we have some details of roadmap or future of software instead of a cheap discount to convince you to sub's.

Seems CFF Explorer by Daniel Pistelli still exists & maintained.

So CoreStylerz play with this http://www.ntcore.com/exsuite.php or anyone interested.

CoreStylerz wrote:The poor discussion and the continous complaint about features missing has been degraded because of lack of communication from developers!
So im kind bored of your sentences tester, seems that in your view dspr IS Kremlin...

Not exactly. Because it continues that way - developers no longer participate. I have been there, I saw the (...) done. Figure out how to fix it - this should be your challenge, not complaining the tester for pointing such obious things...

We have a political party here, invented by Kaczynski brothers some years ago. If you heard the stories, you know how bad is it. Bad weather? Blame the goverment. Earthquakes in America? Blame the goverment.

The most profound & problematic quotation ever cited.

"Ignorance is bliss"

This one seems rather apposite too...

A. Einstein wrote:Insanity: doing the same thing over and over again and expecting different results.