• Content count

  • Joined

  • Last visited

Community Reputation

119 Good

About Wulfmaer

  • Rank

Profile Information

  • Gender

Recent Profile Visitors

948 profile views
  1. That tunnel, and the two north out of the lake to it's northern end are all knarr only.
  2. I notice on the test server that the catseyes run through the tunnel. Does this mean the new highway system will include tunnels? I assume it does, some early indication of what will be required for a tunnel to be considered a highway would be very nice. But, please bear in mind that some of the longer routes on Xanadu currently make use of single tile wide tunnels (with both walls reinforced), so if such tunnels will not be able to be used as part of a highway we will need some way of removing the reinforced wall to widen them.
  3. Caption: "This year's single hell hound powered horseless carriage growls along on minced horse meat"
  4. Are you using the unstable client, and are you using the select bar to mine? There is an issue, reported elsewhere, and still unfixed where using the select bar to mine a wall tile will start mining the floor. When this happens the select bar title is unchanged, but clicking on a floor tile still shows the mine up and down actions. A way to prevent this problem from causing issues is to either use mine up, or down, or mine using a keybind.
  5. I built a stone altar before I left last night, the only silver I could find was quite low quality
  6. The rift is in G20, at http://wurmonlinemaps.com/Maps/Xanadu?x=5379&y=-2140&z=6 The easiest access is probably by the 'Road to the North' leaving the Emerald Highway at guard tower 'LIGO G19'.
  7. Can't even connect - but that is probably a good thing... Keenan, on IRC, just said they are aware of the problem.
  8. Don't seem to be able to hit anything on the 'cooking' server now. Getting '[12:16:39] You cannot fire the stone brick to there, you are not allowed.' even when the catapult would not hit anything! Probably something to do with the fences, and catapults, being in the perimeter of Now We Are Cooking? --- This does not appear to be anything to do with being in the perimeter - just built a catapult on the beach, outside the perimeter - and am getting the same message trying to fire the catapult from there.
  9. @Samool - Have managed to recreate the problem with the current unstable client 4.00-5cb0867. Machine details are as above. The problem seems to start being noticeable after about 30 minutes game play. I also managed to capture a short clip showing the problem. Console log
  10. Silly question... On the 'cooking' PVE server, at the Catapult Firing Range - am I meant to be able to be able to destroy part of Budda's Shed? Have managed to destroy the internal floor, and cause damage to one of the house walls. The wiki sayes This building is in the perimeter of Now We Are Cooking, so I'd expect the off limitation to apply. Even if it was on deed I should not be able to catapult it, as the deed does not give destroy building permission.
  11. Not likely to be related to Windows 10, as I'm seeing the same problem running on macOS. I notice that the unstable client does not appear to be saving the keybindings file in the character directory despite saying it has in the logs , but the current stable client does.
  12. Not managed to recreate this problem today. So, looks as if it has been fixed. Scrub that - just jumped over to the test client and am getting the wireframe flicker with a catapult. So, test client build 4.00-584db20 - iMac (27" late 2013), GeForce GTX775M, macOS Sierra 10.12.4 - default macOS video driver. However with the NVIDIA web drivers (367.15.10.45f01) I am not seeing the wireframe issue. The only difference I see, at a glance, is that with the NVIDIA web drivers we get 'GLSL max fragment uniforms: 4096 (4096)' while with the default drivers we have 'GLSL max fragment uniforms: 2048 (2048)'. N.B. There are issues with using the NVIDIA web drivers with some other applications.
  13. I am using a late 2013 27" iMac - NVIDIA GeForce GTX 775M. Both the default macOS 10.12.4 and NVIDIA Web Drivers 367.15.10.45f01 show this problem. Forgot, I applied the latest macOS, and NVIDIA drivers, earlier - not seen it since then not sure if the update fixes it, or if being a gnome is. It seems to be more common when on horse back - will add console log when it happens again, but don't recall seeing anything there at the time it happens.
  14. still a problem...
  15. No fooling - our gnomic overlords have been experimenting with our genome while we slept