Affichage des articles dont le libellé est causing. Afficher tous les articles
Affichage des articles dont le libellé est causing. Afficher tous les articles

lundi 10 février 2014

[Help] Bone read causing crash topic




hello i'm trying to make a bone esp but i'm having a issue..

I'm using this classes:


Code:


class CBone
{
public:
    char*      m_BoneName;    //0x00 
    char        pad_04[136];      //0x04
    D3DXMATRIX  BoneMatrix;  //0x8C 
    D3DXMATRIX  SomeMatrix;  //0xCC 
};


class CBoneInfo
{
public:
    char      pad_00[20];
    DWORD      oneNum;          //0x18
    CBone*    pBones;            //0x1C
};


class CSkeleton
{
public:
    char      pad_00[40];
    CBoneInfo* BonePtr;        //0x28
};

class CPlayer
{
public:
    char _0x0000[36];
    D3DXVECTOR3 m_Position; //0x0024
    char _0x0030[16];
    D3DXVECTOR3 m_vMuzzlePosition; //0x0040
    char _0x004C[908];
    DWORD m_NameXor; //0x03D8
    char _0x03DC[60];
    __int32 m_NameLength; //0x0418
    char _0x041C[132];
    __int32 backpackItemID; //0x04A0
    __int32 alive_state; //0x04A4
    char _0x04A8[12];
    float m_iHealth; //0x04B4
    char _0x04B8[3392];
    CSkeleton* m_Skeleton; //0x11F8
    char _0x11FC[36];
    //    CWeaponInfo* m_pWeaponPrimary; //0x1220
    //CWeaponInfo* m_pWeaponSecondary; //0x1224
    char _0x1228[32];
    float m_flPickupTime; //0x1248
    char _0x124C[96];
    D3DXVECTOR3 m_Movement; //0x12AC
    char _0x12B8[4];
    float m_cameraHeight; //0x12BC
    float m_stamina; //0x12C0
    char _0x12C4[16];
    __int32 SniperTest1; //0x12D4
    __int32 SniperTest2; //0x12D8
    char _0x12DC[28];
    DWORD m_bDead; //0x12F8
    char _0x12FC[36];
    float m_jumpHeight; //0x1320
    char _0x1324[16];
    D3DXVECTOR3 m_vRecoilCameraAngles; //0x1334
    char _0x1340[116];
    float m_yaw; //0x13B4
    float m_pitch; //0x13B8
    char _0x13BC[4];
    float m_fSpeedStrafe; //0x13C0
    char _0x13C4[4];
    float m_fSpeed; //0x13C8
    char _0x13CC[92];
    D3DXMATRIX m_BoneCoeff; //0x1428
    char _0x1468[24];
};


and this to read:


Code:


CPlayer Player = p_MemProc->read<CPlayer>(PlayerAddress);
BoneMatrix = Player.m_Skeleton->BonePtr->pBones[1].BoneMatrix;


but when it runs it crash on the 2 line.. someone can help me?

thx





mercredi 29 janvier 2014

Re: UTC "timezone" causing brain explosions topic




On 01/29/2014 01:52 PM, Skip Montanaro wrote:
> Following up on my earlier note about UTC v. GMT, I am having some
> trouble grokking attempts to convert a datetime into UTC.
>
> Okay, let's see what GMT does for us:
>
>>>> GMT = pytz.timezone("GMT")
>>>> u = GMT.normalize(s)
>>>> u

> datetime.datetime(2014, 1, 29, 21, 39, 35, 263666, tzinfo=<StaticTzInfo 'GMT'>)
>>>> u.hour

> 21
>
> That looks correct, but I don't understand why I don't get hour==21
> out of the UTC.normalize call. It's like it's a no-op.


Having not examined the code, I can't tell you why UTC is different. I can say that .astimezone seems to work in all cases:

--> GMT
<StaticTzInfo 'GMT'>

--> UTC
<UTC>

--> LOCAL_TZ = pytz.timezone("America/Los_Angeles")

--> now = datetime.datetime.now()

--> s = LOCAL_TZ.localize(now)
--> s
datetime.datetime(2014, 1, 29, 14, 9, 56, 494967, tzinfo=<DstTzInfo 'America/Los_Angeles' PST-1 day, 16:00:00 STD>)

--> s.astimezone(UTC)
datetime.datetime(2014, 1, 29, 22, 9, 56, 494967, tzinfo=<UTC>)

--> s.astimezone(GMT)
datetime.datetime(2014, 1, 29, 22, 9, 56, 494967, tzinfo=<StaticTzInfo 'GMT'>)

--
~Ethan~





Re: UTC "timezone" causing brain explosions topic




On Wed, Jan 29, 2014 at 1:52 PM, Skip Montanaro <(E-Mail Removed)> wrote:
> Following up on my earlier note about UTC v. GMT, I am having some
> trouble grokking attempts to convert a datetime into UTC. Consider
> these three values:
>
>>>> import pytz
>>>> UTC = pytz.timezone("UTC")
>>>> LOCAL_TZ = pytz.timezone("America/Chicago")
>>>> LOCAL_TZ

> <DstTzInfo 'America/Chicago' CST-1 day, 18:00:00 STD>
>>>> now = datetime.datetime.now()
>>>> now

> datetime.datetime(2014, 1, 29, 15, 39, 35, 263666)
>
> All well and good, right? The variable "now" is a naive datetime
> object. I happen to be sitting in a chair in the city of Chicago, so
> let's call it what it is, a datetime in the America/Chicago timezone:
>
>>>> s = LOCAL_TZ.localize(now)
>>>> s

> datetime.datetime(2014, 1, 29, 15, 39, 35, 263666, tzinfo=<DstTzInfo
> 'America/Chicago' CST-1 day, 18:00:00 STD>)
>
> That looks good to me. Now, let's normalize it to UTC:


I don't think .normalize() doesn't do what you think it does; it's
related to timezones with DST.
I believe you want datetime.astimezone() instead.

>>>> t = UTC.normalize(s)
>>>> t

> datetime.datetime(2014, 1, 29, 15, 39, 35, 263666, tzinfo=<UTC>)
>>>> t.hour

> 15
>
> WTF? Why isn't the t.hour == 21?


Because you didn't actually perform a proper timezone conversion:
>>> t = s.astimezone(UTC)
>>> t

datetime.datetime(2014, 1, 29, 21, 39, 35, 263666, tzinfo=<UTC>)
>>> t.hour == 21

True

<snip>
> That looks correct, but I don't understand why I don't get hour==21
> out of the UTC.normalize call. It's like it's a no-op.


It is indeed a no-op:
"You can take shortcuts when dealing with the UTC side of timezone
conversions. normalize() and localize() are not really necessary when
there are no daylight savings time transitions to deal with."
-- http://pytz.sourceforge.net

Cheers,
Chris





UTC "timezone" causing brain explosions topic




Following up on my earlier note about UTC v. GMT, I am having some
trouble grokking attempts to convert a datetime into UTC. Consider
these three values:

>>> import pytz
>>> UTC = pytz.timezone("UTC")
>>> UTC

<UTC>
>>> LOCAL_TZ = pytz.timezone("America/Chicago")
>>> LOCAL_TZ

<DstTzInfo 'America/Chicago' CST-1 day, 18:00:00 STD>
>>> now = datetime.datetime.now()
>>> now

datetime.datetime(2014, 1, 29, 15, 39, 35, 263666)

All well and good, right? The variable "now" is a naive datetime
object. I happen to be sitting in a chair in the city of Chicago, so
let's call it what it is, a datetime in the America/Chicago timezone:

>>> s = LOCAL_TZ.localize(now)
>>> s

datetime.datetime(2014, 1, 29, 15, 39, 35, 263666, tzinfo=<DstTzInfo
'America/Chicago' CST-1 day, 18:00:00 STD>)

That looks good to me. Now, let's normalize it to UTC:

>>> t = UTC.normalize(s)
>>> t

datetime.datetime(2014, 1, 29, 15, 39, 35, 263666, tzinfo=<UTC>)
>>> t.hour

15

WTF? Why isn't the t.hour == 21?

Okay, let's see what GMT does for us:

>>> GMT = pytz.timezone("GMT")
>>> u = GMT.normalize(s)
>>> u

datetime.datetime(2014, 1, 29, 21, 39, 35, 263666, tzinfo=<StaticTzInfo 'GMT'>)
>>> u.hour

21

That looks correct, but I don't understand why I don't get hour==21
out of the UTC.normalize call. It's like it's a no-op.

Skip





lundi 27 janvier 2014

What's causing my app drawer problem? topic




Hey guys.
About a few times a day whenever I go into my app drawer everything seems to "blacked out". Icons are barely visible but if I simply back out and re-enter, everything is back to normal.

Any ideas?

Thanks.








Attached Thumbnails


Click image for larger version<br/><br/>Name:	Screenshot_2014-01-27-23-27-59.jpg<br/>Views:	N/A<br/>Size:	92.4 KB<br/>ID:	2543871
 
















jeudi 23 janvier 2014

Video streams causing FC in flixter/bbc news topic




youtube streams videos fine but when trying to play files via BBC/Flixster the app refuses to play the video. do these require adobe flash still or something? or is the default open with trying to default to the frozen apk? currently i have BSplayer installed to handle the requests.