CCIP Cockpit Mod
-
@Red:
I fully agree and understand and i do the same
But we need to realize that you will always hear the bad things or the peculiar things, but you will never hear (or hardly) from the majority of users who are happy with your work as you released it.
That majority is silent and way more important than the few guys that are complaining or constantly asking for more without even realising the whishes or the method of the author.So as someone sharing itās work (of love) never be put away by a voicing minority. for every guy complaining about details, there is a hundreth guys being silent but enjoying the work provided.
Think of these guys first and the frustration goes awayYeah, thatās totally right.
Unfortunately, Iām aware that Iām narrow minded. -
Hi,
I understand how you feel and from a dev POV, maybe these unwritten ārulesā will help you manage:
1. Once you release something in Falcon land - Always be sure to grow a thick skin because there will ALWAYS be complains.
2. If someone keeps harassing you on the forums after you explained once (And once is enough!), then just ignore him.
3. 1 or 2 folks out of many that complain/harass/whatever arenāt worth ruining your mood or motivation towards releasing good stuff for everyone else.
4. This isnāt a real job, so never feel rush to do things now. Even if there is a real issue with your work, you can say that you are aware and you will fix whenever you feel up to it.
Follow these ārulesā and you will have much happier time with managing your work. FWIW I see complains about my work almost every day, someone says he canāt understand A or canāt find B or why I didnāt implemented C because itās in the real F-16 since dozen years agoā¦ What I do is I simply read and take notes for myself for what is important, what I may fix and what unlikely, thatās all. I donāt feel like I need to fix anything now nor I have to answer anyone right now. It is what it is.
And last but not least, the most important rule is the mother of all rules:
We are all here for the fun, so letās just try to enjoy.Cheers!
Thank you for the good advice, I-Hawk.
I will keep your words in mind. -
Did anyone said harassment? :rofl:
-
FWIW, I have enjoyed following your progress in this thread and I thank you for making it available.
-
Same here thank you Chuck!
-
Hey Chuck great job, keep it up !
But i have to report an issue about F-ACK. It doesnāt work, i tried to test it couple times with different faults but itās not working for me. The F-ACK screen is blank for all the time.
Btw just wondering about digital altimeter is it WIP or not?
Thanks again for your great job !
(NO PERSONAL MODIFICATIONS)
Best Regards! -
Hey Chuck great job, keep it up !
But i have to report an issue about F-ACK. It doesnāt work, i tried to test it couple times with different faults but itās not working for me. The F-ACK screen is blank for all the time.
Btw just wondering about digital altimeter is it WIP or not?
Thanks again for your great job !
(NO PERSONAL MODIFICATIONS)
Best Regards!PFD is working correctly in the latest version of release. I confirmed it.
If you mean the altimeter can be found in HAF Vipers, I have no plan to make it.
Because, AFAIK, USAF Block 50 doesnāt have it so far.
But please let me know, if Iām wrong. -
PFD is working correctly in the latest version of release. I confirmed it.
If you mean the altimeter can be found in HAF Vipers, I have no plan to make it.
Because, AFAIK, USAF Block 50 doesnāt have it so far.
But please let me know, if Iām wrong.I just asked for information to a real F16 avionic technician, he will reply to me in couple days. Thanks !
-
This post is deleted! -
Excellent work Peca_Chuck!
Lets make the majority to be loud and heard! -
Hey PeCa, here is a Turkish Air Force F16 Block50-Dās Front Seat Cockpit.
As you can see it has a digital altimeter. I dont have any idea about F16-C but if it will provide a ādigital altimer updateā to us i can ask for F16-C Block50 photos ?
Edit: Digital altimer confirmed for F16C Block-50 -
Same apply for HAF Block 52ās and Polish Vipers.
-
Installed it a couple weeks ago. Beautiful work Peca Chuck. The attention to detail on the canopy alone is impressive.
-
Hey PeCa, here is a Turkish Air Force F16 Block50-Dās Front Seat Cockpit. http://i.hizliresim.com/r6gX2m.jpg
As you can see it has a digital altimeter. I dont have any idea about F16-C but if it will provide a ādigital altimer updateā to us i can ask for F16-C Block50 photos ?
Edit: Digital altimer confirmed for F16C Block-50Same apply for HAF Block 52ās and Polish Vipers.
I think his goal is to replicate the USAF Block 50s . Those still have the analog altimeters.
Regards
-
Since Iāve noticed that non-linear output for DOFs is available in 3dckpit.dat, been working on it to get correct indication in some analog instruments.
The problem I have now is, we(end user) cannot have raw data of flight and engine status, except the data in info bar of external view.
That makes nearly impossible to make correct indication in some instrument, even after BMS team incorporated the non-linear DOF schedule.Iāve searched on this forum, .key files and Falcon BMS.cfg to get the kinda āDebug Modeā, but couldnāt find it.
If such āDebug Modā, which could output or display raw flight/engine data, exists in somewhere, I really want it.
We need it, especially for non-dev side 3d cockpit developer, including me.Please consider my request seriously, DEV team.
If we already have a way to get such data, please let me know.Moreover, would you provide us the specification of non-linear schedule output, if itās available.
I mean the list of xxx-needle style definition names and corresponded values.
The list will be very useful for 3d cockpit developers.
I will much appreciate for it. -
This post is deleted! -
Version 6.0.3 has been released.
Change log and the URL for download are available in the first post.If you have already installed the previous version, please follow the following process for update.
Before the installation of this version, you must back up the number of parent records in 3dckpit.dat.
Open the 3dckpit.dat in your installation, and note the following line somewhere.cockpitmodel xxxx;
cockpitmodel2 xxxx;
cockpitmodel3 xxxx;
cockpithudmodel xxxx;
cockpitcanopymodel xxxx;Then, replace the 2.lod, and overwrite the Data folder if you are updating from 6.0.2.
If you have earlier version including 6.0.1, replace all of lods, and overwrite the Data folder.After the replacing and overwriting, re-open the 3dckpit.dat, and replace the ācockpit~ā lines with noted one.
-
@PeCa_Chuck The download links provideās the 6.0.2_Beta file ā¦ā¦
-
@PeCa_Chuck The download links provideās the 6.0.2_Beta file ā¦ā¦
Try reloading the page, or deleting the cookie.
Youāll get the correct link. -
I have just a little insurance
When i press append parent record, it tells me the #3163
But when i click normal on that parent and use the viewer, it shows me the rendered model of the Aggressor F-16 from the view of the cockpit
I tried that with U3
what could i have possible done wrong? I followed the steps from the manual on the webpage until i came across this, then i pulled the brakes
And after lauching the second LODEditor, and entering parent#1 i canāt see any LOD# in my field as you have it in the picture
Edit: Ok, nevermind, itās working
Thanks for creating or improve such a beatiful pit