<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://www.seatribe.se/bt/bugzilla.dtd">

<bugzilla version="4.2"
          urlbase="http://www.seatribe.se/bt/"
          
          maintainer="fredrik@dolda2000.com"
>

    <bug>
          <bug_id>3</bug_id>
          
          <creation_ts>2012-06-28 22:12:00 +0200</creation_ts>
          <short_desc>Crash caused by fire, or more likely smoke effects</short_desc>
          <delta_ts>2012-06-30 07:58:37 +0200</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Salem</product>
          <component>Client</component>
          <version>unspecified</version>
          <rep_platform>PC</rep_platform>
          <op_sys>Windows</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WONTFIX</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>---</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="staxjax">staxjax</reporter>
          <assigned_to name="loftar">fredrik</assigned_to>
          

      

      

      

          <long_desc isprivate="0">
            <commentid>6</commentid>
            <who name="staxjax">staxjax</who>
            <bug_when>2012-06-28 22:12:38 +0200</bug_when>
            <thetext>Smoke effects caused by lit fires causes clients on some textures on some computers to dissapear, and in some cases it will just crash the client.  More information can be found here:

http://forum.paradoxplaza.com/forum/showthread.php?603700-Disappearing-textures-User-Interface-Makes-game-unplayable-Likely-caused-by-FIRE</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <commentid>7</commentid>
            <who name="staxjax">staxjax</who>
            <bug_when>2012-06-29 01:09:33 +0200</bug_when>
            <thetext>Argh, no way to edit description?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <commentid>8</commentid>
            <who name="loftar">fredrik</who>
            <bug_when>2012-06-29 02:16:11 +0200</bug_when>
            <thetext>#1: Nope; issue trackers mostly work like that. If the description is insufficient or incorrect, append to or correct it in subsequent comments. If the whole issue turns out to be incorrect, submit a new one instead, link to it from the old one and mark the old one as INVALID.

As for the linked topic, however, it describes at least two separate issues; one graphical glitch and one crash bug. I&apos;ll assume from the subject that this issue tracks the crash bug.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <commentid>9</commentid>
            <who name="loftar">fredrik</who>
            <bug_when>2012-06-29 02:18:58 +0200</bug_when>
            <thetext>As for the crash bug, please find out what OpenGL version the system running that client is running.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <commentid>11</commentid>
            <who name="staxjax">staxjax</who>
            <bug_when>2012-06-29 06:15:00 +0200</bug_when>
            <thetext>It using openGl 1.5</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <commentid>13</commentid>
            <who name="loftar">fredrik</who>
            <bug_when>2012-06-29 23:42:27 +0200</bug_when>
            <thetext>It would help if I had the actual error report by the client, but I cleared the reports just yesterday when I updated the client along with the combat update.

Can you please tell the affected player to get the crashed in that way again so that it sends a new error report, and then tell me the name of that user?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <commentid>14</commentid>
            <who name="staxjax">staxjax</who>
            <bug_when>2012-06-30 01:33:54 +0200</bug_when>
            <thetext>Crashed a few minutes ago.  Username is Mushibag.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <commentid>15</commentid>
            <who name="loftar">fredrik</who>
            <bug_when>2012-06-30 02:11:43 +0200</bug_when>
            <thetext>That error report indicates that he is using OpenGL 1.3, though. The client requires at least OpenGL 1.4.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <commentid>16</commentid>
            <who name="staxjax">staxjax</who>
            <bug_when>2012-06-30 03:36:00 +0200</bug_when>
            <thetext>I double checked driver version on about 10 different sources and they all say the card has support for openGL 1.4.  It is a ATI Radeon 9250.  Would there be any other reason why the report would say openGL 1.3?

Also, do you think this same issue is most likely affecting the texture/shading issue on the other &apos;fire bug&apos; reports?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <commentid>17</commentid>
            <who name="loftar">fredrik</who>
            <bug_when>2012-06-30 04:23:19 +0200</bug_when>
            <thetext>Even if the card supports OpenGL 1.4, the driver has to support it as well, and many times it is merely the driver which is outdated or inferior (for instance, the nVidia drivers that ship with Windows as compared to those made by nVidia themselves).

However, in this case, I am left wondering which sources you checked. Wikipedia&apos;s article on the card[1] says the card is only capable of OpenGL 1.3. However, do try to download the latest drivers directly from ATI. It might just be that they support OpenGL 1.4.

 [1] &lt;http://en.wikipedia.org/wiki/Radeon_R200&gt;</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <commentid>18</commentid>
            <who name="staxjax">staxjax</who>
            <bug_when>2012-06-30 07:26:23 +0200</bug_when>
            <thetext>I use wikipedia for one source, but under the entry Radeon instead:
http://en.wikipedia.org/wiki/Radeon

I&apos;m thinking that the openGL support would be akin to the problem I was having on my netbook.  As the windowsXP drivers may only support 1.3, but with a windows7 upgrade there are most likely newer drivers available that do support openGL 1.4.

I was having a completely different problem altogether there though (error code 1280/1281), but when I did upgrade the OS/Drivers I could play and I noticed that the smoke effects do not show up at all...which doesn&apos;t bother me but got me to thinking of a work around:

If there were a console command to disable the smoke effects then it could be entered during character selection if people are experiencing this, and later when the options menu has full functionality it could have an option there as well.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <commentid>19</commentid>
            <who name="loftar">fredrik</who>
            <bug_when>2012-06-30 07:58:37 +0200</bug_when>
            <thetext>I&apos;m jumping through enough hoops as it is to support OpenGL 1.4, so I really don&apos;t want to complicate things further by extending support to 1.3 as well, so if you don&apos;t mind horribly much, I&apos;m going to close this bug as WONTFIX, as it doesn&apos;t seem to be a client bug under the premise that it requires OpenGL 1.4+.

If anything, it could be argued that the client should warn immediately upon launch if one isn&apos;t using a 1.4+ driver, but in that case, that&apos;s a separate issue.</thetext>
          </long_desc>
      
      

    </bug>

</bugzilla>