All we hear is talk of anti software piracy to protect the developer, what ever happened to the rights of the user. 

 

Surelly the laws of onwership have radically been redefined here. What happens if thier server gets hacked again, we all go reinstall again. 

 

As a result of this incident i think FSUIPC license  policy is totally weighted in interest of the developer to the inconvinience of the purchaser of the product. 

 

Looking in to the future we can expect to see more and more ridiculus license policies.

 

Its all good though, i welcome anything to put me off this hobby this days.

 

Somebody needs to redefine what onwership of something means, after you have paid for it.

Simmer2050, on 06 May 2013 - 4:59 PM, said:

 

All we hear is talk of anti software piracy to protect the developer, what ever happened to the rights of the user.

 

Surelly the laws of onwership have radically been redefined here. What happens if thier server gets hacked again, we all go reinstall again.

 

As a result of this incident i think FSUIPC license policy is totally weighted in interest of the developer to the inconvinience of the purchaser of the product.

 

Looking in to the future we can expect to see more and more ridiculus license policies.

 

Its all good though, i welcome anything to put me off this hobby this days.

 

Somebody needs to redefine what onwership of something means, after you have paid for it.

Wellll...he did replace it at no cost and he removed the code that does the check. So, he's doing the right thing here...right?

 

The problem with my yoke, however, is actually worse than I thought. I'm also getting sporadic spikes on my other quadrant handles too. I was sitting at half throttle on decent and suddenly the beta light came on and my left engine went into reverse. Moving the throttle a bit resolved it but......help! When I look down at them they're jittering about 3-4%!

_{Well, if it *IS* the fault of FSUIPC, I can assure you that Pete will be on it immediately and a new version will be out. Have you posted your problems in his OFFICIAL forum?}

 

_Vic

 

 

Well, if it *IS* the fault of FSUIPC, I can assure you that Pete will be on it immediately and a new version will be out. Have you posted your problems in his OFFICIAL forum?

 

Just did.  Wasn't aware he had a forum.  Never had an issue before this.  Always a first tiiiiiime.

 

 

As a result of this incident i think FSUIPC license policy is totally weighted in interest of the developer to the inconvinience of the purchaser of the product.

 

Sorry, but this characterization is grossly unfair and shows a lack of understanding of what occurred.  Code signing is as much for the protection of the consumer as anything, and Pete Dowson's asking for the certificate to be revoked by the signing authority is ABSOLUTELY the right call for everyone.  He could have taken the easy road and just left things alone, leaving users more vulnerable to malware but he took the right path, asked for the cert to be revoked when he discovered it had been compromised and offered a free update for all users.

 

Yes, it's an inconvenience - but I expect far more for Mr. Dowson than for any of us.

 

Scott

It's also "Best Practice" in the IT world that the vendor of almost every retail application that is on the market, purchases the certificate to ensure that you know that the app is genuine and authentic, and is coming from a known source. A Verisign Certificate is not cheap.

 

Pete didn't have to do it. He could have simply ignored it.

The thing is - Pete Dowson is one of "the good guys" in this hobby, and deserves a great deal of credit and thanks for the service he has provided tirelessly for an awful long time. This act is just another example of the kind of character which he embodies.

I found out that, whatever has happened, it's also affecting my GoFlight pedals.  Pete says it's not FSUIPC causing it.  Controls are disabled in FSX, UAC is off, FSX is set to run as admin (not necessary if UAC if off but...why not.)  I haven't had any issue with my controls since I originally installed FSUIPC 9 months ago.  At this point, I'm stumped.

I found out that, whatever has happened, it's also affecting my GoFlight pedals. Pete says it's not FSUIPC causing it. Controls are disabled in FSX, UAC is off, FSX is set to run as admin (not necessary if UAC if off but...why not.) I haven't had any issue with my controls since I originally installed FSUIPC 9 months ago. At this point, I'm stumped.

Also check your key mapping to ensure no conflicts.

 

I would make a flight with as little addons as possible just to check no conflicting keys. Or even conflicting applications.

 

I would for example try flight with no EZDOK/ Addon ATC or GSX for example,

 

 

Also check your key mapping to ensure no conflicts.

I would make a flight with as little addons as possible just to check no conflicting keys. Or even conflicting applications.

I would for example try flight with no EZDOK/ Addon ATC or GSX for example,

 

Thanks.  This is exactly my thought.  I have a suspicion.

 

Gregg

I believe I've found it.  It's a program called VAFS...a VA reporting program.  I found out it uses FSUIPC and I think it's stressing it out on my system.  I ran a short test last night and another longer one this morning.  The spikes only occur after I launch it and continue even if I shut it down.  At least that's what I've seen so far.  Keeping my fingers crossed.

Yeah, I ran a much longer test this morning.  Without VAFS running the system was fine.  No spikes at all.  Panic averted...I'll post something to their site.

There is something going on. my FSUIPC.INI has buttons assigned to key strokes for the Desktop Aviator G530 as well as for the F1 Mustang G1000

 

The new FSUIPC has stopped recongnizing these keys.. It simply freezes (at the fsuipc.exe or fsuipc_loader.exe,...depending on which I am using)  when loading FSX,. When I delete these entries from FSUIPC.ini, it gets into FSX

 

I can't post my problem at Pete's website since that site is blocked  at my work place. Luckily AVISIM is not. LOL

 

And yes. I concur...Pete is an awesome person... and I rarely go to his forum since FSUIPC never gave me grief.. its one of those things you install and forget about it for years.

 

 

There is something going on. my FSUIPC.INI has buttons assigned to key strokes for the Desktop Aviator G530 as well as for the F1 Mustang G1000



The new FSUIPC has stopped recongnizing these keys.. It simply freezes (at the fsuipc.exe or fsuipc_loader.exe,...depending on which I am using) when loading FSX,. When I delete these entries from FSUIPC.ini, it gets into FSX



I can't post my problem at Pete's website since that site is blocked at my work place. Luckily AVISIM is not. LOL



And yes. I concur...Pete is an awesome person... and I rarely go to his forum since FSUIPC never gave me grief.. its one of those things you install and forget about it for years.

 

Wish I could help.  I just started looking at admins and then my eyes fell on VAFS.  You might need to go through the same exercise.  I'll be curious what Pete says.

Maybe depends on what version of fsuipc you had been running previously?

 

scott s.

.

I just upgraded from v4.86 to v4.9. Flew my F1 Mustang from Wichita to Jackson Hole. Using FSX Accel, Kostas Tweaks, ORBX, FEX (real world weather), RCV4, TrackIR, Aivlasoft EFB, CH Eclipse yoke, CH Throttle Quad and CH Pro pedals. All the CH products were assigned and calibrated in the earlier version.

 

Beautiful flight, not a single hiccup.

 

I'm thinking these problems must be individual system, user related. Otherwise, wouldn't everyone using v4.9 have the same issues?