Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - AryHann

Pages: [1] 2 3 4
1
The Hydlaa Plaza / Some greetings after many months
« on: March 21, 2009, 02:32:47 pm »
Hello!!!

For the ones that remember about me, I just want to say hello and hope that everything is alright!

Hugs
Arianna

2
Then, follow this procedure!

1. open planeshift client properties menu (right click on the client)
2. change user settings by clicking "edit" and allow all users to have full access
3. click compatibility tab, and on the pull down menu select Windows XP Service Pack 2 or any operating system that may work if XP is not available. You must click a check box to do this. Then click ok and it should work

Thanks to Jate for the help :-)
Arianna

3
Crash Number:0766F664
Description: Rendering issue
BT:>   stdphyslayer.dll!celEntityFinder::`vbtable'()    C++
    rendstep_std.dll!csGenericRenderStep::Perform(iRenderView * rview=0x08b4ba10, iSector * sector=0x1a27d64c, iLight * light=0x00000000, iShaderVarStack * stacks=0x00a1dc70)  Line 581   C++
    rendstep_std.dll!csGenericRenderStep::Perform(iRenderView * rview=0x00a16368, iSector * sector=0x00000300, iShaderVarStack * stacks=0x00000000)  Line 309   C++
    psclient.exe!csView::Draw(iMeshWrapper * mesh=0x00000000)  Line 160 + 0x18 bytes   C++
    psclient.exe!psCamera::Draw()  Line 699   C++
    psclient.exe!psEngine::HandleEvent(iEvent & ev={...})  Line 786   C++
    psclient.exe!psEngine::EventHandler::HandleEvent(iEvent & ev={...})  Line 222   C++
    psclient.exe!csEventTree::Dispatch(iEvent & e={...})  Line 576 + 0x7 bytes   C++
    psclient.exe!csEventTree::Notify()  Line 547   C++
    psclient.exe!csEventQueue::iTypedFrameEventDispatcher::HandleEvent(iEvent & __formal={...})  Line 262 + 0x36 bytes   C++
    psclient.exe!csEventTree::Dispatch(iEvent & e={...})  Line 576 + 0x7 bytes   C++
    psclient.exe!csEventTree::Notify()  Line 547   C++
    psclient.exe!csEventQueue::Process()  Line 298   C++
    psclient.exe!csDefaultRunLoop(iObjectRegistry * r=0x009e3b50)  Line 91 + 0x6 bytes   C++
    psclient.exe!main(int argc=1, char * * argv=0x009946d8)  Line 1878   C++
    psclient.exe!WinMain(HINSTANCE__ * hApp=0x00400000, HINSTANCE__ * prev=0x00000000, char * cmd=0x00133285, int show=1)  Line 205 + 0x1a bytes   C++
    psclient.exe!WinMainCRTStartup()  Line 390 + 0x1b bytes   C
    KERNEL32.DLL!7c5989d5()    
    [Frames below may be incorrect and/or missing, no symbols loaded for KERNEL32.DLL]   

Status: To be investigated


Crash Number:4E524157
Description: Error at startup with plugins
BT:>   4e524157()   
    psclient.exe!csSCF::CreateInstance(const char * iClassID=0x0013f338)  Line 974   C++
    psclient.exe!csPluginManager::LoadPlugin(const char * classID=0x00000026, bool init=true)  Line 173 + 0x18 bytes   C++
    psclient.exe!operator new(unsigned int size=8)  Line 12 + 0x6 bytes   C++
    psclient.exe!csEventTree::SubscriberIterator::SubscriberIterator(iEventHandlerRegistry * r=0x00c2a310, csEventTree * t=0x00c2a318, unsigned long bevent=12839984)  Line 266 + 0x7 bytes   C++
    psclient.exe!csEventTree::Dispatch(iEvent & e={...})  Line 576 + 0x7 bytes   C++
    psclient.exe!csInitializer::OpenApplication(iObjectRegistry * r=0x00c3eb70)  Line 465   C++
    psclient.exe!psCSSetup::InitCS(iReporterListener * customReporter=0x00000000)  Line 188 + 0xb bytes   C++
    psclient.exe!main(int argc=1, char * * argv=0x00394a40)  Line 1859 + 0xf bytes   C++
    psclient.exe!WinMain(HINSTANCE__ * hApp=0x00400000, HINSTANCE__ * prev=0x00000000, char * cmd=0x0016232d, int show=1)  Line 205 + 0x1a bytes   C++
    psclient.exe!WinMainCRTStartup()  Line 390 + 0x1b bytes   C
    kernel32.dll!7c816fd7()    
    [Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]   

Status: To be investigated



UPDATEDCrash Number:034A600B, ****600B,
Description: Rendering problem at startup
BT:
>   rendstep_std.dll!csGenericRenderStep::Perform(iRenderView * rview=0x07e8b8b0, iSector * sector=0x18b47c7c, iLight * light=0x00000000, iShaderVarStack * stacks=0x00b9f548)  Line 572 + 0x9 bytes   C++
    rendstep_std.dll!csGenericRenderStep::Perform(iRenderView * rview=0x00bd7348, iSector * sector=0x00000258, iShaderVarStack * stacks=0x00000000)  Line 309   C++
    psclient.exe!csView::Draw(iMeshWrapper * mesh=0x00000000)  Line 160 + 0x18 bytes   C++
    psclient.exe!psCamera::Draw()  Line 699   C++
    psclient.exe!psEngine::HandleEvent(iEvent & ev={...})  Line 786   C++
    psclient.exe!psEngine::EventHandler::HandleEvent(iEvent & ev={...})  Line 222   C++
    psclient.exe!csEventTree::Dispatch(iEvent & e={...})  Line 576 + 0x7 bytes   C++
    psclient.exe!csEventTree::Notify()  Line 547   C++
    psclient.exe!csEventQueue::iTypedFrameEventDispatcher::HandleEvent(iEvent & __formal={...})  Line 262 + 0x36 bytes   C++
    psclient.exe!csEventTree::Dispatch(iEvent & e={...})  Line 576 + 0x7 bytes   C++
    psclient.exe!csEventTree::Notify()  Line 547   C++
    psclient.exe!csEventQueue::Process()  Line 298   C++
    psclient.exe!csDefaultRunLoop(iObjectRegistry * r=0x00bf2cf8)  Line 91 + 0x6 bytes   C++
    psclient.exe!main(int argc=1, char * * argv=0x00b744d8)  Line 1878   C++
    psclient.exe!WinMain(HINSTANCE__ * hApp=0x00400000, HINSTANCE__ * prev=0x00000000, char * cmd=0x00152348, int show=1)  Line 205 + 0x1a bytes   C++
    psclient.exe!WinMainCRTStartup()  Line 390 + 0x1b bytes   C
    kernel32.dll!7c816fd7()    
    [Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]   
Status: To be investigated


Crash Number:00F27D1C, 01CF7D1C, *7D1C
Description: Crash while parsing xml file (of world) in Hydlaa/Tavern/Arena
BT:>   xmlread.dll!CS::StrDup(const char * s=0x1c4a0020)  Line 119 + 0x9 bytes   C++
    xmlread.dll!csXmlReadDocument::Parse(const char * buf=0x1c4a0020, bool collapse=false)  Line 481 + 0x10 bytes   C++
    xmlread.dll!csXmlReadDocWrapper::Parse(const char * buf=0x1c4a0020, bool collapse=false)  Line 105 + 0xe bytes   C++
    xmlread.dll!csXmlReadDocument::Parse(iDataBuffer * buf=0x0d82d3e8, bool collapse=false)  Line 471 + 0x1a bytes   C++
    psclient.exe!psRegion::Load(bool loadMeshes=true)  Line 405   C++
    psclient.exe!psWorld::ExecuteFlaggedRegions(bool transitional=false)  Line 175 + 0x8 bytes   C++
    psclient.exe!ZoneHandler::ExecuteFlaggedRegions(const csString & sector={...})  Line 362   C++
    psclient.exe!ZoneHandler::OnDrawingFinished()  Line 247 + 0xb bytes   C++
    psclient.exe!psEngine::HandleEvent(iEvent & ev={...})  Line 808   C++
    psclient.exe!psEngine::EventHandler::HandleEvent(iEvent & ev={...})  Line 222   C++
    psclient.exe!csEventTree::Dispatch(iEvent & e={...})  Line 576 + 0x7 bytes   C++
    psclient.exe!csEventTree::Notify()  Line 547   C++
    psclient.exe!csEventQueue::iTypedFrameEventDispatcher::HandleEvent(iEvent & __formal={...})  Line 262 + 0x36 bytes   C++
    psclient.exe!csEventTree::Dispatch(iEvent & e={...})  Line 576 + 0x7 bytes   C++
    psclient.exe!csEventTree::Notify()  Line 547   C++
    psclient.exe!csEventQueue::Process()  Line 298   C++
    psclient.exe!csDefaultRunLoop(iObjectRegistry * r=0x00b9ff78)  Line 91 + 0x6 bytes   C++
    psclient.exe!main(int argc=1, char * * argv=0x00a64568)  Line 1878   C++
    psclient.exe!WinMain(HINSTANCE__ * hApp=0x00400000, HINSTANCE__ * prev=0x00000000, char * cmd=0x00152348, int show=1)  Line 205 + 0x1a bytes   C++
    psclient.exe!WinMainCRTStartup()  Line 390 + 0x1b bytes   C
    kernel32.dll!7c816fd7()    
    [Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]   

UPDATE Status: The problem is due to the fact that some world files are not in binary format any longer.


4
The Hydlaa Plaza / Myself as a bride
« on: August 26, 2007, 11:40:48 am »
Just for satisfying my ego, I will add some pictures from my wedding, that took place yesterday!

Enjoy:





5
If you get a crash, you will usually get a pop up window asking you to save a diagnostic file (in windows). "Error xxxxxx, do you want to save a diagnostic file?": this is the usual text on the window. You should then press yes and remember the name of the file (it will be shown in the next pop up window). 
Before opening a bug report in the bugtracker or sending an email to us, check if the diagnostic file has been already analyzed (the number of the error should be the same as in the field "CRASH NUMBER" of the list, sometimes you should see among the numbers that has some "*" in the ciphers, because the wildcard means that in that position it could be any number ) in the list that will appear here below.
Please, DO NOT SEND the file errorlog.txt, but the file with extension .dmp! If I need some other file for analyzing the problem, I will ask you in the email exchange.

Verify also that you have updated the game (if that is possible) and that you have your latest drivers for your graphic card.

Send the diagnostic file, if it is not already in this list to . I will soon reply to you, please, answer me back if I ask you questions and don't disappear into void, otherwise I will ignore your report! In the email indicate (ALWAYS - otherwise I will ignore the mail):
  • Name of your character
  • What were you doing when you got the crash and the client asked you if you wanted to save a diagnostic file
  • In which area you were
  • Don't FORGET to attach the diagnostic file :-)


Please, DO  NOT reply to this thread!

6
If you get a crash, you will usually get a pop up window asking you to save a diagnostic file (in windows). "Error xxxxxx, do you want to save a diagnostic file?": this is the usual text on the window. You should then press yes and remember the name of the file (it will be shown in the next pop up window). 
Before opening a bug report in the bugtracker or sending an email to us, check if the diagnostic file has been already analyzed (the number of the error should be the same as in the field "CRASH NUMBER" of the list ) in the list that will appear here below.
Please, DO NOT SEND the file errorlog.txt, but the file with extension .dmp! If I need some other file for analyzing the problem, I will ask you in the email exchange.

Verify also that you have updated the game (if that is possible) and that you have your latest drivers for your graphic card.

Send the diagnostic file, if it is not already in this list to . I will soon reply to you, please, answer me back if I ask you questions and don't disappear into void, otherwise I will ignore your report! In the email indicate (ALWAYS - otherwise I will ignore the mail):
  • Name of your character
  • What were you doing when you got the crash and the client asked you if you wanted to save a diagnostic file
  • In which area you were
  • Don't FORGET to attach the diagnostic file :-)


Please, DO  NOT reply to this thread! The thread is opened because I am not a moderator of this board, so I can't locked and unlocked the thread.

7
Forum and Website Discussions / Emails on new posts?
« on: December 11, 2006, 03:52:29 am »
Hi,

I tried to look if there are recent posts about it, and I couldn't find any.

I have set in my options that I want to be notified through email if a new post has been made in a thread where I have been writing and similar.
However, I get emails just "randomly", which means, not for all the threads there are actually reply.

Am I the only one with this issue?


8
Here is back one of my fav thread :-)

If you get a crash, you will usually get a pop up window asking you to save a diagnostic file. "Error xxxxxx, do you want to save a diagnostic file?": this is the usual text on the window. You should then press yes and remember the name of the file (it will be shown in the next pop up window). 
Before opening a bug report in the bugtracker or sending an email to us, check if the diagnostic file has been already analyzed (the number of the error should be the same as in the field "CRASH NUMBER" of the list ) in the list that will appear here below.
Please, DO NOT SEND the file errorlog.txt, but the file with extension .dmp! If I need some other file for analyzing the problem, I will ask you in the email exchange.

Verify also that you have updated the game (if that is possible) and that you have your latest drivers for your graphic card.

Send the diagnostic file, if it is not already in this list to . I will soon reply to you, please, answer me back if I ask you questions and don't disappear into void! In the email indicates:
  • Name of your character
  • What were you doing when you got the crash and the client asked you if you wanted to save a diagnostic file
  • In which area you were
  • Don't FORGET to attach the diagnostic file :-)


Please, DO  NOT reply to this thread! The thread is opened because I am not a moderator of this board, so I can't locked and unlocked the thread.

9
other / Compiling guide
« on: April 30, 2006, 01:06:50 am »
In this subforum I consider MinGW since being under Windows it requires a mixed setting between Windows and gcc.

You can find the guide here:
http://cvs.sourceforge.net/viewcvs.py/planeshift/planeshift/docs/compiling-mingw32.txt?view=markup

If you have any suggestions, updates, adds-on, something is not clear, whatever, write it here.

10
gcc / Compiling guides
« on: April 30, 2006, 01:05:18 am »
gcc can be used under different systems.
I will include here just the Linux ones and not MinGW since it has some "Windows" background that makes things differents and a little bit hybrid. You find more information about minGW here : http://hydlaa.com/smf/index.php?board=52.0

Various build guides are here.  Select the OS that you use from the dropdown box:

http://planeshift.svn.sourceforge.net/viewvc/*checkout*/planeshift/trunk/docs/compiling.html?revision=639&pathrev=639

For comments, adds-on, problems with the guides post it here.


11
VisualC++ / Compiling guide
« on: April 30, 2006, 01:00:05 am »
Here you can find the build guide for building under MSVC:
http://cvs.sourceforge.net/viewcvs.py/planeshift/planeshift/docs/compiling-visualc.txt?view=markup

You can use MSVC 7 and superior. PS doesn't support any longer MSVC 6.

If you have any suggestions, comments, something wrong, to make it clear, whatever, just post it!

12
If you get a crash and you have the possibility to save a diagnostic file, before doing it and open a bug report in the bugtracker or send an email to us, check if the diagnostic file has been already analyzed (the number of the error should be the same!).

Verify also that you have updated the game and that you have your latest drivers for your graphic card.

Send the diagnostic file, if it is not already in this list to arianna.benigno@gmail.com. I will soon reply to you, please, answer me back if I ask you questions.

The situation so far:

0041A9A3 : problems while deleting regions.
BT:
   psclient.exe!psCelClient::OnRegionsDeleted(csArray,csArrayMemoryAllocator > & regions={...})  Line 706 + 0x43 C++
     psclient.exe!ZoneHandler::ExecuteFlaggedRegions(const csString & sector={...})  Line 354    C++
     psclient.exe!ZoneHandler::OnDrawingFinished()  Line 237 + 0xa   C++
     psclient.exe!psEngine::HandleEvent()  Line 730  C++
     psclient.exe!psEngine::EventHandler::HandleEvent(iEvent & ev={...})  Line 225   C++
     psclient.exe!csEventTree::Dispatch(iEvent & e={...})  Line 558 + 0x7    C++
     psclient.exe!csEventTree::Notify()  Line 529    C++
     psclient.exe!csEventQueue::iTypedFrameEventDispatcher::HandleEvent(iEvent & __formal={...})  Line 260 + 0x36    C++
     psclient.exe!csEventTree::Dispatch(iEvent & e={...})  Line 558 + 0x7    C++
     psclient.exe!csEventTree::Notify()  Line 529    C++
     psclient.exe!csEventQueue::Process()  Line 292  C++
     psclient.exe!csDefaultRunLoop(iObjectRegistry * r=0x00a2c6a8)  Line 90 + 0x6    C++
     psclient.exe!main(int argc=1, char * * argv=0x00a246b8)  Line 2000  C++
     psclient.exe!WinMain(HINSTANCE__ * hApp=0x00400000, HINSTANCE__ * prev=0x00000000, char * cmd=0x00152348, int show=1)  Line 194 + 0x1a  C++
     psclient.exe!WinMainCRTStartup()  Line 390 + 0x1b   C
Solution:
Not yet any.


22958BD5: A problem in CS genmesh.
BT:
 genmesh.dll!csGenmeshMeshObject::GetRenderMeshes(int & n=, iRenderView * rview=, iMovable * movable=, unsigned int frustum_mask=)  Line 1105 + 0x8    C++
Solution:
Not yet any.


0042F42A: A problem with SSE optimization or something like that. Problem known and most probably solved soon.
BT:
Not relevant.
Solution:
Fixed in CVS.


005391AD: AnchorSpline in effects that happens when casting sometimes flame burst. Probably the problem is in the .eff file of the effect.
BT:
>  psclient.exe!csBSpline::GetInterpolatedDimension(int dim=0)  Line 305   C++
     psclient.exe!psEffectAnchorSpline::Update(unsigned int elapsed=27)  Line 117 + 0xd  C++
     psclient.exe!psEffect::Update(unsigned int elapsed=27)  Line 533 + 0x13 C++
     psclient.exe!psEffectManager::Update(unsigned int elapsed=27)  Line 328 + 0xa   C++
     psclient.exe!psEngine::UpdatePerFrame()  Line 892   C++
     psclient.exe!psEngine::HandleEvent()  Line 736  C++
     psclient.exe!psEngine::EventHandler::HandleEvent(iEvent & ev={...})  Line 225   C++
     psclient.exe!csEventTree::Dispatch(iEvent & e={...})  Line 558 + 0x7    C++
     psclient.exe!csEventTree::Notify()  Line 529    C++
     psclient.exe!csEventQueue::iTypedFrameEventDispatcher::HandleEvent(iEvent & __formal={...})  Line 260 + 0x36    C++
     psclient.exe!csEventTree::Dispatch(iEvent & e={...})  Line 558 + 0x7    C++
     psclient.exe!csEventTree::Notify()  Line 529    C++
     psclient.exe!csEventQueue::Process()  Line 292  C++
     psclient.exe!csDefaultRunLoop(iObjectRegistry * r=0x00a2c6a8)  Line 90 + 0x6    C++
     psclient.exe!main(int argc=1, char * * argv=0x00a246b8)  Line 2000  C++
     psclient.exe!WinMain(HINSTANCE__ * hApp=0x00400000, HINSTANCE__ * prev=0x00000000, char * cmd=0x00152348, int show=1)  Line 194 + 0x1a  C++
     psclient.exe!WinMainCRTStartup()  Line 390 + 0x1b   C
Solution:
Fixed. Available in the next client update/release.




13
Forum and Website Discussions / Forum Styles
« on: June 18, 2005, 04:14:11 am »
Hi,

I have tried to search if this thread was already existing somewhere but without success, maybe I was not carefully...
Anyway, I have set as default forum style the old one, the one in light blue (I think it is much more readable than the \"brown and green\" one, forgive me, but I think it is not really usable for the choice of colors... ), I can see all the forum sections in this nice light blue color, except when I go in \"linux specific issues\" where automagically everything become brown and yellow.

If I decide that I want blue, the forum shouldn\'t take control over my decision and force me to buy sunglasses, no? ;)


14
Development Deliberation / item_stats table
« on: May 03, 2005, 03:27:56 am »
Hi!

I have been digging a bit out the code of gmspawnwindow, because I was encountering some trouble loading items that were having the same name.

I have discovered that for how is the code the name of the items in item_stats should be unique.

Probably that could be a way to sort this out in code, but I think the easiest solution is to make the key \"name\" in item_stats unique.

Ary

15
Development Deliberation / Warnings (MSVC 7.1)
« on: April 19, 2005, 03:34:35 am »
Hi,

I know that PS philosphy is generically the one to ignore the warnings, but I would have liked to be able to fix them, because I don\'t like to have warnings in my application, but I don\'t have the clue on how to fix them!

I ll show them here:
C:\\Development\\planeshift\\src\\common\\util\\fparser.cpp(1520): warning C4805: \'!=\' : unsafe mix of type \'const char\' and type \'bool\' in operation
C:\\Programmi\\Microsoft Visual Studio .NET 2003\\Vc7\\include\\ostream(574): warning C4530: C++ exception handler used, but unwind semantics are not enabled. Specify /EHsc

These are examples of what I get while compiling PS. and they make references to eedit that I don\'t need. I get similar warnings also for other parts (specifically psengine.cpp).

Since csStringHash or something has changed, I get a lot of warnings concerning the updater (also this I don\'t need, I am just telling so you know, than you can do what you want with this information)


More, there are a lot of files that would need to change the includes from imap/parser.h to imap/loader.h. I would like to send those files, just if I would be sure that it is not considered stupid, since it is such an easy modification :-)

Well, I could write all the warnings here (there is some unsigned/signed mismatch also), but probably it is beyond the goal of this post :-)

Ary

Pages: [1] 2 3 4