Updated plugin interface available

After checking the header files (internalsplugin.hpp), I noticed two interesting variables:
- mFrontFlapActivated
- mRearFlapActivated

Does it means that rFactor 2 since build 68 will have support for dynamic/movable wings?
 
Perhaps. :)

In reply to my first post... We may have found an issue that means maybe only 1 plugin can function with rf2 at a time, and for most of you track ir is maybe taking that slot. Working on a fix.
 
1968/69 F1 season saw manually adjustable wings in play before these high wings (as seen in rF2) were banned due to wing failures causing the terrible Lotus 49B accidents in the '69 Spanish GP at Montjuich. I hope it could be implemented on the 60s racing cars, that would be great!
 
I just download it... I 'm quite disapointed...
It still contain OBVIOUS bugs, for example :
Original classes virtual function declaration :
virtual bool ExampleInternalsPlugin::CheckHWControl( const char * const controlName, double &fRetVal ) { return false; }
Examples.hpp
bool ExampleInternalsPlugin::CheckHWControl( const char * const controlName, float &fRetVal );

It can't works... the function signature for the virtual is wrong, it will be never called. I didn't look further.
I don't want to spend several hours again to check everything.

EDIT : same error with UpdateHardware, I already pointed all those bugs... ><

So let's wait for version #3 with ALL error fixed.
Thanks.
 
magicfr said:
It can't works... the function signature for the virtual is wrong, it will be never called. I didn't look further.
I don't want to spend several hours again to check everything.

EDIT : same error with UpdateHardware, I already pointed all those bugs... ><
Click to expand...

There are literally 4 changes, all in InternalsPlugin.hpp: 3 mExpansion[]'s have been reduced in size with some (largely already documented) values pulled out, and a comment has been added specifying an extra environment path.

You would save yourself some time with a decent file/folder comparison tool :)

As for the virtual function signatures being wrong, I think at least one (ForceFeedback()) could be made to run by simply changing the Example.hpp signature to match the virtual (float -> double, in that case) - unfortunately that particular one, when I tested a few months ago, didn't actually produce the required effects despite being run. So that may be the case with the others too - you'd have to test.

Ultimately we have to accept that plugin development isn't a core part of the game itself, so it's likely we won't see all the features and capabilities added to this interface until the game has reached the initial release stage - or even afterwards.
 
The thing is, when the first sample was release I had already explained those errors, and they didn't fix it. The way it is it can't works, mean, they didn't even test it themself. So why updating it?
As game developer myself I prefer don't do things instead of doing them badly or in a hurry without any tests.
 
The interface itself is left over from rF1, so they haven't done work to put it in and then done it badly. It's just not been updated to work with rF2's new stuff - sure, they could have fixed those things as well as implementing some of the stuff that doesn't work even with those virtual definitions fixed, but it's not exactly top of the priority list. It doesn't make much sense to delay rF2 features/stability in order to properly finish the plugin interface - that can come later without affecting anyone but plugin developers.
 
You must log in or register to reply here.
Back
Top