RPCE Revision #0033 - Printable Version +- Renegade Projects Network Forums (https://forums.renegadeprojects.com) +-- Forum: Inject the Battlefield (https://forums.renegadeprojects.com/forumdisplay.php?fid=60) +--- Forum: News from the Battlefield (https://forums.renegadeprojects.com/forumdisplay.php?fid=20) +--- Thread: RPCE Revision #0033 (/showthread.php?tid=643) Pages:
1
2
|
RPCE Revision #0033 - VK - 19.02.2007 Rock Patch Celebration Edition Revision #0033 released! Download it here. *NUKE Warhead fix *AITargeting fix *AutoFire fix *THD1 to TUT1 back *something else RE: RPCE Revision #0033 - Mig eater - 19.02.2007 & that something else would be...? o.0 RE: RPCE Revision #0033 - Renegade - 20.02.2007 Another buggy feature RE: RPCE Revision #0033 - Bobingabout - 20.02.2007 Quote:AITargeting fixthis means i have to turn AITargeting back to 1 based? RE: RPCE Revision #0033 - Marshall - 20.02.2007 I guess RP-Gen is a success then And I can confirm that the Launch Base side of the installer is working nicely too. RE: RPCE Revision #0033 - Bobingabout - 20.02.2007 has anyone tried it on TFD yet? i can't do it now, its too late, any my PC has been moved. RE: RPCE Revision #0033 - pd - 20.02.2007 works with T.F.D. btw, why is it revision #0033? is there any logic involved with that number?? RE: RPCE Revision #0033 - Mig eater - 20.02.2007 Hasn't there already been a revision #0033 I know there has been a #0035, so is RP going backwards? RE: RPCE Revision #0033 - Bobingabout - 20.02.2007 erm, IIRC, his revisions are the number of times he's edited gamemd.exe for this version of RP. i think instead of "This version" it should be total, so, we should really be upto #0069. RE: RPCE Revision #0033 - Marshall - 20.02.2007 Depends on how you look it. I work for a pretty large software company and I know the following holds true for our QA department, at least: If the Revision is actually a build number [please ignore all my previous posts regarding build numbers because I didn't know what I was talking about then] then it should work as Bobingabout described. However, if the last part of the version number is actually a forever-increasing build, then there should not be public releases with the same version number. I.E. You can't release X.Y1.B2 if X.Y1.B1 has already been released - you have to release X.Y2.B2. The way CnCVK is handling this is to have X.Y.Z, with Z just being another branch of the version number. This is appropriate for the RockPatch. It's nice and easy to understand. (except for the fact that it is currently "RPCE".Z instead of X.Y.Z) RE: RPCE Revision #0033 - Speeder (as a guest) - 20.02.2007 Okay. WHAT "else"? RE: RPCE Revision #0033 - Guest - 20.02.2007 So what's the deal with this revision, do we uninstall the original RPCE, or do we install this over the top of it? RE: RPCE Revision #0033 - Nighthawk - 20.02.2007 And are any important tags altered? Apart from the AITargeting, which I assume is now back to 1 based, and after I changed everything to 0-based too. RE: RPCE Revision #0033 - TheMan - 20.02.2007 Guest why dont you try by yoursself? Launch it, it will uninstall older version and install new version RE: RPCE Revision #0033 - VK - 20.02.2007 Quote:btw, why is it revision #0033? is there any logic involved with that number?? dir F:\RockPatch\RockPatchCE Code: 05.12.2006Â Â 22:56Â Â Â Â Â Â Â Â 5Â 943Â 296 gamemd_Revision0001.exe Quote:Hasn't there already been a revision #0033 I know there has been a #0035, so is RP going backwards?no. Revision number reset, when new RP released. Quote:Okay. WHAT "else"?Revisions is only fix bugs, no new features in it. (this allow RP be more stable). I had written so, because I didn't remember: fixed something else or not ohh... EvaActivated, for example, fixed too. |