UPIS User Feedback

---

---

FAQ

If you have a question you would like to see posted, please send email to pkv@cs.cmu.edu

Why does the error message "Can not locate upisdll.dll" appear when I try to run "upis.exe"?

upis.exe searches the working directory to find the upisdll.dll that is loaded into UT2004. Either copy upisdll to the directory from which you are starting upis.exe, or change the working directory to the directory containing upis.exe and upisdll.dll.

Why do I get the error message "The procedure entry point FreeImage _SaveToMemory could not be located in the dynamic link library FreeImage.dll"?

This is caused by an incompatible version of FreeImage.dll being loaded in upisdll.dll. Rename or delete any version of FreeImage.dll in the same directory as ut2004.exe.

Why does the following error appear when I try to run upis.exe? "The application failed to initialize properly (0xc0150002). Click on OK to terminate the application."

This usually indicates that the MS Visual C++ 2008 Redistributable has not been installed. Download and install the redistributable from Microsoft. Some versions of UPIS include the installer vcredist_x86.exe (for 32-bit x86 architectures).

When I launch run.bat, a console briefly appears, but UT2004 never runs.

Check the two string parameters in run.bat. The first must be a valid path to ut2004.exe, while the second must be a proper configuration string for UT2004, and must include a space as the first character. An example of a well formed string would be the following:

" DM-compWorldDay4b_250?spectatoronly=1?game=USARBot.USARDeathMatch?TimeLimit=0?quickstart=true -ini=usarsim.ini"

Why doesn't UPIS support any 64-bit Windows OS?

UPIS uses the Microsoft Detours library to hook DirectX calls. Unfortunately, the free version of Detours is restricted to 32-bit operation. We plan to fix this by changing the hook code to use the MHook library in a future version.

When I minimize UPIS, why does it stop sending images?

It seems that minimizing UPIS completely causes most host applications (like UT2004) to stop rendering frames. Right now, UPIS cannot capture frames if the application is not rendering them, so minimizing the image server will prevent frame capture. However, the window will still render if it is occluded or off screen, so it is possible to move it out of sight or cover it with another window. In the future, UPIS should intercept minimization calls and redirect them to hide the window rather than fully minimizing it.

Comments

If you have a comment you would like to see posted, please send email to pkv at cs.cmu.edu

[FIXED] Ambiguity in JPEG format options.

Arnoud Visser has suggested that the AVERAGE image format be replaced with the FAIR image format to avoid ambiguity with the NORMAL format: (This change was incorporated on 2009-05-29)

• old format tags: -f {RAW, SUPER, GOOD, NORMAL, AVERAGE, BAD}
• new format tags: -f {RAW, SUPER, GOOD, NORMAL, FAIR, BAD}

Known Bugs

If you have a bug you would like to see posted, please send email to pkv at cs.cmu.edu

"Debug" configuration creates broken binary.

• When compiled under the Debug configuration, Visual Studio will complete the build with success, but the resulting executable will never send images when requested. As a workaround, please use the Release configuration to build the source code.

[FIXED] If UPIS is run within 2 minutes of exiting after a WSS crash, a "Bind Failed" message appears.

• The addition of the SO_REUSEADDR flag on 2009-05-29 fixes this problem. For older versions, waiting two minutes should allow the socket to time out and UPIS will run normally again.

Sometimes, if UPIS is shutdown, a UT2004.exe process may still run in the background.

• So far, we have been unable to replicate this problem.