Re: Anyone able to use the S-fix with Redux?
This is what I get for working on two different engines at the same time – Trouble. In short, while there certainly are plenty of mitigating circumstances for me on this mess, it still does not undo that I carelessly provided faulty information because I assumed too much, thinking that both engines would be the same on this. After closer investigation - triggered by Nagnars post - it is now very clear to me that this is not the case. Evidently the V.1.1 and V.2.01-engines does function differently and it does make a difference on all this, in contrast to my previous claims…. Thus I have too take back my previous remarks on that note, as the facts have proved them wrong. In addition, I apologise for whatever inconvenience and problems this may have caused people here….
My findings - after having now investigated both engines - are as follows:
- V.1.1-engine + Regular EXE + RXB1003 hotfix = works (as advertised).
- V.1.1-engine + No-CD patched EXE + RXB1003 hotfix = works (as advertised).
- VI/V.2.01-engine + Regular EXE + RXB1003 hotfix = Don’t work
- VI/V.2.01-engine + No-CD patched EXE + RXB1003 hotfix = Don’t work
Reason: The relevant files are named differently in the VI/V.2.01- engine then the V.1.1-engine.
Solution: Change filename in RXB1003-hotfix to match VI/V2.01-engine file-specifications – from LukMap.Lbm to LukUpMap.Lbm.
Result:
- VI/V.2.01-engine + Regular EXE + changed RXB1003 hotfix = work (as advertised)
- VI/V.2.01-engine + No-CD patched EXE + changed RXB1003 hotfix = work (as advertised)
...
That said, I will also remove the defect hotfix and replace it with a new one that works on ALL engines, straight out of the box - without any manual changes and corrections necessary. The withdraw and release of the replacement hotfix will be made shortly...
- A
Bookmarks