What's New: RMP 1.4.1:
- New : Logger now uses 24 hours time system.
- BugFix: Windows 10 detected as Windows 8 (New Algorithm).
SpoilerComplete changelog::
RMP 1.4.1:
- New : Logger now uses 24 hours time system.
- BugFix: Windows 10 detected as Windows 8 (New Algorithm). RMP 1.4:
- New : Tixati peerId & Key validator.
- New : Upload & Download rate show in Real time.
- New : You can change Upload & Download rate in Real time.
- New : More finished options (seeding, Leeching, Custom (%, Byte, KB, MB, GB)).
- New : Total upload, Total download, Left and Ratio numbers. (Needs translating)
- New : Total upload, Total download and Ratio stop conditions. (Needs translating)
- New : Torrent & over-all settings now save at Tracker update besides at Exit.
- BugFix: uTorrent peerId validator failed in some rare special cases. RMP 1.3.3:
- New : Tixati peerId and key support.
- New : Can't add new torrent while working on another.
- BugFix: Over logging in some cases (Like moving your mouse on tray icon). RMP 1.3.2:
- BugFix: Special log message for empty tracker respond.
- BugFix: Tracker URL is repeated in Trackers ComboBox.
- BugFix: Selected tracker url is not saved correctly.
- BugFix: Can't load HTTPs Tracker URL in some cases.
- BugFix: Can't decode tracker respond if its encoding is gzip. RMP 1.3.1:
- BugFix: Tracker Respond logged as empty text.
- BugFix: TorrentDay trackers URLs not get correctly loading. (Reported: greenberet)
- BugFix: Tracker request not valid for HTTPs trackers. (Working on the latency) RMP 1.3:
- New : GUI icons and arranged controls.
- New : You can now use uTorrent client without memory reader (uT versions >3.4.x, Change bt.randomize_peer_id to false).
- New : You can now use Transmission client without memory reader.
- New : PeerId and Key get generated at start-up by default.
- New : Port generated at start-up IF the port text box is empty.
- New : Tracker URL & Torrent hash is read only now.
- New : All torrent trackers loaded at the start-up and you can choose one to use.
- New : Faster Memory reader and the GUI still responsive while reading memory.(with uT > 3.4.x support)
- New : Memory reader now respect if the PeerID & Key is global or not.
- New : PeerId validation for uTorrent & Transmission peerIds.
- BugFix: PeerId exceptions ignored and always passed as fixed value.
- BugFix: New port generated with 'every' announce.
- BugFix: Wrong Java version detection in special cases (New detection algorithm).
- BugFix: Can't load tracker URL in some cases. (Reported)
- BugFix: RM+ can't remember the last used client between starts.
- Remove: Internal clients removed.
- Remove: Client files update manager is removed.
ClientFile Changelog:
- New : New extension ".pclient" (had to, because of the many changes).
- New : randomize="" attributes for peerId & Key.
- New : urlencoding="upperCase" & urlencoding="lowerCase" to specify %AB or %ab
- New : global="" attributes for peerId & Key.
- New : query {localip},{ipv6},{ip} place-holders support.
- New : headers {customport},{allports} place-holders support.
- New : PeerId type value "uT" or "ut" for generating valid uTorrent peerId without memory reader. <peer_id type="ut"
- New : PeerId type value "Tr" or "tr" for generating valid Transmission peerId without memory reader. <peer_id type="tr"
- New : <peer_id node has exceptions="" attribute now.
- New : <hash node has exceptions="" attribute now.
- Change: No <urlencoding node anymore (use <hash & <peer_id to add exceptions by exceptions="" attribute).
- Change: No value="" in PeerId and key node in client file anymore.
RMP 1.2:
- New : RM+ now simulates the real client accurately.
- Fixed : RM+ doesn't save Torrent's config file if there is no language file loaded.
- Fixed : Couldn't decode tracker respond correctly (Reported: Rebound)
- Fixed : BitComet 0.70 wrong peerID prefix
- UI : SB-I reference in Title bar.
- New : Auto uTorrent peerID prefix -not whole pId- generator.
- Client Files: up-to-date client files serving the new changes.
RMP 1.1:
- Fixed : "Check for updates" button is not greyed while updating.
- Fixed : Wrong add at log window (example : "unNumUpdatesFounjd=Found {0} updates" after update).
- Fixed : No log messages if language file exist.
- New : IPv6 support {ipv6}
- New : New Icon (Thanks anon)
RMP 1.0:
- New : Client updates via SB-I's server.
- Removed: Check for new version at start-up.
- Removed: "Check for new version" CheckBox.
- Removed: "Help with proxies" at "Network" tab.
- Fixed : Wrong Windows(7 X64) version detection.
- Fixed : Wrong Windows(8,8.1) version detection.
- Fixed : Java wrong version detection.
very important points:
- You can now use RatioMaster plus without memory reader if you run it standalone.
- RatioMaster's Client files is not valid for the plus version anymore.
i´m having memory error when using transmisson-qt...anybody else?
when using qbittorrent everything is ok...
Open the client file with notepad and change the process name to 'transmisson-qt' instead of 'transmisson' and restart rm+ and try again and it will work.
PS: already using the latest Transmission 2.84 v1.3, works great...as Lucius said
"Open the client file with notepad and change the process name to 'transmisson-qt' instead of 'transmisson' and restart rm+ and try again and it will work. "
Started a test on an 32bit Win 7 PC and did the trick off open the client file provided by mmmmm with notepad and change the process name to 'tixati_Windows32bit' instead of 'tixati_Windows64bit' and memory read worked ok , but I'm just curious because without closing tixti client and doing the same process with another RatioMasterPlus instance memory read didn't show the same PeerId and key (Test was different torrents, but same tracker)
closing tixti client and doing the same process with another RatioMasterPlus instance memory read didn't show the same PeerId and key (Test was different torrents, but same tracker)
Use memory reader only on the original Tixati not modified and why you're reading RM's memory it has no point.
memory reader is useful to make the Real tixati and the faked one (rm) appears as just one application, RM+ has an ability of deciding if the captured data (or just a part of it) has to be ignored. Rm+ will choose the perfect situation to appear to the tracker as another torrent in one Tixati instance.
Anyway in case of Tixati, the peerId and the key is not global. That means you can use Rm+ without memory reader (try to memory read Tixati in rm+ and the ignore image will appear beside peerId and key).
memory reader will only read the port and the numwant values.
Just write it (port & numwant) manually in the other Rm+ instance and you will be safe.
memory reader is useful to make the Real tixati and the faked one (rm) appears as just one application, RM+ has an ability of deciding if the captured data (or just a part of it) has to be ignored. Rm+ will choose the perfect situation to appear to the tracker as another torrent in one Tixati instance.
I don't understand this 100%, but...
Originally Posted by Lucius
Anyway in case of Tixati, the peerId and the key is not global.
...suppose this is why memory read could be ignored, except port and the numwant values
EDIT: maybe you missed
without closing tixti client and doing the same process with another RatioMasterPlus instance memory read didn't show the same PeerId and key (Test was different torrents, but same tracker)
Bookmarks