HuntingNut
HuntingNut
   Login or Register
HomeCommunity ForumsPhoto AlbumsRegister
     
 

User Info

Welcome Anonymous


Membership:
Latest: taptistabenn
New Today: 1
New Yesterday: 1
Overall: 12476

People Online:
Members: 0
Visitors: 51
BOT: 5
Total: 56
Who Is Where:
 Visitors:
01: Forums
02: Home
03: Forums
04: Forums
05: Home
06: News
07: Photo Albums
08: Forums
09: Your Account
10: Forums
11: Forums
12: Forums
13: Forums
14: Forums
15: Home
16: Home
17: Home
18: Forums
19: Photo Albums
20: Forums
21: Home
22: Forums
23: Forums
24: Forums
25: Forums
26: Home
27: Forums
28: Forums
29: Home
30: Forums
31: Forums
32: Home
33: Forums
34: Forums
35: Photo Albums
36: Forums
37: Forums
38: News
39: Forums
40: Forums
41: Forums
42: Forums
43: Forums
44: Home
45: Photo Albums
46: Forums
47: Forums
48: Forums
49: Forums
50: Forums
51: Forums
  BOT:
01: Your Account
02: Forums
03: Home
04: Forums
05: Your Account

Staff Online:

No staff members are online!
 

Coppermine Stats
Photo Albums
 Albums: 304
 Pictures: 2340
  · Views: 296518
  · Votes: 1302
  · Comments: 85
 

Support our Advertisers

One problem and two requests
Help / Support / How-to's / Discussion related to PointBlank Software and External Ballistics in general
Post new topic   Reply to topic   Printer Friendly Page    Forum Index » PointBlank Software

View previous topic :: View next topic  
Author Message
lince
Member
Member


Joined: Jul 19, 2006
Posts: 32
Location: Madrid, Spain

PostPosted: Wed Feb 08, 2012 3:18 am    Post subject: One problem and two requests Reply with quote

Hello everybody from Spain!,
I don’t know if this is a problem because I have introduced incorrect data or maybe it’s a software problem (my suspect is that it’s this last option but maybe you can confirm).
Note: I attach the file database.xml if you want to double check

1) I start PB software, I have two firearms, .300 WM and 7mmRemMag, each one has one load, etc…
2) When I start the bullet diameter in both loads are blank (even if in the database.xml file they are not blank)
3) I select to change from one load (norma plastic point) to the other one (Winchester supreme ballistic silvertip) and I receive an error (the complete text is at the end of this email in red font)
4) Also, if I want to select the bullet diameter in one of the loads all loads are the same bullet diameter!: example, I select “.284” in Winchester supreme ballistic silvertip, and I change to norma plastic point and the “0.284” is selected in this caliber, so if I change here to “.308” and I come back again to Winchester load, “0.308” is selected in this load.
5) If I exit from the PB software and enter again, no data from bullet diameter is recovered.

Also a couple of new feature requests:
1) is it possible to calculate the point black range table also in a opposite way?, I mean, if I give to the software the kill zone (eg. 12 cm) the software calculates the ballistics table and also gives to me the zero adjusting distance I have to set my sight.
2) Suppose that I have two different bullets. If I have the sight adjusted to one of them (for example let's say to have a zero at 200m) is it possible to calculate the ballistic table for the other bullet with the current adjustment for the first one?. In this way I can calculate the behaviour of my shots with those two diffrerent bullets.

Thanks in advance and best regards.

Error received according to step 3:

Consulte el final de este mensaje para obtener más detalles sobre cómo invocar a la depuración
Just-In-Time (JIT) en lugar de a este cuadro de diálogo.

************** Texto de la excepción **************
System.NullReferenceException: Referencia a objeto no establecida como instancia de un objeto.
en PointBlank.ControlLoad.comboBulletWeight_SelectedIndexChanged(Object sender, EventArgs e)
en System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
en System.Windows.Forms.ComboBox.set_SelectedIndex(Int32 value)
en PointBlank.ControlLoad.SetData(LoadTreeNode node)
en PointBlank.ControlDatabase.TreeView_AfterSelect(Object sender, TreeViewEventArgs e)
en System.Windows.Forms.TreeView.TvnSelected(NMTREEVIEW* nmtv)
en System.Windows.Forms.TreeView.WmNotify(Message& m)
en System.Windows.Forms.TreeView.WndProc(Message& m)
en System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
en System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Ensamblados cargados **************
mscorlib
Versión del ensamblado: 2.0.0.0
Versión Win32: 2.0.50727.5448 (Win7SP1GDR.050727-5400)
Código base: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
PointBlank
Versión del ensamblado: 1.0.4348.38758
Versión Win32: 1.0.4348.38758
Código base: file:///C:/Users/asanchez.CATEC/Documents/as/docs/caza/Balistica/PointBlack/PointBlank.exe
----------------------------------------
System.Windows.Forms
Versión del ensamblado: 2.0.0.0
Versión Win32: 2.0.50727.5446 (Win7SP1GDR.050727-5400)
Código base: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Versión del ensamblado: 2.0.0.0
Versión Win32: 2.0.50727.5447 (Win7SP1GDR.050727-5400)
Código base: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Versión del ensamblado: 2.0.0.0
Versión Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
Código base: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
mscorlib.resources
Versión del ensamblado: 2.0.0.0
Versión Win32: 2.0.50727.5448 (Win7SP1GDR.050727-5400)
Código base: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll
----------------------------------------
System.Xml
Versión del ensamblado: 2.0.0.0
Versión Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
Código base: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
Versión del ensamblado: 2.0.0.0
Versión Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
Código base: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Windows.Forms.resources
Versión del ensamblado: 2.0.0.0
Versión Win32: 2.0.50727.5420 (Win7SP1.050727-5400)
Código base: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms.resources/2.0.0.0_es_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------

************** Depuración JIT **************
Para habilitar la depuración Just In Time (JIT), el archivo de configuración de esta
aplicación o equipo (machine.config) debe tener el
valor jitDebugging establecido en la sección system.windows.forms.
La aplicación también se debe compilar con la depuración
habilitada

Por ejemplo:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

Cuando esté habilitada la depuración JIT, cualquier excepción no controlada
se enviará al depurador JIT registrado en el equipo
en lugar de controlarlo mediante el cuadro de diálogo.





database.zip
 Description:
This is the file where I can see the observed error
 Filename:  database.zip
 Filesize:  1.36 KB
 Downloaded:  99 Time(s)
Back to top
View user's profile
TRBLSHTR
Super Member
Super Member


Joined: Mar 23, 2007
Posts: 1037
Location: Lower 48's-left coast(near portlandia)

PostPosted: Wed Feb 08, 2012 12:24 pm    Post subject: Re: One problem and two requests Reply with quote

wtf No habla espanol! Very Happy

_________________
"Tolerance becomes a crime when applied to evil." Thomas Mann
Back to top
View user's profile
lince
Member
Member


Joined: Jul 19, 2006
Posts: 32
Location: Madrid, Spain

PostPosted: Wed Feb 08, 2012 2:18 pm    Post subject: Re: One problem and two requests Reply with quote

Wow, I was wondering if somebody wanted to start to learn spanish! Wink
Now seriously, I think although part of the windows error is in spanish, it can be easily understood, but please let me know if you need translation of some part, feel free to ask...
Back to top
View user's profile
DallanC
Site Admin
Site Admin


Joined: Jan 18, 2005
Posts: 3151
Location: Utah

PostPosted: Wed Feb 08, 2012 3:03 pm    Post subject: Re: One problem and two requests Reply with quote

lince wrote:
Hello everybody from Spain!,
I don’t know if this is a problem because I have introduced incorrect data or maybe it’s a software problem (my suspect is that it’s this last option but maybe you can confirm).
Note: I attach the file database.xml if you want to double check

1) I start PB software, I have two firearms, .300 WM and 7mmRemMag, each one has one load, etc…
2) When I start the bullet diameter in both loads are blank (even if in the database.xml file they are not blank)
3) I select to change from one load (norma plastic point) to the other one (Winchester supreme ballistic silvertip) and I receive an error (the complete text is at the end of this email in red font)
4) Also, if I want to select the bullet diameter in one of the loads all loads are the same bullet diameter!: example, I select “.284” in Winchester supreme ballistic silvertip, and I change to norma plastic point and the “0.284” is selected in this caliber, so if I change here to “.308” and I come back again to Winchester load, “0.308” is selected in this load.
5) If I exit from the PB software and enter again, no data from bullet diameter is recovered.

I will dig into this further at home, great repro steps though! Very useful.

Quote::
Also a couple of new feature requests:
1) is it possible to calculate the point black range table also in a opposite way?, I mean, if I give to the software the kill zone (eg. 12 cm) the software calculates the ballistics table and also gives to me the zero adjusting distance I have to set my sight.

In version 1.8a, the user was prompted to enter in a specific Kill zone and the rest was computed. 99% of the users used the same few settings so I just made the table automatically show those values.

What you want to see I guess is the zero range from the PointBlank table fed back into the ballistics calculator and data re-calculated?


Quote::
2) Suppose that I have two different bullets. If I have the sight adjusted to one of them (for example let's say to have a zero at 200m) is it possible to calculate the ballistic table for the other bullet with the current adjustment for the first one?. In this way I can calculate the behaviour of my shots with those two diffrerent bullets.

The ballistic calculator isnt setup currently in a way to calculate this... and it becomes complex quickly. The angle of the barrel would would have to be calculated and run back through the equasions. I can explore this further when I get time.


-DallanC
Back to top
View user's profile Photo Gallery
lince
Member
Member


Joined: Jul 19, 2006
Posts: 32
Location: Madrid, Spain

PostPosted: Thu Feb 09, 2012 1:36 am    Post subject: Re: One problem and two requests Reply with quote

DallanC wrote:
What you want to see I guess is the zero range from the PointBlank table fed back into the ballistics calculator and data re-calculated?
-DallanC
I wrote in that way, so maybe it can be understood that this is my final request. That could be a very good way to quickly see the PBR ballistic table, and if it's easy to add this feature I thing it could be really nice, but from my opinion it's not a must to get usability: the thing I consider important is to calculate the zero adjust distance, so you can manually insert those data in the ballistics calculator.
Hope that helps.
Back to top
View user's profile
DallanC
Site Admin
Site Admin


Joined: Jan 18, 2005
Posts: 3151
Location: Utah

PostPosted: Sun Feb 12, 2012 9:13 pm    Post subject: Re: One problem and two requests Reply with quote

Ok so there was a bug with the spain version of the data (ie: its yet again another instance of using coma's verse periods in fractional numbers... ie: ".284" vs ",284" This is what was causing the diameter to be empty in your above step #2.

Next, in your database.xml the value for your 7mm is "284,000" when it should be ",284". Did you manually attempt setting the caliber value to a non-decimal point value or is this a different bug? I tried seeing if I could reproduce this but I am not able to... which makes me think it might be manually entered.

I added extra checking which now catches this case and is able to figure out the proper diameter from the caliber name.

This has fixed the overall crash you experienced.


-DallanC
Back to top
View user's profile Photo Gallery
lince
Member
Member


Joined: Jul 19, 2006
Posts: 32
Location: Madrid, Spain

PostPosted: Mon Feb 13, 2012 1:47 am    Post subject: Re: One problem and two requests Reply with quote

Hi again.

I didn't modify manually modify the file, in this way I suppose there could be "external" errors that you couldn't manage or try to reproduce. I'll try to update the sw with patcher, introduce all the data from scratch and see if everything appears ok. I'll let you know...

BTW, please, let us know when you consider my requests are implemented (if you consider that they are useful) to try them.

Thanks again for your good work
Back to top
View user's profile
lince
Member
Member


Joined: Jul 19, 2006
Posts: 32
Location: Madrid, Spain

PostPosted: Tue Feb 14, 2012 2:31 am    Post subject: Re: One problem and two requests Reply with quote

Ok, I have checked and now everything appears to be correct, also I am not able to reproduce the problem, so as usual GREAT THANKS! Salute
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic   Printer Friendly Page    Forum Index » PointBlank Software
Page 1 of 1
All times are GMT - 7 Hours



Jump to:  


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Advertisements
 


Valid CSS! Valid HTML 4.01!
Click to check if this page is realy HTML 4.01 compliant for speed :)

All logos and trademarks in this site are property of HuntingNut.com.
The comments are property of their posters, all the rest © 2011 by HuntingNut.com
Interactive software released under GNU GPL, Code Credits, Privacy Policy

.: Upgraded to DragonFly 9.2 by Dizfunkshunal :.