Virtavia A4 invalid license message

[FSX68]

Anyone else getting the invalid license message for the VIrtavia A4 Skyhawk?

I purchased it from PCAviator yesterday and got the invalid message last night and now today.

There wasn't any license to enter in the first place so I don't know whats up with that? :isadizzy:

 

[jojohnson9]

Yes, this message comes up with every load. Just acknowledge it and go flying.

 

[cajj1]

It's mentioned in the manual, something to do with click sounds for switches in the VC I think.

 

[FSX68]

Thanks for the responses - I notified their support and got a trouble ticket number. Never got this with their other stuff. Good to know that I'm not the only one with this issue
just wish they (Virtavia) would sort this out,

 

[FSX68]

Now I notice that is mentioned in their manual.

 

[Cleartheprop]

I get this message too.
Just acknowledge and go flying.

What puzzles me more is the artificial horizon thats shows incorrect attitudes when flying upside down. Keeps me away from this add-on.

 

[FSX68]

I get this message too.
Just acknowledge and go flying.

What puzzles me more is the artificial horizon thats shows incorrect attitudes when flying upside down. Keeps me away from this add-on.

Heck of a way to run a railroad. Oh well it is all moot now.


I did like the discount offer to buy it and there are some good aspects to it.
Brand X sells it at for a price that is just way too much for my woodpile.

 

[skyhawka4m]

this message comes up because you are supposed to start your flight in the VC. If you start outside the cockpit it will pop up and yes it will stop popping up if you cycle through the views including the VC. My default starting position is always in the VC.

 

[n4gix]

Look in the [VCockpit01] section of the panel.cfg file and locate the sound gauge entry. Copy/paste it to the [Window00] section, renumber as necessary, and set the parameters to 0,0,1,1

That should solve the problem entirely.

 

[FSX68]

Look in the [VCockpit01] section of the panel.cfg file and locate the sound gauge entry. Copy/paste it to the [Window00] section, renumber as necessary, and set the parameters to 0,0,1,1

That should solve the problem entirely.

I tried that and decided to take it for a spin and check it out, I still get the invalid license pop-up here, I hope I followed you directions correctly. Here is what I did to the panel.cfg :

[Window00]
file=Blank.bmp
size_mm=1024,768
window_size_ratio=1.000
position=7
visible=1
ident=MAIN_PANEL
nomenu=0
window_size= 1.000, 1.000
window_pos= 0.000, 0.000
gauge00=Virtavia_Sound!DeadPixl_XMLSound, 0,0,1,1 <<<< this is same file as below ? :isadizzy: <<<< No paramenter to reset as they are same as below.
gauge01=Virtavia_Sound!DeadPixl_XMLSound, 0,0,1,1 <<<<<< Pasted here and renumbered >>>>>>>>>


[Vcockpit01]

gauge36=Virtavia_Sound!DeadPixl_XMLSound, 0,0,1,1 <<<< This is one I copied and pasted to above location. Paramenter is already 0,0,1,1



So what did I do wrong?

 

[skyhawka4m]

this message comes up because you are supposed to start your flight in the VC. If you start outside the cockpit it will pop up and yes it will stop popping up if you cycle through the views including the VC. My default starting position is always in the VC.

again....

 

[FSX68]

again....

If you are replying to me, I know and read what you said.

I was telling n4gix who had "the cure" that it did not work for me.

I as so much notified him via PM of same.

Again......

 

[skyhawka4m]

ok.....not sure why a "fix" is needed. I do believe when the A-4 first came out someone who was here that spoke for Virtavia even mentioned that your flight should start in the VC. Another company who was like this was Eaglesoft.

 

[FSX68]

ok.....not sure why a "fix" is needed. I do believe when the A-4 first came out someone who was here that spoke for Virtavia even mentioned that your flight should start in the VC. Another company who was like this was Eaglesoft.

Same company had same issues with their BN2 Islander and they did pony up a patch that fixed this "invalid license issue". It is a bit of a hassle for me. The other
Devs managed to create a product that didn't perform like this A4 addon. For now, I can click their "oops I made a mistake" button and keep flyin' I guess.
I sent them an email about this and will be interested in their reply.

 

[n4gix]

gauge01=Virtavia_Sound!DeadPixl_XMLSound, 0,0,1,1 <<<<<< Pasted here and renumbered >>>>>>>>>

So what did I do wrong?

You did absolutely nothing wrong, honestly. I recognized the Message Box text as one being generated by the sound module I coded and licensed to a specific company. Having gone now and checked the code build for DeadPixl, I see that the version of the code used requires the interior model to be loaded within thirty seconds so that the license check may be performed.

This is why they insist that the aircraft be loaded in the VC view. As some others have noted, if you load in 2d view, quickly switch to the VC view and then back to the 2d view, the Message Box and error message will not appear. Keyboard method is a quick F10 (VC view) followed by F9 (2d view).

One method to overcome this restriction would be to create a simple "gauge" who's only task is to switch the sim to VC view automatically, then switch back to the 2d view. This would allow the interior model to be properly initialized and loaded so that the license check could be accomplished transparently and without error.

Hopefully this information will clear up any of the mystery about the Message Box error message. :ernae:

 

[FSX68]

You did absolutely nothing wrong, honestly. I recognized the Message Box text as one being generated by the sound module I coded and licensed to a specific company. Having gone now and checked the code build for DeadPixl, I see that the version of the code used requires the interior model to be loaded within thirty seconds so that the license check may be performed.

This is why they insist that the aircraft be loaded in the VC view. As some others have noted, if you load in 2d view, quickly switch to the VC view and then back to the 2d view, the Message Box and error message will not appear.

One method to overcome this restriction would be to create a simple "gauge" who's only task is to switch the sim to VC view automatically, then switch back to the 2d view. This would allow the interior model to be properly initialized and loaded so that the license check could be accomplished transparently and without error.

Hopefully this information will clear up any of the mystery about the Message Box error message. :ernae:

Thanks Bill for clearing this up. It looks like I did follow your directions. As far as making that gauge you mentioned I am all thumbs on that.
I remember when this outfit had same issues with their BN2 Islander and they came out with a patch that stopped the invalid license popup.
Wish/Hope they can follow suit with this one but like I mentioned before I can click on their "oops I made a mistake" button and keep on flying.

 

[n4gix]

Wish/Hope they can follow suit with this one but like I mentioned before I can click on their "oops I made a mistake" button and keep on flying.

Perhaps this simply got lost in the wall of text, but there really are two very simple solutions:

1. Load the a/c in VC view, then switch to 2d view if you prefer that panel.
2. After loading, press F10 (VC view) followed by F9 (2d view). You have up to 30 seconds.

The only consequence to a "License failure" is that you will lose the 'extra sound effects' that this module provides, otherwise the a/c works as designed.

 

[FSX68]

You did absolutely nothing wrong, honestly. I recognized the Message Box text as one being generated by the sound module I coded and licensed to a specific company. Having gone now and checked the code build for DeadPixl, I see that the version of the code used requires the interior model to be loaded within thirty seconds so that the license check may be performed.

This is why they insist that the aircraft be loaded in the VC view. As some others have noted, if you load in 2d view, quickly switch to the VC view and then back to the 2d view, the Message Box and error message will not appear. Keyboard method is a quick F10 (VC view) followed by F9 (2d view).

One method to overcome this restriction would be to create a simple "gauge" who's only task is to switch the sim to VC view automatically, then switch back to the 2d view. This would allow the interior model to be properly initialized and loaded so that the license check could be accomplished transparently and without error.

Hopefully this information will clear up any of the mystery about the Message Box error message. :ernae:

If I \\ the gauge then, I don't get the pop-up message. If I take out the \\ then it comes back

I didn't notice any appreciable differences in the cockpit:

View attachment 94100

[Vcockpit01]
file=$vpanel01.bmp
Background_color=0,0,0
size_mm=512,512
visible=0
pixel_size=512,512
texture=$vpanel01

gauge00=Virtavia_Skyhawk!HDG_window, 11,9,62,18
gauge01=Virtavia_Skyhawk!WarnLts_Gear-L, 98,9,33,33
gauge02=Virtavia_Skyhawk!WarnLts_Gear-C, 136,9,33,33
gauge03=Virtavia_Skyhawk!WarnLts_Gear-R, 173,9,33,33
gauge04=Virtavia_Skyhawk!WarnLts_FuelCtrl, 211,9,33,33
gauge05=Virtavia_Skyhawk!WarnLts_SplrArm, 251,9,33,33
gauge06=Virtavia_Skyhawk!SplrArm, 1,1,1,1
gauge07=Virtavia_Skyhawk!GenSwOn, 1,1,1,1
gauge08=Virtavia_Skyhawk!Radios_ADF, 296,44,103,20
gauge09=Virtavia_Skyhawk!Radios_COM_Act, 406,2,103,20
gauge10=Virtavia_Skyhawk!Radios_COM_Stby, 406,23,103,20
gauge11=Virtavia_Skyhawk!Radios_NAV_Act, 296,2,103,20
gauge12=Virtavia_Skyhawk!Radios_NAV_Stby, 296,23,103,20
gauge13=Virtavia_Skyhawk!NavComp_PP_Lat, 292,66,72,15
gauge14=Virtavia_Skyhawk!NavComp_PP_Lon, 367,66,72,15
gauge15=Virtavia_Skyhawk!NavComp_D_Lat, 292,84,72,15
gauge16=Virtavia_Skyhawk!NavComp_D_Lon, 367,84,72,15
gauge17=Virtavia_Skyhawk!NavComp_MagVar, 442,46,63,24
gauge18=Virtavia_Skyhawk!NavComp_Spd, 451,74,41,23
gauge19=Virtavia_Skyhawk!NavComp_Dir, 441,103,64,22
gauge20=Virtavia_Skyhawk!WarnLts_Drift, 250,45,33,33
gauge21=Virtavia_Skyhawk!Drift_Spd, 373,98,63,27
gauge22=Virtavia_Skyhawk!WarnLts_LowOXY, 251,81,33,33
gauge23=Virtavia_Skyhawk!WarnLts_RadAlt, 251,117,33,33
gauge24=Virtavia_Skyhawk!AOA Indexer, 79,46,50,108
gauge25=Virtavia_Skyhawk!WarnLts_APC off, 133,46,27,85
gauge26=Virtavia_Skyhawk!WarnLts_Wheels, 164,52,83,28
gauge27=Virtavia_Skyhawk!WarnLts_Obst, 164,82,83,28
gauge28=Virtavia_Skyhawk!WarnLts_Fire, 164,113,83,28
gauge29=Virtavia_Skyhawk!Gunsight, 279,224,220,240
gauge30=simicons1024!ATC Icon, 375,130,19,19
gauge31=simicons1024!Radio Icon, 397,130,19,19
gauge32=simicons1024!GPS Icon, 419,130,19,19
gauge33=simicons1024!Map Icon, 440,130,19,19
gauge34=simicons1024!Kneeboard Icon, 463,130,19,19
gauge35=Virtavia_Skyhawk!Stick Icon, 484,130,19,19
//gauge36=Virtavia_Sound!DeadPixl_XMLSound, 0,0,1,1 <<<< \\ out the gauge and the picture above reflect that.
gauge37=Virtavia_Skyhawk!Smoke, 0,0,1,1
gauge38=Virtavia_Skyhawk!WarnLts_Fuel, 287,103,33,33
gauge39=Virtavia_Skyhawk!WarnLts_SpdBrk, 366,155,68,19
gauge40=Virtavia_Skyhawk!WarnLts_Spoilers, 439,155,68,19
gauge41=Virtavia_Skyhawk!BuNoSwitcher, 439,178,68,16


EDIT: I have flown this bird with the gauge 36 snubbed out and I don' get anymore pop-ups. So far so good.