OK, I'm getting it now, the VC collimation has the top of it cut off leading me to believe it was the default and not csWeapons HUD thus I was stuck with the 2D display.

I carried out the calibrations and still have the collimation 'decapitated' eg.
ctrl+shift+9 or 0 and also the xml file changes to give me test pattern.
<Collimate>1</Collimate>
<!-- VC HUD collimation. 1-yes, 0-no (1). -->
<TestFrame>0</TestFrame>
<!-- HUD test pattern. 1-yes, 0-no (0). -->

Looks like I've have to adjust the XYZ co-ordinates.

Thank you for your tollerance.

earnorbust wrote on Feb 8^th, 2011 at 10:12pm:


Most likely the weapon is not properly installed on the t-p aircraft.

Thank you Ian....I appreciate your response on what to do in that matter.

I've been trying to follow the SDK with the gauge installation as well, and it's NOT going well.  I wish Captain Sim would please give more guidance than the SDK...

I have so far manually entered the gauge name on the Aircraft that I want it to appear in for it's hud, but now when I turn on the HUD, nothing displays.  It's really getting frustrating very fast.

Any ideas what to do?  I am going NUTS here....at least I found the SDK online, they don't even state you have to download it....

John

FSX and Weapon loader must be OFF while you make any changes in the CSWeapon.xml.

Captain Sim wrote on Feb 9^th, 2011 at 4:24pm:


That's a very helpful comment Alex. What the hell is a t-p aircraft and who needs a weapon installed there?  

OK whatever, as you admit, using the Loader program doesn't even seem to install your utility on your own F...... t-p aircraft (whatever that is) correctly - let alone any of my airplanes.

But as a user of your product I can only install the utility or uninstall the utility in my planes - nothing else. That is precisely what your product should do - am I right or am I right?  

I still can't calibrate any plane of my choice since every red circle is above the green circle (amazingly your FA18 Defender model which installs automatically shows the circles overlap). Well - that means your product doesn't work properly on my system for my needs. Am I right or am I right?

So why aren't you guys asking the right questions to get this solved? For me, that is the only thing worth posting! Reading your manuals doesn't solve my problem. Wake up people - I am not the only one posting this problem! Something is bugged in your CSWeapon.xml scripting, causing all this trouble. Even as a program layman I know something is going very wrong when changing a term like unlimited>0< to unlimited>1< in a script causes all ammunition to vanish instead of becoming unlimited, even after resetting it back to unlimited>0< again! And changing the unlimited term once in the file leads to a permanent vanishing of the red calibration circle. Isn't that curious? Why does your FA18 defender modell show a red circle overlapping the green circle on my system - but not in other of my plane installments. The answer must be in the CSWeapons.xml file. FIND OUT WHY...and maybe you will get the problem solved!

Besides that, if I have to take a course studying SDK -techniques to figure our how to use your product...you should have told me before buying it!

I wanted a working product and not another hobby.

This is getting very frustrating.    ...grrrr  

P.S. By the way, moving to many threads around often causes confusion and is a bad forum policy. You force posters to search there posts anew (which is time consuming) and give people the impression that you are hiding unwanted critisism or product information.

Well, I just wanted to help.

earnorbust wrote on Feb 9^th, 2011 at 10:27pm:

t-p = third-party

Quote:

For obvious reasons the loader works with 2D only. And it works perfectly. For HUD installation to VC please see SDK, the loader has nothig to do with VC.


Quote:

SDK is not about using a product. It's about its development. We've just provided a tool. It's a free bonus for advanced users and developers.

Quote:

We've thought the term SDK (software development kit) is self-explanatory. To make it 100% clear we've just added in capital red this:
CAPTAIN SIM DOES NOT SUPPORT ANY MODIFICATIONS OF THE ORIGINAL PRODUCT INCLUDING ITS INSTALLATION TO THIRD-PARTY AIRCRAFT. MAKE AND USE THE MODIFICATIONS ON YOUR OWN RISK.


Quote:

It is working. You just experience difficulties modifying it, and there can be many reasons beyond our control.

Ragtopjohnny wrote on Feb 9^th, 2011 at 10:24pm:


Hi John

try rearranging [Window01] and [Window02] to look like this:

[Window01]
size_mm=900, 250
windowsize_ratio=0.600
position=4
BACKGROUND_COLOR=0,0,0
visible=0
ident=Engine_state

gauge00=Viper!Statem, 0, 0, 900, 250
gauge01=Viper!State1, 0, 0, 1, 1
gauge02=Viper!State2, 0, 0, 1, 1

[Window02]
Background_color=0,0,0
no_luminous=1
size_mm=1024, 170
position=7
visible=0
window_size=1.000, 0.170
ident=10901
zorder=2

gauge00=CSWeapon_panel!CSWeapon_panel, 0, 0, 1024, 170

I don't know if that is causing your problem, but it looks like [Window02] is placed right in the middle of [Window01]. And also that the CSWeapon_panel gauge is gauge11=... instead of gauge00=...

Do you need to have the CSWeapon_panel.cab in this: C\FSX\Simobjects\Airplanes\Aersoft F-16A9\panel folder? It is already in the FSX\gauges folder. FSX looks in the Panel folder first, then the gauges folder unless it is told to look somewhere else.

Whether this is what is causing your problem, I don't know, but fixing that might help you somewhere.

Mark

Thank you very much Mark - I will try it and let you know.. I didn't even notice that the two looked like they were in the middle of the same window. 

Captain Sim, I understand, but just confused at the time,  thanks - and here is hoping Mark's code will work - I'll definitely give it a shot and write back.

Thank you all!

John