Install the app
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
PEVSoft Mesh Viewer and Windows 8.1
- Thread starter epa
- Start date
Trainz Mesh Viewer Changes
This is taking a lot of time because I am trying to implement three rendering methods so that various hardware and OpenGL implementations should work. I think I have two options working for all Trainz materials but the third method is more difficult (but the most needed).
The presence of the OpenGL instructions is checked for each method but I have one "glARB" instruction without which nothing will work so I am trying to get another option or preferably multiple options for it.
BUMP
Updated graphics card drivers, as well as installed AMD Catalyst control center. Still getting problems using 2.23.
This is taking a lot of time because I am trying to implement three rendering methods so that various hardware and OpenGL implementations should work. I think I have two options working for all Trainz materials but the third method is more difficult (but the most needed).
The presence of the OpenGL instructions is checked for each method but I have one "glARB" instruction without which nothing will work so I am trying to get another option or preferably multiple options for it.
Sorry to Bump this thread, but I am wondering if this was ever fixed? I just updated to Windows 7 and am getting the same error message as the original starter of this thread. It would be bad if I couldn't get Peter's Mesh Viewer to work on my new OS.
Thank you
Dave Snow
Thank you
Dave Snow
For the last year or so I have been compiling and using all of my tools using Windows 7 and NVidia graphics card. Everything works perfectly here.
The work I mentioned in the posts above works perfectly for me here, but when it was tested on a PC with ATI graphics the shader routines did not provide the correct colours, and the ARB extensions for normal mapped graphics did not work at all. The lowest level rendering routines (as included in ALL previous versions of Mesh Viewer) DID WORK, so no errors were generated by the ATI card.
Unfortunately I cannot reproduce the errors you are getting and I can't fix things I can't see.
I have done my best, in the new version, to test for the presence of all the graphics routines needed by the various render methods. However, I do not test for the lowest level routines; these are assumed to be present if the OpenGL extension list is detected. If the list has any gaps in it I don't see them.
I can add a test for every OpenGL graphics routine used in the program but this will take some time to set up. I have to scan the entire code (about a dozen files) for every OpenGL command... boring!!
And all this testing will only tell you and me what routines are missing. I don't know whether it will be possible to find alternative routines.
The work I mentioned in the posts above works perfectly for me here, but when it was tested on a PC with ATI graphics the shader routines did not provide the correct colours, and the ARB extensions for normal mapped graphics did not work at all. The lowest level rendering routines (as included in ALL previous versions of Mesh Viewer) DID WORK, so no errors were generated by the ATI card.
Unfortunately I cannot reproduce the errors you are getting and I can't fix things I can't see.
I have done my best, in the new version, to test for the presence of all the graphics routines needed by the various render methods. However, I do not test for the lowest level routines; these are assumed to be present if the OpenGL extension list is detected. If the list has any gaps in it I don't see them.
I can add a test for every OpenGL graphics routine used in the program but this will take some time to set up. I have to scan the entire code (about a dozen files) for every OpenGL command... boring!!
And all this testing will only tell you and me what routines are missing. I don't know whether it will be possible to find alternative routines.
Last edited:
For the last year or so I have been compiling and using all of my tools using Windows 7 and NVidia graphics card. Everything works perfectly here.
The work I mentioned in the posts above works perfectly for me here, but when it was tested on a PC with ATI graphics the shader routines did not provide the correct colours, and the ARB extensions for normal mapped graphics did not work at all. The lowest level rendering routines (as included in ALL previous versions of Mesh Viewer) DID WORK, so no errors were generated by the ATI card.
Unfortunately I cannot reproduce the errors you are getting and I can't fix things I can't see.
I have done my best, in the new version, to test for the presence of all the graphics routines needed by the various render methods. However, I do not test for the lowest level routines; these are assumed to be present if the OpenGL extension list is detected. It the list has any gaps in it I don't see them.
I can add a test for every OpenGL graphics routine used in the program but this will take some time to set up. I have to scan the entire code (about a dozen files) for every OpenGL command... boring!!
And all this testing will only tell you and me what routines are missing. I don't know whether it will be possible to find alternative routines.
Hey Peter, thanks for the reply. Well, I don't know what to say, but I restarted Windows and now everything is working perfectly!! Who can really understand Computers!! Ha! Sometimes I think they have a mind of their own.
Enjoying using the Mesh Viewer again! Thank you ever so much for your programs.
Cheers,
Dave
The program worked in Windows 7 on the same PC, but I have an ATI Mobility Radeon 3100 (Don't hate on my graphics please)
EDIT: Here's what the Mesh Viewer and error windows look like.
image deleted...
ATI drivers have probably changed no matter what version of your video card you are using. The unfortunate part is ATI (AMD) is notorious for poor Open/GL support and always has been.
Zeldaboy14
Owner of ZPW.
I know this is a bit off topic, but what is the difference from a PM mesh to a IM mesh?
shaneturner12
Tutorial Creator
I know this is a bit off topic, but what is the difference from a PM mesh to a IM mesh?
Quite simple really. PM is progressive mesh, which is the older type of mesh mainly created in GMax and older versions of 3DSMax,and is usually worse in performance terms. IM meshes are indexed mesh which usually are better and can be used as part of a LOD (Level of Detail) system.
Shane
Zeldaboy14
Owner of ZPW.
Why do Indexed mesh's work in older versions of trainz (ex: Trainz, UTC, Trainz 2004, Trainz 2006) but Progressive mesh support has been discontinued (ex: Trainz Classic 1 and 2, Trainz 2009, Trainz 2010, Trainz 2012, and T:ANE) and you need to convert them to IM?
shaneturner12
Tutorial Creator
It's because Progressive Meshes are obsolete, and have been replaced by Indexed Meshes. I did briefly explain in my last post, but others here may be able to give you a more detailed explanation.
Shane
Shane
Zeldaboy14
Owner of ZPW.
I know. I was curious. Thanks for a brief explanation shane.
shaneturner12
Tutorial Creator
No problem - hopefully someone will be able to expand on it though.
Shane
Shane
Indexed and progressive meshes for the same object have exactly the same material and geometric data. Progressive meshes have extra data to control how the poly count is "progressively" reduced by combining neighbouring triangular facets.
So if you are NOT doing progressive poly reduction they are effectively identical.
So if you are NOT doing progressive poly reduction they are effectively identical.
Zeldaboy14
Owner of ZPW.
So, why were they obsoleted by IM mesh's then PEV?
Similar threads
- Replies
- 10
- Views
- 1K
- Replies
- 13
- Views
- 2K
- Replies
- 8
- Views
- 2K