Custom Query (16363 matches)
Results (1165 - 1167 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11468 | obsolete | Minecraft Mouse Issues (disappearing cursor; invisible pointer) | ||
| Description |
Ubuntu host (and lots of others too); XP-x86 guest; Java version does not matter, nor does the version of the game. The issue seems widespread and recognized at large. [What is Normal] Moving around using the mouse, as with lots of other first-person games, movements are way off whenever mouse integration is enabled. To solve this, HostKey+I has to be pressed in order for it to be disabled. [What is the problem] However, deactivating mouse integration makes the game playable, up to the point where menus (an integral part of the game) are accessed, at which point there is no crosshair, although a mouse pointer is lacking. In other words, one has, often several times per minute, to toggle mouse integration on and off, in order for crafting (an integral part of the game) to be performed. Besides that, the game works fine. LAN servers are ran over here without any problems either. Great frame rate; great experience, besides the irritating (and most-frequent) need to toggle mouse integration. Mouse-pointer options (such as enabling trails or showing pointer location pressing ctrl) have been tried but have not been of any help, as there are absolutely no sings of the mouse pointer inside menus. |
|||
| #12647 | obsolete | [3D acceleration] Elasto Mania (video game) virtualization slowness | ||
| Description |
Host: Ubuntu; guest: XP. Experimental 3D-acceleration drivers have been installed, and then set to "enabled" in the VirtualBox machine video settings. The game (demo version, from http://www.elastomania.com/elma.exe) has been installed on a fresh system install. As is the case with native XP machines, there is some frame choppiness present. In other words, things are not as smooth as they should be, and some frames are (as a rule) dropped here and there. Virtualization, therefore, is representative of the original experience in this regard. The problem lies in the experience produced using the "unsmoothness" fix, which works wonders in native XPs. This fix (links are provided in the next paragraph) can be applied by running the ElmaXP exefile from the game folder. It works, the author said (although he said no more than that), by "tuning the system timer on game start, then tuning it back to its normal state on game-process close." http://nh.gorodok.net/ElmaXP.zip (elmaxp file inside); http://zworqy.com/elmaguide/files/ElmaXP.zip (elmaxp file inside); http://kopasite.net/up/0/ElmaXP.exe.txt (remove the .txt extension). The problem is this: using the fix (so the game can run smoothly on post-98 systems), makes it run in slow motion (the speed of the timer, for example, is more than halved). To recapitulate, without ElmaXP.exe under virtualization, there is choppiness (therefore, same behavior as before). However, with ElmaXP.exe under virtualization, the game is significantly slowed down (unexpected behavior). How come? (I am curious.) Notes: I have tried various vboxmanage commands, such as: VBoxManage setextradata "VM name" "VBoxInternal/TM/TSCTiedToExecution" 1 (did not change anything); VBoxManage setextradata "VM name" "VBoxInternal/TM/WarpDrivePercentage" 200 (sped up elma.exe, as expected, although did not change much of the slowness of the good [smooth] version, being elmaxp.exe); VBoxManage setextradata "VM name" "VBoxInternal/Devices/VMMDev/0/Config/GetHostTimeDisabled" (did not change anything either). Disabling vertical synchronization did not solve the issue (nor did it change anything). |
|||
| #17913 | duplicate | documentation indicates (incorrectly) that NAT VM can't communicate with host over network -> duplicate of #16912 | ||
| Description |
https://www.virtualbox.org/manual/ch06.html#networkingmodes Table 6.1 "VM ↔ Host" column has a "–" symbol for NAT, which is misleading, as the guest VM is able to communicate over the network with the host, in fact bypassing the host's firewall (which, btw, seems like a security issue which should also be noted in the documentation, particular since NAT is the default); the guest VM, for example, can ping the host's IP. The host, however, can't ping the guest VM's IP. |
|||

