We have now released our 3rd party addon packs for the Mindstar GNS' and the Flight 1 GTN's.

The reason we are charging for these is that it took a serious amount of time (and effort) to get these to work properly, not including actually making the models and texturing them.  

There are NO REFUNDS.  We will support our end of the product(s) but no support will be given for the 3rd party product(s).

http://milviz.com/fs/item.php?id=GA_Adds
 

There are NO REFUNDS and we do not support them in any way.  Install at your own risk.

 

 

Buyer beware - I am getting constant sound errors as well as no frames around the GTN units on the 310R using the 750/650 option.  Curious to see if it worked for anyone else.

I'm sorry but have to ask, how can you charge for something and then not support it in any way? I understand there will be problems unrelated to your aircraft but what if that isn't the case and support by Milviz is required?

And as simple as that I am turned off from Milviz. Really thought about getting the Metro, but I can't see the sense in any of that post other than to hear people want for something, do a little work to get their money then offer no support for a "product" that they make.

 

You are either all in with you business or not.

Glad I held fire after receiving an email from them this morning.

If the issue is caused by us, then we will fix it.  We will support those who have issues with OUR end. Just not support the mindstar or the F1 installations. 

Don't we ALWAYS provide support even if (I'm) it's sometimes difficult?

 

The sound error is one we are aware of.  It's actually not us...

 

Bill says the fix is thus:

 

The "sound error" can only occur if for some reason the path to the SND files isn't present, or is mis-configured.  Check in the panel.Mindstar530 folder and load the panel.cfg file in Notepad.exe...

Down towards the bottom of this file, you should see an entry for the Milviz_Sound gauge that should be precisely this:

gauge00=Milviz_Sound!FBGS_XMLSound,  0,0,1,1,SimObjects\\Airplanes\\Cessna 310R MilViz\\panel\\C310R_Sounds#22

Please confirm that this entry is present.

My guess is they will step up, but, the warning is pretty stern hence my posting.

 

Tinkering as I do, discovered the issue with the sound errors already.  An incorrect folder name in the panel.cfg file.

 

Beginning to wonder if *may be* the panel listing is for P3D.  Even re-installed to be sure.  "FSX" is missing from the folder name in question, and, the gauge naming seems different than what I have been using for the GTN series in FSX.

 

Joe

And as simple as that I am turned off from Milviz. Really thought about getting the Metro, but I can't see the sense in any of that post other than to hear people want for something, do a little work to get their money then offer no support for a "product" that they make.

 

You are either all in with you business or not.

 We don't have a Metro.  That's Razbam.  Not us.

Ya, you got me there on that typo. I let it fly anyways as I was looking at not the Metro from you but the 737. Also looking at the Metro too. Small world now with the limited P3D addons.

 

Point still stands be it a 737 or a Metro. Business like that does not give people a good reason to purchase from you.

 

What would be so hard in supporting this hard work you put into the making of this?

If the issue is caused by us, then we will fix it.  We will support those who have issues with OUR end. Just not support the mindstar or the F1 installations. 

 

Don't we ALWAYS provide support even if (I'm) it's sometimes difficult?

 

The sound error is one we are aware of.  It's actually not us...

 

Bill says the fix is thus:

 

The "sound error" can only occur if for some reason the path to the SND files isn't present, or is mis-configured.  Check in the panel.Mindstar530 folder and load the panel.cfg file in Notepad.exe...

 

Down towards the bottom of this file, you should see an entry for the Milviz_Sound gauge that should be precisely this:

 

gauge00=Milviz_Sound!FBGS_XMLSound,  0,0,1,1,SimObjects\\Airplanes\\Cessna 310R MilViz\\panel\\C310R_Sounds#22

 

Please confirm that this entry is present.

 

Yes, except, your 310R main installer names the folder in FSX as "Cessna 310R FSX MilViz", not "Cessna 310R MilViz"

 

Joe

Aware of that too.  I am not the one who makes the installers. That's Bill.  If he says it's broke, it will be fixed tmrw first thing (after Mass) and then, we will send out the fixed version to all clients.

 

Here's the straight skinny on this... When we first started supporting RXP, we had a TON of people asking us "how do you do this that and the other thing" with RXP.  Nothing to do with us.  So, this time, I wanted to make it clear.  Perhaps I've been too clear?

 

Anyway, this kind of issue will, of course, be fixed as we would be shooting ourselves in the foot.  And we don't do that kind of thing in Canada.

Well, after your backup on your original statement, that seems better now that you have thought about supporting your own product, because your initial statement in this post...

 

 

There are NO REFUNDS and we do not support them in any way.  Install at your own risk.

 

 

Also seems to match what you have on your site. It does not state that you don't support Mindstar issues, but the issues with your own product. Maybe a change in the wording is in order to clear up any confusion.

 

From your site. Easy to see why we are questioning it.

 

 

Product Support

We do not provide support for these products in any way. You install and use them at your own risk.

Note: There is a known CTD on unloading an aircraft with these. Not our fault.

These products are sold AS IS. NO REFUNDS.

Mmmm... I see your point.  It will be changed now.

 

Fixed.   We "now" offer support on our end.

 

I will be sending out an email to all purchasers shortly with the "fix" as Bill stated and,  tmrw, I will ask him to make new installers.

 

Thanks for your attention (and for not getting pissy with me...)

Once I change the panel.cfg entry with the correct folder name the sound errors go away.

 

Please look at the gauge entry for FSX.  I get no bezels around either the 650 or 750.

 

Where I previously created a FTN gauge entry listing as:

(for instance) gauge07=F1GTN!GTN750,0,0,640,606,UNIT1.VC, 

 

You now drop the .VC at the end and add it to the gauge name, in essence. Don't want to post your entry since it is proprietary to your release.  But, it seems different than what F1 says, and, I am not getting any frames or bezels.  You may be correct their, but again, no bezels.

Bill will take a look at this when he can in the morning.. .It's Saturday night and tmrw's he's got Mass and then... he will see.  I am out tmrw all day with the kid (adventures!) but as soon as I get home, I will send out (and replace) the fixed files.