http://dev.ryzom.com/ 2013-02-07T22:46:54+01:00 Ryzom Core Development Site Redmine http://dev.ryzom.com/issues/1522 2013-02-07T22:46:54+01:00 DuDraig <p>Windows 7 x64 in the ryzom.com game.</p> <p>When moving your character forward by holding down the forward keyboard key (in my case 'w') and using the mouse right-drag to change direction, sometimes the drag is spuriously canceled and the right-click popup menu ("Free Look" | "Move") appears all on its own without lifting the right mouse button. This can also happen when you just press the right-mouse button without releasing when intending to start a drag. This behavior is unique to this game on my computer.</p> The expected behaviors are: <ul> <li>If you press the right-mouse button, drag outside a defined small rectangle, and then release, only the direction change function should happen and the right-click popup menu should not appear at any time during the drag or after the right mouse button is released.</li> <li>If you press the right-mouse button, while the button remains pressed the right-click popup menu should not appear regardless of whether the mouse has moved or not.</li> <li>If you press the right-mouse button, do not drag the mouse outside a defined small rectangle, and then release, the right-click popup menu should appear.</li> </ul> <p>Because of the technical nature of this problem, I was asked in-game by a CSR to report it here.</p> http://dev.ryzom.com/issues/1464 2012-04-26T04:05:44+02:00 shackra jorgean@lavabit.com <p>Please write about the source code layout in order to make easy hack into the Ryzom Core source code the wiki page exists <a class="external" href="http://dev.ryzom.com/projects/ryzom/wiki/SourceCodeLayout">http://dev.ryzom.com/projects/ryzom/wiki/SourceCodeLayout</a> (I created it :P)</p> http://dev.ryzom.com/issues/1347 2011-08-20T12:37:01+02:00 Potlatch sevmek@free.fr <p>Hi,</p> <p>Well, i'm not really sure it qualifies as a bug. Still each time I startup ryzom client in window mode, it grabs the mouse pointer and put it somewhere else. I find it quit annoying and don't see the purpose of it in the window mode.</p> <p>Official client on Ubuntu 10.04</p> <p>Best regards.</p> http://dev.ryzom.com/issues/1267 2011-03-25T02:00:40+01:00 rti <p>When reactivating the window with a mouse click, a click event with the old mouse position is fired.</p> <p>Reproduce:</p> <ul> <li>open ryzom client</li> <li>click "Manage Account" or anything else that opens an external browser</li> <li>reactivate the ryzom client window with a click</li> <li>the "Manage Account" button is clicked again and another browser opens</li> </ul> http://dev.ryzom.com/issues/1245 2011-01-23T16:56:05+01:00 Qantourisc <p>When multiple CGDMouseMove's are received in 1 frame, all previous CGDMouseMove's are discarded.<br />Bug is most visible on very high (1000HZ) sample rates. Lower framerate also increases the visibility of this bug.</p> <p>Note: From time to time I explain things poorly, if so, ask, and I will explain it in a different fashion.<br />Also recommend your read the patch and source code, this will clear up a lot.</p> <p>What happens:<br /><strong>Bug 1 (This only affected non-mouse-smoothed players):</strong><br />In this code _MouseDeltaAX is set to _MouseDeltaAX = x * ClientCfg.FreeLookSpeed;<br />It should however be _MouseDeltaAX += x * ClientCfg.FreeLookSpeed;<br /><strong>Bug 2 (Affecting all):</strong><br />if (fabs(_MouseDeltaAX) > epsilon) is used both to set and UNSET _MouseAngleX.<br />As a result, a subsequent update of a mouse-move of (X=0,Y=1) would reset the fact that X moved.<br /><strong>Bug 3 (Affecting all):</strong><br />CEventsListener::getMouseAngleY() doesn't reset the delta angle.<br />This in combination with bugfix-1 would result in an ever-increasing delta.<br /><strong>Possible bug 4:</strong><br />CUnixEventEmitter::emulateMouseRawMod might be called to often then required.<br />As a result it's not always sane to flush the XEvents.</p> <p><strong>Suggestion 1:</strong><br />I also recommentdropping isMouseAngleY/X and only using getMouseAngleX/Y then detect float == 0 on that. (If this always works.)<br />(No risk of floating point errors (at least I think), because it will always be reset after reading the to-proccess-angle.)</p> <p><strong>Suggestion 2:</strong> (Topping Suggestion 1)<br />Move the check "if (fabs(_MouseDeltaAX) > epsilon)" CEventsListener::updateFreeLookPos to EventsListener::isMouseAngleX<br />This way it's only ran ONCE instead of every time :)<br />(This also removed the entire suggestion 1 in a cleaner fashion.)</p> <p><strong>Note 1:</strong><br />In the current state of affairs, you MUST call getMouseAngleX after isMouseAngleX to keep a sane state.</p> <p><strong>Note 2:</strong><br />This should also be fixed for CEventsListener::updateCursorPos ... this suffers from the same bugs, but this isn't too bad. (No bad effects.)</p> <p>If suggestions and notes are accepted, I will also make a fix for those if you desire.</p> http://dev.ryzom.com/issues/1243 2011-01-19T16:27:46+01:00 lubos <p>Each binary should have a man page.</p> http://dev.ryzom.com/issues/1183 2010-11-09T23:31:34+01:00 rti <p>This happens only in fullscreen mode. <br />Events are even reported, if the mouse is moving over another window, so they get reported "through" the other window.</p> <p>To fix this, NeL need to know whether the application is currently active or not. Currently, this is not implemented on Mac.</p> http://dev.ryzom.com/issues/1056 2010-08-05T03:17:17+02:00 rti <p>In FreeLook mode, the mouse is hidden and the position is reset to 0.5/0.5 after every move (raw mode emulation on X11).<br />When the FreeLook mode ends and the mouse shows up again, the old position (before hiding the mouse) should be restored.</p> <p>This works well if the mouse is only hidden for ~0.5sec. It works as well if the mouse stays hidden for ~5sec.</p> <p>But it does not work, if the mouse is hidden for like 2sec and not moved! It shows up at 0.5/0.5 then.</p> http://dev.ryzom.com/issues/997 2010-06-22T15:02:31+02:00 kerozcak kaczorek@gmail.com <p>When client disconnects (FS lost) it's required to restart client. There should be reconnect option without restarting client.</p> http://dev.ryzom.com/issues/969 2010-06-07T21:07:39+02:00 Enoril <p>How generate this bug:<br />- in client, show identity frame (shortcut P)<br />- click on title combobox<br />- use shortcut P to hide the identity frame<br />- combobox list is still here</p> http://dev.ryzom.com/issues/968 2010-06-07T21:02:46+02:00 Enoril <p>How generate this bug:<br />- log into shard<br />- kill shard (FS for example)<br />- client show "FS lost" <br />- click on "Quit" button<br />- if you click on "Character selection", the waiting frame appear<br />-> you can do anything from that moment (except kill client via tasks manager)</p> <p>(if you click on "Quit ryzom" > no problem, the client exit...)</p> http://dev.ryzom.com/issues/967 2010-06-07T20:55:06+02:00 Enoril <p>How generate this bug: <br />- switch to dual screen (bottom screen is the main screen, top screen is the extended screen),<br />- move client in windowed mode in 2nd screen (top)<br />- quit client <br />- position x,y of the windows is stored in configuration file<br />- desactivate dual screen (or reduce screen resolution)<br />- launch client<br />-> client is launch, invisible (because it is at the top) and can't be moved</p> http://dev.ryzom.com/issues/954 2010-06-02T19:41:03+02:00 sfb matt.raykowski@gmail.com <p>At least one tool (sheets_packer) uses the client_sheets library directly but also requires the following source files directly from the client:</p> <ul> <li>code/ryzom/client/src/continent_manager_build.cpp</li> <li>code/ryzom/client/src/continent_manager_build.h</li> <li>code/ryzom/client/src/sheet_manager.cpp</li> <li>code/ryzom/client/src/sheet_manager.h</li> </ul> <p>Move these four files to client_sheets. There is the possibility that more tools and applications will arise that load the client sheets directly and thus may need these loaders as well.</p> Optional: <ul> <li>Move client_sheets entirely to code/ryzom/common/src.</li> <li>Move client_sheets code into a unique namespace.</li> </ul> http://dev.ryzom.com/issues/938 2010-05-25T10:09:50+02:00 kervala kervala@gmail.com <p>For the moment, we have 10 MB for low quality textures for entities and 40 MB for high quality ones.</p> <p>That's declared in code/ryzom/client/src/init_main_loop.cpp line 150 :</p> <pre> // Size in Mo of the cache for entity texturing. #define ENTITY_TEXTURE_NORMAL_MEMORY 10 #define ENTITY_TEXTURE_HIGH_MEMORY 40 </pre> <p>We should remove these defines and implement a dynamic algorithm to use actual video memory size.</p> http://dev.ryzom.com/issues/843 2010-05-06T22:39:25+02:00 browser_ice <p>Today, May 6th, I have just downloaded the Ryzom Client Core and upon starting it (as is) I got a crash from the very beginning. Nothing was displayed, nothing was asked:</p> <p>A failed assertion occurs<br />ProcName: client_ryzom_r.exe<br />Date: 2010/05/06 16:18:03<br />File: .\driver_direct3d_shader.cpp<br />Line: 410<br />FuncName: NL3D::setFX<br />Reason: "drv->activeShader (&#38;s)" <br />-------------------------------</p> <p>No log<br />-------------------------------</p> <p>Windows XP Pro SP3<br />2Gb memory<br />ATI Radeon 9600XT - Catalyst 8.4<br />No problems playing commercial game</p>