Jump to content
Eternal Lands Official Forums


  • Content count

  • Joined

  • Last visited

About psihokiller4

  • Rank
  • Birthday 08/02/1988

Profile Information

  • Gender
  1. linux: graphic problems NPC scrached trough whole map

    ok it's verified that counters have no effect on it I'm still having same problems some times did a card reset tho the first days it was suggested saying just for letting you know counters have no effect on it yeah it felt strange as I even went verified few times if it's it and was correct well this topic can be closed
  2. linux: graphic problems NPC scrached trough whole map

    interesting how to reset the card? yea I know counters shouldn't have any influence but it felt so strange when it worked
  3. linux: graphic problems NPC scrached trough whole map

    thanks I thought too that counters have nothing to do with graphic too but I do not understand why could I do work around exactly with counters and nothing else :S EDIT: the problem is I don't know how to reproduce the bug once I do a work around :S and I think that new SSD disk doesn't have anything to do with this too I'll add it in 1. post
  4. my info: uname -a Linux military-desktop-linux 2.6.32-38-generic #83-Ubuntu SMP Wed Jan 4 11:12:07 UTC 2012 x86_64 GNU/Linux Video card: ATI Radeon HD 4800 Series Vendor ID: ATI Technologies Inc. OpenGL Version: 3.2.9756 Compatibility Profile Context Supported extensions: GL_AMDX_name_gen_delete GL_AMDX_vertex_shader_tessellator GL_AMD_conservative_depth GL_AMD_draw_buffers_blend GL_AMD_performance_monitor GL_AMD_seamless_cubemap_per_texture GL_AMD_shader_stencil_export GL_AMD_texture_cube_map_array GL_AMD_texture_texture4 GL_AMD_vertex_shader_tessellator GL_ARB_color_buffer_float GL_ARB_copy_buffer GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_fragment_coord_conventions GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_map_buffer_range GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_seamless_cube_map GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_snorm GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_ATI_draw_buffers GL_ATI_envmap_bumpmap GL_ATI_fragment_shader GL_ATI_meminfo GL_ATI_separate_stencil GL_ATI_texture_compression_3dc GL_ATI_texture_env_combine3 GL_ATI_texture_float GL_ATI_texture_mirror_once GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_compiled_vertex_array GL_EXT_copy_buffer GL_EXT_copy_texture GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_histogram GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_wrap GL_EXT_subtexture GL_EXT_texgen_reflection GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_buffer_object GL_EXT_texture_buffer_object_rgb32 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_shared_exponent GL_EXT_texture_snorm GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_IBM_texture_mirrored_repeat GL_KTX_buffer_region GL_NV_blend_square GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_explicit_multisample GL_NV_primitive_restart GL_NV_texgen_reflection GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays GL_WIN_swap_hint WGL_EXT_swap_control installed system on 2 discs: SSD mount point / - 25 GB HDD mount point /swap - 4GB HDD mount point /tmp - 4GB HDD mount point /home - 40GB and boot was added on SSD eternallands-data 1.9.3ubuntu1 eternallands-sound 1.9.2ubuntu4 eternallands 1.9.3ubuntu1 I copyed all my previous counters and everything from the system I have "deleted" it well I had problems: and some alts had this and some didn't so I did: 1. delete everything that game saves on my disc: /home/username/.elc/pk counters_altname.dat quest_altname.list quest_altname.log recipes_altname.dat spells_altname.dat recipes_altname.names 2. run game than it worked fine 3. copy everything back had same issues 4. I deleted only first 3 counters_altname.dat quest_altname.list quest_altname.log 5. run game work fine 6. copy everything back and delete only counters works fine finally I figured out what's worong and some workarounds so I wanted to report that old counters aren't compatible with new client so I copy counters back as my plan was to make screenshots and it works WTF now I have did some system changes: Commit Log for Tue Feb 14 01:08:52 2012 Upgraded the following packages: dbus (1.2.16-2ubuntu4.2) to 1.2.16-2ubuntu4.3 dbus-x11 (1.2.16-2ubuntu4.2) to 1.2.16-2ubuntu4.3 fglrx-modaliases (2:8.723.1-0ubuntu5) to 2:8.723.1-0ubuntu6 and the bug had reappeared so I deleted counters to see if it works and it works and after that I have copied counters back and had same problems and now I have made screenshots and now I do: 1. close client with problems 2. #save with client that hasn't got this problems 3. copy counters back it works fine now can someone explain what I did to do a work around?!?!? I'm sorry I really do not understand I hope I did good "foot prints" what I did to somehow figure this things out PS. I had never had this problems before EDIT: I'm not sure but I think it's happening to same 2 alts
  5. Competition Chinese new Year 4710 on 23. January 2012

    No not correct - how were supposed to figure THIS particular set of coordinates?! where was the blue crystal supposed to be on the map? Ok, looking again at the map I did find the following 1s that would serve as a start place (=blue crystal) for finding a bag at that location - but I cannot imagin any way we would have figured THESE being ste place to start/put the crystal: - digit No. 31 in the row starting with the '8' character - digit No. 38 in the row starting with the '8' character BUT the first one doens't havy ANY connection (path of 1s) to the bottom row - and the second one doesn't lead to three potential places (1s at the bottom row) for the hyperbag, but only two. Could we have some explaination of your logic for that? start at number 8 + means 8 is char and start is right after number 8 witch means 00111000 = 8 so start is at first 1 you can see the next character is: 00000011 I know it's a bit difficult about map and I did a mis calculation by my self witch I'm very sorry it's 93,63 not 94.63 otherwise I tried to help as much as I could ... 011101000110100001101001011100110010000001101001 t h i s i 011100110010000000100000010011010100000101010000 s M A P 011100110111010001100001011100100111010000100000 s t a r t 011000010111010000100000011001010110100101100111 a t e i g 011010000111010001101110011101010110110100101011 h t n u m + 001110000000001101110011010100110101010001000001 8 s S T A 010100100101010000010101011100100110010100100000 R T r e 011101000111110100100000011001000111001001101001 t } d r i 011010100110101000110000001110010110111101110101 j j 0 9 o u 010100100010000000001110000001000010001100110010 R # 2 001101000011011000100011101100000110110001110100 4 6 # ° l t 011010010110111000101000100011111010000000101110 i n ( ? . 010001000100100101000111001000000110100101110100 D I G i t
  6. Competition Chinese new Year 4710 on 23. January 2012

    does this mean stros found the location of IP or raistlin you need to verify please
  7. Competition Chinese new Year 4710 on 23. January 2012

    yes correct
  8. Competition Chinese new Year 4710 on 23. January 2012

    totally wrong maybe you could try 1 number that is missing looooool
  9. Competition Chinese new Year 4710 on 23. January 2012

    Actually when using Opera on Win7 with no strange options of any kind known to me I see all 0s and 1s as same width. But yes, on Notepad thats the case for sure. correct
  10. Competition Chinese new Year 4710 on 23. January 2012

    very good this is how you should read the map congratz now!!! very important try using notepad as it's char 1 and char 0 has same lengths - on forum they don't have same lengths 0 is longer than 1 congratzzz... you still have 2 things to get it till you get 10 EWEs will add 1 hint - sorry for long being gone
  11. Competition Chinese new Year 4710 on 23. January 2012

    I'm going to post only correct - partionally correct or wrong posts that have some same or clue that's correct from different aproach by accident wrong
  12. Competition Chinese new Year 4710 on 23. January 2012

    wrong wrong and correct wrong correct wrong
  13. Competition Chinese new Year 4710 on 23. January 2012

    partionally wrong
  14. Competition Chinese new Year 4710 on 23. January 2012

    [PM from Lalaith: I tried to find the coords from the pictures in C2 portalsroom. 70,70 leads to NRM. 98,132 is near IotF. 94,70 and 98,63 are not near...] [PM from Lalaith: ... any exit]