GRLevelX Users Forum

We are NOT affiliated with Gibson Ridge Software (grlevelx.com). If you are seeking access to those forums, you will need to contact the administrator of that site. We cannot help you in any way whatsoever with access or your licensing. Registered and properly activated users can access update information through this site and our Facebook group.

GR2 update from 2.9...
 
Notifications
Clear all

GR2 update from 2.9 to 3.3

2 Posts
2 Users
0 Reactions
18 Views
(@jfanjoy)
Posts: 1
New Member
Topic starter
 

Is there currently a site or document that has the differences and/or what has been upgraded between GR2 2.9 and GR2 3.3?


 
Posted : November 16, 2025 6:43 pm
(@joey49)
Posts: 15
Eminent Member
 

I copied this from the Owner's forum I hope this helps you in anyway.

 

Update: GR2Analyst 3.3.0

Postby admin » Wed Jul 24, 2024 11:04 am

I've uploaded GR2Analyst 3.3.0. It contains the following change:

D3D11 renderer improvements (3.3.0.4)
I brought over improvements in the GRE/GRM D3D11 renderer. These improvements significantly reduce the amount of data that needs to be sent down to the graphics hardware when drawing warnings and background imagery.

UDPs now have PHIfromHGT() (3.3.0.3)
I've added support for PHI to UDPs with the PHIfromHGT() function.

Now only supports GRS sounding format environmental data (3.3.0.3)
GR2 now only supports the GRS/JSON format sounding data. This only affects users who need to import sounding data manually. The program automatically downloads sounding data for live and archive radar data.

Added support for "TROPICAL CYCLONE" LSR type (3.3.0.2)
This was added by NOAA last year and will probably become more useful in the coming weeks!

Fixed GPS code to handle non-$GP strings (3.3.0.2)
This ancient code assumed that NMEA strings always begin with $GP, which would cause it to fail on $GN strings.

Fixed bug with Cross-section when viewing BV/SRV/CC (3.3.0.1)
This bug was introduced a while ago, where an out-of-range value (basically, past the end of a radial) was not tested for and allowed through to the renderer.

Built using new development environment
I've moved my development environment to Visual Studio 2022 (was 2008). Obviously, a major change. I'm seeing performance improvements of 2-4X in software-intensive parts of the program, like UDPs, algorithms, etc.


 
Posted : November 17, 2025 3:59 am
Share: