Ai4rei

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"

Version 1.5.0 Added support for skinning buttons. See the accompanied INI for details on design and restrictions.

Version 1.4.0 Added support for background skinning, see the INI or first post for details.

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.

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)

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.

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).

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.

As stated, opensetup.log contains the reason.

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)?

Experimental Version 1.4.0 Support for background image and control resizing/moving. binary (replaced by a proper release)

Can you please post "general" and "display" tabs of dxdiag, as well?

Don't worry about it, that's normal. If it would exceed 7, then it might be reason for worry.

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.

I hope you are kidding.

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.

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>

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.

Thank you. Updated to 2.8.3, fixes and updates translations, no functional changes.

Have you diffed 'restore login window' by any chance? If so, the auto-login won't work. The setup looks fine to me. Version 1.3.0 Added settings to lock down some features, intended for paranoia defaults in embedded INI (see the included INI for details). Fixed the client could fail with error "Requires elevation to execute" when using Start or Replay buttons. Anyone interested in some basic skinning (background), something to the effect of RO Patcher Lite skinning (put a bgskin.bmp file next to the .exe to try) ? Version 1.3.1 Fixed missing button labels, when user name was saved.

RO Credentials About Simple and tiny client launcher+login. Has no prerequisites and runs on all Windows versions. Known Issues [aavc] This tool is not safe for computers running Avast Anti-Virus. Download binary, reference source Q & A Is it customizable? Yes. How? With resource editing tools, such as ResourceHacker. All text and icons can be customized. Settings can be edited in an INI file (included). What is "reference source"? You cannot compile it (unless you provide the missing components), but see what functionality the latest binary contains. I want it to be xyz.exe, but it does not read the INI file. Why? You have to match the INI name to the EXE name. rocred.exe -> rocred.ini mytest.exe -> mytest.ini How can I embed an INI file into the EXE? Add the INI file as RCDATA resource named CONFIG with ResourceHacker. How do I use background skinning? Create a file named bgskin.bmp (magenta #ff00ff is considered transparent). You can also embed the file as BITMAP resource with the name BGSKIN. Window size is adjusted to the bitmap size, position of controls must be set in the INI. Buttons can be skinned as well, see the INI for names. Can I add custom buttons, if so, how many? Yes, see the INI template for details. There is no defined limit on how many, the only constraints are available memory, GDI resources and INI size limit on some platforms. By the way, custom buttons can be skinned as well. Why does the client not auto-login when I press "Start"? The client must be 2010-08-04aRagexeRE or newer and must not have the "Restore Login Window" patch. This work is licensed under a Creative Commons Attribution-Noncommercial 3.0 Unported License.

Administrator and compatibility mode have no effect on OpenSetup. Try the lastest version. If it still cannot detect your video modes, please post a screenshot of the display tab in "dxdiag" (start via Win+R).

Thank you both very much!Updated to 2.8.2, fixes a Lua loading bug and adds sanity checks for Lua for people with Lua errors in client (and messed up installs). Also updates above translations. There is no public 2.8.1, because it was not stable. New bits: TEXT_ERROR_INSANE_ENGINE, "Selected settings engine has determined, that your installation state will interfere with the correct loading and saving of settings.\r\n\r\nSee opensetup.log for details."

Click the [?] in the upper right, then click on the option you want to know about.

Updated to 2.8.0, adds configurable "HKLM to HKCU", visual resolution input and a batch of bug-fixes. For details see website.