I recently participated in teh NX12 Beta testing. For further testing (event has ended) I wanted to use the NX110custom files.
I replaced all instances of "NX110" in all files and also added below line to the version declarations.
if %NX_NUMBER%==NX120 set NX_VERSION=V30.0
However, when I trie to start NX12 using the changed Custom files I get below error.
-version= - Version number should start with upper case V. eg, -version=V18.0
As you see in above code piece it is clearly written with an upper case V.
What could be the cause of the error?
Same for me. Works with just that change.
As soon as I change the NX_Number to 120 (and change the Library folder name) it starts complaining about the Upper case problem.
Check where NX_NUMBER comes from and change that source to result in NX120 too.
Changing this will make things work with the correct version string.
Production: NX10.0.3, VERICUT 8.1, FBM, MRL 3.1.7 | TcUA 10.1 MP7 Patch 0 (10.1.7.0) | TcVis 10.1
Development: VB.NET, Tcl/Tk Testing: NX12.0 Preparing: NX12.0
Employees of the customers, together we are strong
How to Get the Most from Your Signature in the Community
NX Customization - Best Practice Guide
It could be that for beta, they haven't changed the registry setting "version" yet?
Look in (regedit) for the keys under
Is there a separate key for "12.0"?
Production: NX10.0.3.5 MP16/TC11.2
I'd rather be e-steamed than e-diseaseled
Seems to be a network issue. If I start the bat file from a mapped network drive I have the issue. If I copy the folder to a local drive then it works...
Running NX11 with the same files is no issue from mapped network drive.