Jump to content

Ai4rei

Members
  • Posts

    425
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by Ai4rei

  1. Updated to 2.4.2 Maintenance and refresh release. Updates iRO patch information and refreshes core libraries.
  2. Use Resource Hacker to edit the String Table. Yes, Resource Hacker only. For the button names, see the example INI shipped with rocred (ex. filename: btnreplay.bmp / resource: IDB_REPLAY). It's called "focus", because it occurs when the button gains focus (tab or mouse-button pressed), if it would react to mouse-over, it would be called as such; mouseover/mouseout tracking is painful to add with the methods I know (TrackMouseEvent function), that's why i choose focus instead.
  3. Make sure you created the folder as following: .\WeeDiff.exe .\plugins\WeeDiffGen.dll .\plugins\WeeDiffGen\<your WDG plugins go here>
  4. https://sourceforge.net/projects/atwl/files/WeeDiffGen/
  5. Version 1.6.0 Per request, added support for providing the server with miscellaneous user information (requires user consent once). When enabled, requires modification of the login packet code on server-side to extract the url-style parameters from the t1 (token) field.
  6. What do you mean? If you do not like the option, just do not use it?
  7. Updated to 2.9.0, adds troubleshooting option for disabling hardware-accelerated graphics, detection of active mirror drivers (which prevent hardware-acceleration) and various tweaks to visuals and translations. New bits: IDCHECKBOX_HELDEVICE, "Turns hardware-accelerated graphics on and off.\n\nThis option is only for troubleshooting graphics card issues. When enabled, graphics card will not be utilized by the client for graphics rendering.\nNote: This option is NOT recommended for low and average system specification users." IDINFOICON_VIDEO_MIRRORDRIVER, "Warning: Mirror driver detected.\n\nYour graphics card cannot be detected when a mirror driver is active. This can be caused by an active VNC session, remote control server software or malware." TEXT_DLG_HELDEVICE, "Disable hardware-accelerated graphics"
  8. Version 1.5.0 Added support for skinning buttons. See the accompanied INI for details on design and restrictions.
  9. Version 1.4.0 Added support for background skinning, see the INI or first post for details.
  10. You might want to try this nightly release. It adds support for disabling hardware-accelerated rendering, see Graphics->Troubleshooting. Note, that the client performance might be pretty bad, or completely unusable; for some people testing this feature, the client even crashed.
  11. Random guesses: data.grf is write-protected (file attribute in properties) data.grf is in use (possibly by the preview window) data.grf is broken RO folder is not writable (location dependent)
  12. Unfortunately there is probably little I can do. Though I'll try to see, whether or not the client can be forced into using software rendering. Edit: The client will run with software renderer selected, but I wonder about the performance. I wasn't able to pull out more than 0.05-0.1 FPS (1 frame every 10-20 seconds) on my somewhat aged PC. But since it works, I'll include it as troubleshooting option.
  13. DX7E_P_EnumDeviceCallback: RGB Emulation [Microsoft Direct3D RGB Software Emulation] DX7E_P_EnumDeviceCallback: Not a hardware device [Microsoft Direct3D RGB Software Emulation] DX7E_P_EnumDriverCallback: DX7E_P_EnumDevices returned zero devices [Driver de vídeo primário] Your graphics card driver does not support any hardware rendering of DirectX7/DirectDraw. If newer 3D games run fine for you, it might be that NVIDIA dropped support for DirectDraw (newer DirectX versions use Direct3D for 2D rendering).
  14. You are likely to lack default settings in you RO folder's system folder. For Lua 5.0.2 it would be system\OptionInfo.lub (and dependent files) and for Lua 5.1.4 it would be system\LuaFiles514\OptionInfo.lub (and dependent files). Note, that just copying OptionInfo from savedata won't fix it.
  15. So far I do not see anything wrong with your configuration. Mind running a debugging application for the directx part of opensetup and provide the generated log (dx7edbg.txt)?
  16. Experimental Version 1.4.0 Support for background image and control resizing/moving. binary (replaced by a proper release)
  17. Can you please post "general" and "display" tabs of dxdiag, as well?
  18. Don't worry about it, that's normal. If it would exceed 7, then it might be reason for worry.
  19. Check out opensetup.log, there should be a hint what's wrong, though I just assume from the screenshot, that you ran it outside of a RO folder.
  20. For that case it would be <SHIFT+TAB>enter username<TAB>enter password<ENTER> Also: ENTER = Start ESC = Close Replay does not have any shortcut, but since you do not need to enter user/password for that, clicking should be more preferable.
  21. Not quite sure if I understand you, but you can already TAB between those two. The fastest login sequence would be: When user name is not remembered (user name textbox is selected on start): enter username<TAB>enter password<ENTER> When user name is remembered (password textbox is selected on start): enter password<ENTER>
  22. Please post a screenshot of the Display tab in dxdiag (run via Win+R). Scratch that, telling from the icons you use a Windows 8 incompatible OpenSetup version. Update to the latest.
×
×
  • Create New...